A widget is a type of app extension. A widget can then be of a variation of types Since a widget is an app extension, then: No it can't have the same bundle id of the main app's. Meaning: if your app's bundle id is app.foo.bar, then your app extension's bundle id should be app.foo.bar.baz As mentioned above, you can't use identical bundle ids. Each target (app, app extension) requires their own bundle.

That's expected. The os is getting launched only for the notification that was tapped on. Beyond that you can use this API: https://developer.apple.com/documentation/usernotifications/unusernotificationcenter/getdeliverednotifications(completionhandler:) to query all delivered notifications and then process those. That said I recommend against processing delivered notifications. It's not the users's intent to interact with the rest. At best you should just log them. Like imagine if each notification caused a navigation to a certain part of your app. Do you want to process and navigate 5 notifications at once?!

I see thanks. The word 'active' was confusing. I thought it meant just staying on the screen. So 'active' in this context means 'able to receive updates'. Right?

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

I believe you need a paid developer account and have regular push notifications enabled. Then things should work...

Pretty sure it's not possible, nor desirable. Imagine if someone did that to your app. Also from the user's perspective, the Dynamic Island is meant to show anything active from other apps. The moment it stops showing, it hints to the user that the Live Activity is not longer active. You'd create an incorrect illusion that the Live activity was ended, but that's incorrect.

Might be that the app is out of budget for new tokens. Look into Console. Check for liveactivitiesd or apnsd or search for the activity attributes type Example RideActivityAttributes Make sure you're requesting tokens within the didFinishLaunching. Otherwise app might be awaken, but you're not subscribed for the newer tokens Did you include the input-push-token: 1 as well? using os.logs might be helpful to properly see the sequence of events along with OS logs itself to see a better picture of things.

I'm guessing this is because the used the OS settings and turned off Notifications on their device . That makes the token unregistered. But then next time you request the token from OS, the OS gives you the same token. I just asked a similar question about it with more detail. Take a look: https://developer.apple.com/forums/thread/806522