Fritz, The app does periodically (re)check for CL and auth status -- this isn't the problem. However, the didChangeAuthorizationStatus listening I was not doing, and me thinks that was the missing piece. I'll try that, and many thanks all :-)
Regards, John On Feb 1, 2012, at 9:24 AM, Fritz Anderson wrote: > On 1 Feb 2012, at 2:09 AM, John Michael Zorko wrote: > >> This app requires location services -- the client does not want the app to >> perform it is function if it detects that it's somewhere it's not supposed >> to be. Is it possible for the app to somehow detect when the iOS-supplied >> alert has been dismissed, so it can do it's CL check in case the user tapped >> "Don't Allow"? > > Checking for Core Location, only once, in advance of need, is probably the > wrong approach. The user could authorize or deauthorize CL at times other > than the moment your application happens to load. Make yourself the delegate > of the shared CLLocationManager, and listen for > locationManager:didChangeAuthorizationStatus:. > > If you don't have CL, disable the functions you want to restrict, even if > that means putting a 50% alpha black mask over the whole screen, preferably > with a button to show an explanation of why the app is crippled. Respond > (don't assume) when CL comes back or goes away. > > — F > _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
