[
https://issues.apache.org/jira/browse/CB-13241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174867#comment-16174867
]
Phil Lennon edited comment on CB-13241 at 9/21/17 2:42 PM:
-----------------------------------------------------------
Please excuse the delay in responding. I missed the notification in my email.
Marked as high priority so shouldn't happen again.
Just to address the points so far:
In my own testing, I spotted a situation where the app could request the
geolocation up to 3 times in parallel. I have resolved this with a new version
deployed to play store today. Sadly I should have spotted this during the
original testing. I'll post another comment if the error reports significantly
drop from new version onwards.
[~bowserj] Error tracking is reporting users browser/webview as "Chrome Mobile"
with version "60.0.3112" (and older versions) so I assumed there wasn't a
special Samsung Webview?
[~jcesarmobile] The only permission missing is
"android.permission.ACCESS_LOCATION_EXTRA_COMMANDS" which seems to be redundant
for Cordova (based on this stack overflow link)
https://stackoverflow.com/questions/9917888/android-access-location-extra-commands-permission-uses.
[~filmaj] Thanks for testing this out. My current thought is to ask users to
change their location settings to high accuracy as everything seems to works
fine over repeated attempts. The sheer volume of error reports is still
baffling if Cordova is working as expected.
was (Author: frontendphil):
Please excuse the delay in responding. I missed the notification in my email.
Marked as high priority so shouldn't happen again.
Just to address a few other points first:
In my own testing, I spotted a situation where the app could request the
geolocation up to 3 times in parallel. I have resolved this with a new version
deployed to play store today. Sadly I should have spotted this during the
original testing. I'll post another comment if the error reports significantly
drop from new version onwards.
[~bowserj] Error tracking is reporting users browser/webview as "Chrome Mobile"
with version "60.0.3112" (and older versions) so I assumed there wasn't a
special Samsung Webview?
[~jcesarmobile] The only permission missing is
"android.permission.ACCESS_LOCATION_EXTRA_COMMANDS" which seems to be redundant
for Cordova (based on this stack overflow link)
https://stackoverflow.com/questions/9917888/android-access-location-extra-commands-permission-uses.
[~filmaj] Thanks for testing this out. My current thought is to ask users to
change their location settings to high accuracy as everything seems to works
fine over repeated attempts. The sheer volume of error reports is still
baffling if Cordova is working as expected.
> Potential issue with geolocation when device is set to GPS only
> ---------------------------------------------------------------
>
> Key: CB-13241
> URL: https://issues.apache.org/jira/browse/CB-13241
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
