Adithya Reddy
Adithya Reddy
@zoontek doing `request` for `LOCATION_ALWAYS` will return `RESULTS.BLOCKED` right now if we have `LOCATION_WHEN_IN_USE` permission already.
You're right yea it's more complicated than I initially thought. Do you have any ideas on how to approach fixing it? My initial guess is that without some form of...
@jdegger that'll work for the initial request -- but to keep the API consistent we also need to track manually when we've asked for it already and return `DENIED` --...
@zoontek would you be willing to accept a PR that fixes only the iOS permission escalation issue (where you can't request location always authorization after you've been granted location when...
PR opened for this here: https://github.com/zoontek/react-native-permissions/pull/529
@taylorkline we'd all like to see this fixed but for now you'll have to consider this a missing feature. I'd suggest using the changes in my PR linked above along...
@zoontek we're revisiting this at our org -- the PR I made for this was left hanging because of your concern over a promise that might be unresolved indefinitely (which...
@zoontek here's the new PR! https://github.com/zoontek/react-native-permissions/pull/716
@Peeeep happy to help! Make sure you read the limitations in the README!
@zoontek would you be okay merging this if I update the PR with @nasmuris's approach here to avoid having the unresolved promise? https://github.com/zoontek/react-native-permissions/pull/529#discussion_r550209147 Would really like to get this feature...