Post

Replies

Boosts

Views

Activity

Live Activity Persistence After App Force Quit
I have a state in my app that is connected to a Live Activity. When the state is true, the Live Activity is active, and when it is false, the Live Activity is ended. I have noticed, though, that if a user starts the Live Activity (by changing the state to true), then force quits the app, then reopens the app and changes the state to false, the Live Activity is not ended / removed from the lock screen. Is there any way to fix this? Since there is no problem ending the Live Activity if the user doesn't force quit the app, it seems as though the Live Activity may be somehow connected to the specific instance of the app. Is there a way to not have the Live Activity connected to the only active instance of the app, but be able to have it ended by any future instance of the app?
2
0
1.5k
May ’23
ManagedSettingsStore applicationCategories all() specifications
Within ManagedSettingsStore, in the documentation for the ShieldSettings.ActivityCategoryPolicy enum (here), one of the options is all(). It states that if this is used, the device will shield "all apps and websites". In practice, I have noticed that when this is used, a handful of apps (i.e. Messages, Maps) remain unblocked. Furthermore, it appears that on different devices, this usage results in different apps remaining unblocked (on my device Messages remained unblocked, but on another tester's device Messages was blocked). Can anyone provide clarification as to explicitly which apps are not included in the specification of "all()" and whether this changes based on device, iOS version, etc.?
2
0
892
Mar ’23