Push tokens from push-to-start Live Activities require user permissions?

App & System Services Widgets & Live Activities
JerielBRZ OP
Created Sep ’25
Replies 2
Boosts 3
Views 133
Participants 3

Just wanted to clarify some expected behaviors here. It seems that there are two distinct behaviors for Live Activity flows for freshly installed apps.

When you start a Live Activity for the first time and the user hasn't yet clicked on Allow/Don't Allow in the activity interface, there are two different sequences:

Starting a Live Activity locally

  1. Request a Live Activity locally via Swift
  2. Live Activity starts
  3. .pushTokenUpdates is immediately triggered, even if the Allow/Don't Allow buttons appear under the Activity UI

Starting a Live Activity via push-to-start

  1. Send a push-to-start notification to launch a Live Activity
  2. Live Activity starts
  3. .pushTokenUpdates is not triggered, and .pushToken returns nil.
  4. If a user clicks on Allow in the Activity UI, only then is .pushTokenUpdates triggered.
Replies  2
Boosts  3
Views  133
Participants  3
bradpriddy OP
1w

This is what I've observed as well

1
SwiftyHoney OP
1w

Doing a server based approach. And yes in ours hitting "Allow" was what allowed update tokens to be issued by the OS

1
Push tokens from push-to-start Live Activities require user permissions?
First post date Last post date
 
 
Q