Push tokens: how to get a user/app to run after users transfers to a new phone?

If the user installs an application which uses push notifications onto iPhone A and then runs the app then the app will send the push token to the server (and from that point one the app should detect if the push token changes and send the new token to the server).

However there's no way that the app can do this in the situation where the user backs up iPhone A to iCloud and then restores to iPhone B.

If the user doesn't explicitly launch the application, then the application has no chance to detect that the push token will have changed, and so meanwhile the server is sending pushes using the token from phone A but the user now is using phone B.

User's won't know they have to launch an app on phone B, and there's no way the app can launch itself, so the user's now have a non functioning app but they don't realise it.

There must a lot of apps using push that face this situation, yet there's no solution?

I was hoping iOS 16's background asset download might be a solution to this - if the extension gets called after restoring from iCloud it could detect the device change and thus push token change and post a notification to the user telling them they need to launch the app, but this extension appears to be functionally sandboxed and its not possible to post a notification from within it (unlike many other extensions).

The asset download extension would have been an opportunity to transmit the new push token, but the documentation for it says "Use the framework only to download additional assets for your app; don’t use it for any other purposes. For example, don’t collect or transmit data"

Push tokens: how to get a user/app to run after users transfers to a new phone?
 
 
Q