App continues to wake in background after stopUpdatingLocation

I'm experiencing an odd (to me) case when the app has

requestAlwaysAuthorization
- a user can start location updates, receive updates at regular intervals as expected, and later stop updates. The strange thing is that although the app has inidcated that it should no longer receive location updates, the OS (11.x) continues to wake the application from background with the launch key
UIApplicationLaunchOptionsKey.location
(which signals to my app that it should resume location services).


Am I doing something wrong, or is this intentional behavior on behalf of the OS and location services? It seems that once I tell the location manager to stop, the application should no longer be woken in the background.

Are you using significant location updates or region monitoring? What do you mean exactly by "he app has indicated that it should no longer receive location updates"?. The use of these services produces the application is waken up in the background. In case you are doing that, you might want to stop these services when it is convenient for the application in order not to be launched in background.

App continues to wake in background after stopUpdatingLocation
 
 
Q