The "Allow Once" authorization is temporary and expires when your app is no longer in use, reverting to CLAuthorizationStatus.notDetermined. It is an option that gets the worst treatment. ![]() "Allow Once", which requests the least authorization, should get the least constraint. Their decision sticks there even after the app is uninstalled. Users will only see the location dialog only once. The only way to recover is to direct a user to the setting and unchanged the selection (which is unlikely to happen). The subsequent request of user location goes in vain. Once a user decided to tap "Don't Allow", you are almost done. The problem of asking for any kind of location permission, in general, is you only have one chance to do it. This is suit for an app that asking for user location isn't a core feature of an app, but a nice addition, e.g., get current user location to show nearby store, send current location to a friend over messaging app.Īsking for a one-time location is troublesome with the current implementation in the following areas: One-shot ![]() The location button provides a better way to ask for a one-time user location. Let's see what problem this button is trying to solve and how. In iOS 15, Apple introduces a new way of asking for user location, Location Button. As a developer, asking for user's sensitive data at an inappropriate time or not enough clear context might get rejected. It isn't a surprise if users would concern about their privacy.
0 Comments
Leave a Reply. |