Thanks, Albert. One clarification: the issue does not occur during a normal user-initiated force quit. If the user force-quits the app while the CLBackgroundActivitySession is active, the blue location indicator is removed as expected. The issue occurs specifically during an in-place app update: The installed version starts a CLBackgroundActivitySession. While that session is active, a newer version is installed over the existing app. After the process replacement, the blue location indicator remains visible. Force-quitting the newly installed version does not remove it. Only restarting the device clears the indicator. It therefore appears that the assertion belonging to the previous app process becomes orphaned during the update. The newly installed process has no reference to that session and cannot invalidate it. We have submitted a focused sample project and a sysdiagnose through Feedback Assistant: FB24182791 — Blue location indicator remains after in-place app update with active CLBackgroundActivitySession Thanks again for pointing us in the right direction.

Thanks, Albert. To clarify, this issue isn’t related to our Live Activity. The affected gps track-recording feature currently doesn’t use a Live Activity. Our use case is continuous background track recording using CLLocationUpdate.liveUpdates() together with a retained CLBackgroundActivitySession. The blue location indicator during recording is expected. The issue occurs when the app is updated while background tracking is active: Version 1 is recording in the background. While CLLocationUpdate.liveUpdates() and the retained CLBackgroundActivitySession are still active, version 2 is installed over the existing app. The old process is terminated during installation. Version 2 stops or doesn’t resume location tracking. The blue indicator nevertheless remains permanently visible. Force-quitting and reopening the app doesn’t remove it. Only restarting the iPhone clears it. The issue occurs during App Store updates, but it can also be reproduced during development by installing a newer build over the existing app using Xcode. This suggests that the system-level assertion belonging to the process terminated during installation isn’t being cleaned up correctly. If helpful, we can prepare a focused sample app that reproduces the issue.