Push notifications do not work for a specific device with the "completely unknown token" log

Silent push notifications do not work for a non-developer device with iOS 10.0. There are no problems with certificates or profiles, and APNS does not respond with a “wrong error” for any other error, so it seems that the token is valid (I tried to send notifications from the server and from a local tool called Pusher, and the results were the same).

When I connect the device to the Mac and see console logs, I can see the following lines:

default 15:43:26.138766 +0300 apsd 2017-07-12 15:43:26 +0300 apsd[86]: isAppSpecificTokenValid? <cf0d4bad 846685a1 0b0e4e34 0e1ad03e 74c00df2 295a23e3 7586f94c 78c46284> found cached token NO default 15:43:26.139477 +0300 apsd 2017-07-12 15:43:26 +0300 apsd[86]: Received incoming push notification for topic: <my.app.id> but for a completely unknown token <cf0d4bad 846685a1 0b0e4e34 0e1ad03e 74c00df2 295a23e3 7586f94c 78c46284> default 15:43:26.140523 +0300 apsd 2017-07-12 15:43:26 +0300 apsd[86]: <APSCourier: 0x1004109c0>: Responding with REMOVED status for message received with topic: '<my.app.id>' to device token (instead of per-app token) 

I can’t understand the steps for reproducing this error, but this may be due to installing the AppStore version over the TestFlight version.

+7
ios testflight apple-push-notifications
source share
1 answer

but this may be due to the installation of the AppStore version over the TestFlight version.

To make this a problem, it looks like you are not doing registerForRemoteNotifications every time the application starts. You must make this call every time (and possibly update it on your server), because there is a chance that it can change, and there is a chance that the user changed the permissions on your application when it was not running.

0
source share

All Articles