I know device tokens remaining active after an uninstall is expected but the unexpected part of this is that the device tokens will still send pushes after reinstalls. Here is the scenario:
I have recorded the deviceToken of an existing app install using Urban Airship. Then deleting the app and reinstalling, I recorded the new device token as well. These tokens are different. From the UA test panel, I am able to send a test push to both of these tokens and the device receives 2 pushes, one for each token, even though the first token has since been uninstalled. But, in UA device lookup, both tokens are marked as active.
Currently, on one development device, I am receiving up to 8 pushes at a time and all previous tokens remain active. What exactly will cause one of these tokens to go inactive? I have found this list but it does not seem to apply here: http://docs.urbanairship.com/reference/troubleshooting/ios-push.html#inactive-device-token
Is there any recommendation for unregistering from push notifications before an uninstall? Obviously, we cannot manually unsubscribe on the app uninstall event. Also want to remain subscribed between sessions of the same install. I thought of storing the original device token in the device keychain to persist it between installs and updating it when necessary but that is not a very straight forward solution or friendly solution.
The app is built with an enterprise profile. Additional info can also be found here: http://stackoverflow.com/questions/40408872/urban-airship-device-tokens-remain-active-between-installs
Comments
3 comments