We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Run npx react-native info in your terminal and copy the results here.
npx react-native info
Is this issue related to Android, iOS, or both ?
Please add the used versions/branches
While trying to fetch the current location in ios device, latitude is coming as 0 whereas longitude has a valid value
Provide a detailed list of steps that reproduce the issue.
Excepting both longitude & latitude to have a valid value instead of 0
The text was updated successfully, but these errors were encountered:
Hi @Agontuk Could you please help here, as there are quite frequent occurrences of this issue in our production environment
Sorry, something went wrong.
Since last 3 month, we are also face this issue for IOS Device.
"react-native-geolocation-service": "5.3.0", "react-native": "0.67.3",
Hello @Agontuk This issue has frequent occurrences, please help here.
@anmolx123 @amankalra4 @khushbujilka22 did you get any solution for this issue
Any luck on this?
No branches or pull requests
Environment
Run
npx react-native info
in your terminal and copy the results here.Platforms
Is this issue related to Android, iOS, or both ?
Versions
Please add the used versions/branches
Description
While trying to fetch the current location in ios device, latitude is coming as 0 whereas longitude has a valid value
Reproducible Demo
Provide a detailed list of steps that reproduce the issue.
{
enableHighAccuracy: true,
timeout: 15000,
maximumAge: 10000,
distanceFilter: 50,
accuracy: {
ios: 'best'
}
}
Expected Results
Excepting both longitude & latitude to have a valid value instead of 0
The text was updated successfully, but these errors were encountered: