-
Notifications
You must be signed in to change notification settings - Fork 24.9k
Closed
Labels
Ran CommandsOne of our bots successfully processed a command.One of our bots successfully processed a command.Resolution: LockedThis issue was locked by the bot.This issue was locked by the bot.Type: DocsIssues concerning the docs are tracked elsewhere: https://github.com/facebook/react-native-websiteIssues concerning the docs are tracked elsewhere: https://github.com/facebook/react-native-website
Description
According the the documentation found here,
Android API >= 23 Requires an additional step to check for, and request the ACCESS_FINE_LOCATION permission using the PermissionsAndroid API. Failure to do so may result in a hard crash.
However, in actual usage of the navigator.geolocation.getCurrentPosition()
API, it does not actually require that the permission is requested from the user. It automatically requests the user's permission for ACCESS_FINE_LOCATION
. The code that reflects this change can be found here.
Here is the commit that introduced the change.
Should the documentation reflect reality?
Metadata
Metadata
Assignees
Labels
Ran CommandsOne of our bots successfully processed a command.One of our bots successfully processed a command.Resolution: LockedThis issue was locked by the bot.This issue was locked by the bot.Type: DocsIssues concerning the docs are tracked elsewhere: https://github.com/facebook/react-native-websiteIssues concerning the docs are tracked elsewhere: https://github.com/facebook/react-native-website