-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
react-native-geolocation-service throwing internal error occurred only for few android devices #408
Comments
@kirannaikI I'm facing the same issue. Have you found a solution? |
I'm also facing the same issue. Recently after upgrading into API Level 33. It works without issue while using the app in mobile network. But, If I use the app in the wifi connection it throws 'could not invoke : rnfusedlocation.getcurrentposition' error and crashes |
same here |
2 similar comments
same here |
same here |
Same for me |
same here. only occurs on some phones. any updates? |
In my case function getCurrentPosition returned "Internal error occurred" when geolocation was turned off in parent control. |
Environment
System:
OS: Windows 10 10.0.19045
CPU: (8) x64 Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz
Memory: 1.07 GB / 15.29 GB
Binaries:
Node: 14.18.1 - C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 6.14.15 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: Version 2020.3.0.0 AI-203.7717.56.2031.7784292
Visual Studio: Not Found
Languages:
Java: 15.0.2
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.66.0 => 0.66.0
react-native-windows: Not Found
npmGlobalPackages:
react-native: Not Found
Platforms
Android only
Versions
Please add the used versions/branches
Description
React native geolocation service plugin issue: geolocation getCurrent position throwing error
Reproducible Demo
Provide a detailed list of steps that reproduce the issue.
Expected Results.
throwing error: internal error occurred
The text was updated successfully, but these errors were encountered: