incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Ambrus (JIRA)" <>
Subject [jira] [Commented] (CB-1603) Compass / Geolocation issue on iOS 6 (iPhone)
Date Mon, 15 Oct 2012 08:36:03 GMT


Martin Ambrus commented on CB-1603:

Michal, I've never done any XCode development myself, so I don't even know how to set up a
basic project with webview. On top of that, the time it would take me to learn this is too
long for me to spend at work, as I don't have XCode at home.

Would you be able to create such a sample project and attach it here? I could then try it
out on our iPhone and possibly also report the bug to jQuery Mobile with the project attached.

Thanks for all your help so far!
> Compass / Geolocation issue on iOS 6 (iPhone)
> ---------------------------------------------
>                 Key: CB-1603
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 2.1.0
>         Environment: iPhone 5, iOS 6
>            Reporter: Martin Ambrus
>            Assignee: Shazron Abdullah
>            Priority: Critical
>              Labels: geolocation, location
>             Fix For: 2.2.0
> Applications targeted for iPhone (iOS 4.3+) using Cordova 2.1 and developed in XCode
4.5 automatically turn on Compass / Geolocation. This is true only for devices that have iOS
6 installed. User is never asked if they want to reveal their location to the app, so it's
probably the Compass plugin kicking in.
> What we see is the compass arrow on the right-hand top side of iPhone screen (status
bar). When the application closes, arrow disappears.
> This is an issue for us, as it drains considerably more battery than version running
on iOS 5.1, where this problem does not exist.
> We have tried to remove all - Location, Compass and GeoLocation plugins from the Cordova.plist
to no avail.

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

View raw message