[ 
https://issues.apache.org/jira/browse/CB-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981823#comment-13981823
 ] 

Ryan Archer commented on CB-6529:
---------------------------------

Also I should mention that Geolocation call never works successfully the first 
time on my testing. The whole page/screen/view needs to be (force) refreshed 
for the function call to work successfully. Right now I have a timeOut going to 
onError which then calls the refresh. Makes the page look a bit broken.

> Cordova geolocation API issue
> -----------------------------
>
>                 Key: CB-6529
>                 URL: https://issues.apache.org/jira/browse/CB-6529
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CordovaJS, iOS
>    Affects Versions: 3.4.0
>         Environment: Testing on iOS7 on iPad 3 and using iOS Simulator 
> provided by Xcode 5.1
>            Reporter: Ryan Archer
>              Labels: features, javascript, newbie
>
> Hi everyone! Shazron has recommended I post the issue I am experiencing here. 
> I am using Cordova 3.4 and calling Geolocation API.
> It is never successful the first time around, it always times out throws 
> onError and I have to refresh the whole page for it to work the second time 
> around. I am not calling geolocation on the onDeviceReady as I am calling the 
> API on a separate view (multi page app with JQM) and also Google Maps API. If 
> I call external scripts (google maps) on the first load, Apple App store will 
> be sure to reject my app. Here is my stackoverflow post on it: 
> http://stackoverflow.com/questions/23292335/why-does-phonegap-geolocation-onsuccess-never-fires-the-first-time-around
>  
> I really hope there is something missing here and I’ve forgot to implement it 
> or something. I'm not the only one with the problem. It's happening on 
> Android environment too. I hope there is a way we can make it more reliable 
> and not rely on a refresh action.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to