Geolocation timed out, code 3

[avdept]

Description

I have geolocation running in my app, followed examples described in docs. IOS version works fine, android however works only on non xiaomi devices. I tried on 2 xiamomi devices, and got Location request timed out error. While on samsung devices it works fine.

Reproduction

navigator.geolocation.getCurrentPosition(
            (position) => {
                let initialPosition = JSON.stringify(position);
                console.log(initialPosition);
            },
            (error) => console.log(JSON.stringify(error)),
            {enableHighAccuracy: Platform.OS != 'android', timeout: 2000, maximumAge: 2000 }
        );

Solution

Need to find a way either provide reason why timed out, or just fix it.

Additional Information

• React Native version: 0.42
• Platform: Android
• Operating System: Mac OS
• Dev tools: Android SDK v23

[booboothefool]

Need to check permissions on some devices before requesting navigator.geolocation.getCurrentPosition(...):

Use https://github.com/lucasferreira/react-native-android-permissions or https://facebook.github.io/react-native/docs/permissionsandroid.html

[brunolemos]

Duplicated of #7495

[pewh]

Have same issue, too. Check permission is not enough. See my answer at #7495 (comment)

[hramos]

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

• Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
• If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
• Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

[nicotroia]

For anyone else struggling with this issue on android, try removing the maximumAge: 2000 option parameter. This option was causing geolocation to either timeout or crash the app.

I'm running react-native 0.46.4 btw.

[imyagnesh]

I am also struggling for the same issue. let me know if anybody have solution for this.

I am using RN 0.48

[cristisavaintelligentbee]

Has anybody find a solution for this ?

[kelset]

Duplicate #7495

[milon87]

when working with map:

1. Set permission if you build app with SDK >23 (android)
2. if enableHighAccuracy is on, in that case, check if your phone is Enabled.

[ajRiverav]

For those of you who still are experiencing this issue, I was able to solve it by omitting the parameter maxAge, e.g. {enableHighAccuracy: true, timeout: 5000}).

At least I can confirm this with API level 23 and RN 0.51. I also used had

    <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
    <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />

in the AndroidManifest.xml file.

About not using maxAge: a pull request mentions an issue with it (Clintal/react-native-picker@320003e)

[digvijayMobantica]

{ enableHighAccuracy: false, timeout: 20000, maximumAge: 1000 },

Make "enableHighAccuracy: false" works for me