You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are seeing a bug where when we request request(Permissions.PERMISSIONS.IOS.LOCATION_ALWAYS) and we see the popup below. Upon selecting Allow while using app (LOCATION_WHEN_IN_USE), if we then check both the permissions LOCATION_ALWAYS and LOCATION_WHEN_IN_USE, they return as granted. The expected behaviour from this flow would be that LOCATION_ALWAYS is denied and only LOCATION_WHEN_IN_USE is marked as granted
If your app’s current state is CLAuthorizationStatus.notDetermined and you call requestAlwaysAuthorization(), Core Location uses two prompts before it fully enables Always authorization.
The first prompt displays immediately with the string from NSLocationWhenInUseUsageDescription. The user prompt displays the following options, which determine the authorization your app receives:
Allow While Using App | Core Location grants your app a Provisional Always authorization. The delegate receives CLAuthorizationStatus.authorizedAlways.
And later, it will prompt a second time saying this app uses background location and the user will be able to change his mind.
Bug summary
We are seeing a bug where when we request request(Permissions.PERMISSIONS.IOS.LOCATION_ALWAYS) and we see the popup below. Upon selecting Allow while using app (LOCATION_WHEN_IN_USE), if we then check both the permissions LOCATION_ALWAYS and LOCATION_WHEN_IN_USE, they return as granted. The expected behaviour from this flow would be that LOCATION_ALWAYS is denied and only LOCATION_WHEN_IN_USE is marked as granted
In suspecting that this may be related to: #490
I am investigating going through the "A normal permission escalation" as outlined here.
Library version
3.3.1
Environment info
The text was updated successfully, but these errors were encountered: