[
https://issues.apache.org/jira/browse/CB-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096842#comment-15096842
]
Tom Nightingale commented on CB-10338:
--------------------------------------
The geolocation API doesn't work in Chrome either though it works fine in the
stock Android browser.
Seems that this issue is specific to the device that I am using (a Panasonic
Toughpad FZ-X1 running Android 4.2.2).
:-\
In Chrome I do get the following deprecated notice:
{{getCurrentPosition() and watchPosition() are deprecated on insecure origins,
and support will be removed in the future. You should consider switching your
application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for
more details.}}
But that's just a warning and if Crosswalk has already deprecated geolocation
on insecure origins then I wouldn't see the "Searching for GPS" notification in
the status bar.
On an unrelated note: More and more web APIs are requiring secure origins
(Geolocation, Websockets, Service Worker, etc...). Does Cordova have a strategy
to handle this?
> getCurrentPosition() hangs on Android 4.2.2
> --------------------------------------------
>
> Key: CB-10338
> URL: https://issues.apache.org/jira/browse/CB-10338
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Geolocation
> Affects Versions: 2.0.0
> Environment: Android 4.2.2 (running [email protected])
> Reporter: Tom Nightingale
> Labels: android
>
> Neither success or error callbacks are called after calling
> navigator.geolocation.getCurrentPosition().
> Stepping through the plugin with Chrome's Javascript debugger and Android
> Studio's Java debugger shows that the plugin's shim code successfully
> executes the Geolocation 'getPermission' check and returns back to fire the
> shim's success handler (line 31
> [here|https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;a=blob;f=www/android/geolocation.js;h=82e3582e0c225340db44add8fe3ea81256dff03f;hb=57eb4dc550a3d88d3ebbb60a0d6a83d61f898dd7#l31]).
> However the next line which appears to call the platform's native
> getCurrentPosition() just hangs; neither the provided success or error
> callbacks are called. If I try step into that function call with the Chrome
> remote debugger it just jumps to the end of the executing function (line 36 @
> above link). It's as if getCurrentPosition() is a no-op. Chrome's "show
> function definition" functionality isn't able to resolve the definition
> either.
> I wonder if the bug is somewhere in the cordova/modulemapper code? This is an
> area of Cordova I am not familiar with...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
