3

Does any one know why the location indicator stay on for certain bundle identifer vs. the others? I am using an Apple sample LocateMe app, installed on my iOS device running version 5.0.1. When I'm using an old bundle identifier, the location indicator stays on the status bar, after the CLLocationManager stopUpdatingLocation is being call.

But, when I'm using the same exact app, with the only difference being a new bundle id, the app works as expected and the location indicator disappear once the stopUpdatingLocation is being called.

Did anyone experience this problem or can explain it?

Gilad M
  • 942
  • 10
  • 12

2 Answers2

7

I finally figured that if I reset the Location Warnings from the Settings, the bug disappear.

From your iOS Settings select General | Reset | Reset Location Warnings. This will reset the warning to all the apps. This mean that the next time you start an app that requires location, the iOS will prompt you with the location permission dialog. Select 'Reset Warnings' from the action sheet.

When running the app again, the iOS will prompts you with the location permission dialog (if it doesn't - repeat the process above to reset the location warnings). After selecting yes, the app behaves as expected, and the location indicator disappears after few seconds.

Gilad M
  • 942
  • 10
  • 12
  • 1
    This bug is still present in iOS6. Thanks for the solution, that works for me on iOS5 and iOS6. – emrys57 Jan 23 '13 at 16:20
  • Gilad, you sir are my new hero. I've been fighting with this dang thing for most of the day! @emrys57, I too can confirm this bug does still existing in iOS 6... :/ – JRG-Developer Feb 26 '13 at 07:35
  • This is very weird, but after try everything, reset the warnings was also my solution, and I'm using iOS 7.1 with Xcode 5.1 – Thiago Pires Mar 10 '14 at 01:19
1

Did you try to also stopMonitoringSignificantLocationChanges ? It worked for me.

P.O
  • 101
  • 1
  • 4
  • Yes, I did try stopMonitoringSignificantLocationChanges and it does not work. The different behavior depends on the BundleId – Gilad M Apr 19 '12 at 21:47