Ok this makes sense and it matches with what I've been experiencing. Thanks so much for the detailed answer, Albert! This helped a lot

Is this behavior similar for start token? I initially noticed that start token would regenerate on app upgrade but recently I've noticed that it doesn't if I update right away after a fresh install. Is that token regeneration also handled dynamically by APNs? And a second question about pushTokenUpdates: If the user has not opened the app while a live activity is going, would the pushTokenUpdates still be active throughout the lifespan of the activity or would it get suspended at some point?

We already ask users to enable notifications when they open the app since push notifications are used for other features and we also use notifications to remote start/update live activities. However, when I send a push to start a Live Activity for a new user, iOS shows an Allow/Don’t Allow prompt under the activity. If that activity ends or is dismissed, the same prompt appears again the next time. Usually, only after the 3rd or 4th attempt does Always Allow appear and the prompts stop.

Isn't NSUserNotificationUsageDescription used to define the message shown when the app requests push notification permission? In my case, the app does request push notification permission, but Live Activities still prompt the user several times before “Always Allow” finally appears. It is only after this that the Live Activity starts registering the update token without prompting the user. Let me know if there is something I'm missing about how permissions works.

Isn't NSUserNotificationUsageDescription used to define the message shown when the app requests push notification permission? In my case, the app does request push notification permission, but Live Activities still prompt the user several times before “Always Allow” finally appears. It is only after this that the Live Activity starts registering the update token without prompting the user. Let me know if there is something I'm missing about how permissions works.

Isn't NSUserNotificationUsageDescription used to define the message shown when the app requests push notification permission? In my case, the app does request push notification permission, but Live Activities still prompt the user several times before “Always Allow” finally appears. It is only after this that the Live Activity starts registering the update token without prompting the user. Let me know if there is something I'm missing about how permissions works.