cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filip Maj (JIRA)" <>
Subject [jira] [Commented] (CB-13241) Potential issue with geolocation when device is set to GPS only
Date Wed, 06 Sep 2017 14:50:01 GMT


Filip Maj commented on CB-13241:

OK, interesting. So [~bowserj] this may be a geolocation plugin issue on Samsung.

[~frontendphil] might as well get the full breakdown to try to get a reproduction case prepped.
So details I need are:
* cordova-android version used
* geolocation plugin version used (looks like 2.4.3)
* device hardware you see the issue on (you've provided four different Samsung Galaxy phone
model numbers for this - thank you)
* what about Android / build version on the above phones?
* one more thing: the final AndroidManifest.xml of your app (or, more generally: I want to
know which permissions you have added to your app. In Android 6+, with the runtime permission
model, I may need you to dig out which permissions you have granted to the application on
each of the devices you see the issue on. On my Pixel, this is under Settings -> Apps ->
<the specific app> -> Permissions).

> Potential issue with geolocation when device is set to GPS only
> ---------------------------------------------------------------
>                 Key: CB-13241
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: 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.
>            Reporter: Phil Lennon
>            Assignee: Filip Maj
> 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.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message