incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Romalewski (Commented) (JIRA)" <>
Subject [jira] [Commented] (CB-95) .watchPosition & .getCurrentPosition still timeouts
Date Mon, 05 Dec 2011 05:57:39 GMT


Steven Romalewski commented on CB-95:

As far as I can tell, adding 
    [self.locationManager stopUpdatingLocation];
to Location.m doesn't fix anything.  (This is @mschulkind's fix for #197 above.)  Unless I'm
doing something wrong, when I rebuild Phonegap 1.1.0 after adding this line, watchPosition
still fails to get a position on subsequent calls (it works the first time, but then if I
call it again, it doesn't fire at all and I have to rely on setting a timeout in order to
force my app to get a position).  

I'm going back to @paulj 's approach of adding "this.stop()" to phonegap.js.  Even though
this keeps calling watchPosition and therefore wasting battery power (even though I've cleared
the watchID), at least it seems to force watchPosition to behave like it should.

But "[self.locationManager stopUpdatingLocation];" doesn't seem to have any affect at all.
> .watchPosition & .getCurrentPosition still timeouts
> ---------------------------------------------------
>                 Key: CB-95
>                 URL:
>             Project: Apache Callback
>          Issue Type: Bug
>          Components: iOS
>            Reporter: Shazron Abdullah
>            Assignee: Shazron Abdullah
> reported at:
> by:
> sorry to mention, but [#197](,
[#304]( &
[#287]( are still there.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message