[
https://issues.apache.org/jira/browse/CB-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162618#comment-13162618
]
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: https://issues.apache.org/jira/browse/CB-95
> Project: Apache Callback
> Issue Type: Bug
> Components: iOS
> Reporter: Shazron Abdullah
> Assignee: Shazron Abdullah
>
> reported at: https://github.com/callback/callback-ios/issues/1
> by: https://github.com/schmitti12345
> sorry to mention, but
> [#197](https://github.com/phonegap/phonegap-iphone/issues/197),
> [#304](https://github.com/phonegap/phonegap-iphone/issues/304#issuecomment-2460999)
> & [#287](https://github.com/phonegap/phonegap-iphone/issues/283) are still
> there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
