title: Receiving "DeviceTokenNotForTopic" when pushing to watchOS only app
body: <p>I am trying to receive push notifications in a watchOS-only app and I am getting   <code>DeviceTokenNotForTopic</code> when using the sandbox server and <code>BadDeviceToken</code> when using the production one. I am using the keyId + key certificate (*.p8) method and I am pushing using an http2 client from Node.js (<a href="https://www.npmjs.com/package/apns2" rel="nofollow noreferrer">apns2</a>). I have experimented with adding and removing the <code>.watchkitextension</code> suffix from the topic but I am still getting the same result. I have verified that the APNS client is adding correctly the <code>apns-topic</code> and <code>apns-push-type</code> headers</p>
  <p>For the record, I have successfully pushed notifications using the same route to an iOS-only app (with different keyId/key and bundle name).</p>
  <p>Has anyone experienced something similar?
  Any thoughts would be appreciated.</p>
  <p><strong>UPDATE 10/18/20</strong></p>
  <p>Follow the workarround solution presented in <a href="https://stackoverflow.com/questions/58094221/failing-apns-for-independent-watchos6-app">Failing APNS for Independent WatchOS6 app</a>. It seems that XCode does not include Push Notification entitlements to <strong>.watchkitapp</strong> extension.</p>