[CB-13241] Potential issue with geolocation when device is set to GPS only

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Component/s: cordova-android, cordova-plugin-geolocation

Environment

Reproducible by me on: Samsung Galaxy S5 when phone location settings are set to GPS only.

Error reporting has logged the issue on (based on most first):

Samsung Galaxy S7 (international and European version)
Samsung Galaxy S6 (SM-G920F)
Samsung Galaxy A5 2017 (SM-A520F)
Samsung Galaxy S8 (SM-G950F)
[etc....]

The top 15 devices are Samsung with the exception of the Sony Xperia XA (F3111).

There are other devices on the list but they happen a handful of times so could be false positives or users have poor reception for example.

Of note: Google Pixel and Pixel XL does not appear in the list of devices. I am also unable to reproduce the issue on Nexus 5X.

• Assignee: Joey Robert Bowser
• Reporter: Phil Lennon
• Created: 05/Sep/17 14:23
• Updated: 23/Aug/18 06:45
• Resolved: 25/Sep/17 17:54

Description

Pinging filmaj who asked to be assigned this.

My app uses the Geolocation getCurrentPosition() function on both IOS and Android. I have had an estimated 1.6k Android users unable to get a location with a timeout error code 3. There are no problems on IOS.

I first try to get location with the following settings:

this.geolocationOptionsFirst =

{ enableHighAccuracy: true, maximumAge: 300000, timeout: 10000 }

if that fails I then try again with the following settings:

this.geolocationOptionsSecond =

{ enableHighAccuracy: false, maximumAge: 300000, timeout: 6000 }

The app is failing with a timeout after 16 seconds in total. My testing has made me believe it's something to do with setting phone location settings to GPS only. Please see environment for affected devices.

Happy to provide more information if needed. I am available on the cordova-android Slack channel as frontendphil.