TLDR; How to identify and troubleshoot security prompts that repeat on macOS Monterey 12.3.1 on an Intel MBP?
Fantastical.app (from the Mac App Store) and TV.app (the apple app) will ask multiple times a day for permission to use location data (as in, the dialog box that pops up asking "X would like to use your current location"). I grant them access each time, and also see that they are listed as enabled/authorized for location data in the System Preferences -> Security & Privacy -> Location Services area.
I've tried uninstalling/reinstalling Fantastical.app, but the issue continues. I've also tried unchecking/re-checking the permission of the apps (Fantastical.app, Fantastical Helper.app, TV.app) but the prompts for authorization keep coming back.
I had the Console.app open today and after the issue popped up I went looking through the logs for locationd
log lines. A few that seemed "interesting" or relevant (more log lines below).
locationd denied access to file-read-data
error 15:24:14.047524-0400 kernel Sandbox: locationd(91559) deny(1) file-read-data /Applications/Fantastical.app
From what I gather, which may be incorrect, but locationd
is trying to read data about the app bundle, but fails. I looked at the owner of the /Applications/Fantastical.app/ bundle, and they were root:wheel
, which seems like the default for any app downloaded from the Mac App Store.
locationd recognizing that Fantastical.app wants location data
default 15:24:14.052587-0400 locationd client 'com.flexibits.fantastical2.mac' not authorized for location; not starting yet
This seems like Fantastical is asking for location data, and locationd
is remarking that the app does not have permissions to do so yet.
locationd noting that Fantastical.app now has authorization
default 15:24:17.975759-0400 locationd client 'com.flexibits.fantastical2.mac' authorized for location; starting shortly
default 15:24:17.976041-0400 locationd client 'com.flexibits.fantastical2.mac' authorized for location; starting now, desiredAccuracy, 3000.0, distanceFilter, 1000.0, operatingMode 0, dynamicAccuracyReductionEnabled 0, allowsAlteredAccessoryLocations 0, activityType 0
Here it seems to me that locationd
is now recognizing that I've now authorized Fantastical.app to use my location data (after clicking "allow" in the modal window).
Which seems good until a few moments later.
locationd cannot read (?) /Applications/Fantastical.app
error 15:24:14.459094-0400 kernel 5 duplicate reports for Sandbox: locationd(91559) deny(1) file-read-data /Applications/Fantastical.app
The above log line was followed by locationd logging that the Fantastical.app does not have location permissions after all--one second after I authorized it.
default 15:24:16.052691-0400 locationd {"msg":"client not currently authorized for location; sending error", "client":"com.flexibits.fantastical2.mac"}
I woke up my laptop the next day, and was greeted by this. I had clicked "ok" five or more times before I began recording. This has happened before after I wake the computer from a long sleep.
More logs
Here are the select log lines that seemed related, all together in one codeblock.
error 15:24:14.047524-0400 kernel Sandbox: locationd(91559) deny(1) file-read-data /Applications/Fantastical.app
default 15:24:14.049401-0400 locationd {"msg":"#AutomaticPrompting at subscription", "Client":"com.flexibits.fantastical2.mac", "state":1}
default 15:24:14.049443-0400 locationd {"msg":"Showing #AuthPrompt", "requestType":5, "client":"com.flexibits.fantastical2.mac"}
default 15:24:14.049463-0400 locationd {"msg":"#AuthPrompt AuthorizationRequest completion", "ClientKey":"com.flexibits.fantastical2.mac", "RequestType":"CLClientManager_Type::AuthorizationRequestTypeLegacyAlways"}
default 15:24:14.049496-0400 locationd {"msg":"#AuthPrompt posted", "client":"com.flexibits.fantastical2.mac", "type":"CLClientManager_Type::AuthorizationRequestTypeLegacyAlways"}
default 15:24:14.049782-0400 Fantastical {"msg":"CLClientRequireAgentHandler", "event":"activity", "client":"0x7fb4bc372780"}
default 15:24:14.052587-0400 locationd client 'com.flexibits.fantastical2.mac' not authorized for location; not starting yet
default 15:24:14.457762-0400 Fantastical {"msg":"state transition", "event":"state_transition", "state":"LocationManager", "id":"0x600002aabbc0", "property":"limitsPrecision", "old":0, "new":0}
default 15:24:14.457814-0400 Fantastical {"msg":"state transition", "event":"state_transition", "state":"LocationManager", "id":"0x600002aabbc0", "property":"previousAuthorizationStatus", "old":"NotDetermined", "new":"NotDetermined"}
default 15:24:14.457840-0400 Fantastical {"msg":"state transition", "event":"state_transition", "state":"LocationManager", "id":"0x600002aabbc0", "property":"previousAuthorizationStatusValid", "old":0, "new":1}
default 15:24:14.457859-0400 Fantastical {"msg":"state transition", "event":"state_transition", "state":"LocationManager", "id":"0x600002aabbc0", "property":"isAuthorizedForWidgetUpdates", "old":0, "new":0}
error 15:24:14.459094-0400 kernel 5 duplicate reports for Sandbox: locationd(91559) deny(1) file-read-data /Applications/Fantastical.app
default 15:24:17.975759-0400 locationd client 'com.flexibits.fantastical2.mac' authorized for location; starting shortly
default 15:24:17.976041-0400 locationd client 'com.flexibits.fantastical2.mac' authorized for location; starting now, desiredAccuracy, 3000.0, distanceFilter, 1000.0, operatingMode 0, dynamicAccuracyReductionEnabled 0, allowsAlteredAccessoryLocations 0, activityType 0
default 15:24:17.976435-0400 locationd @ClxClient, register, com.flexibits.fantastical2.mac, accuracy, 3000.0
default 15:24:17.981296-0400 locationd @ClxClient, accuracy, 0, 0, 4, level, Coarse, reg?, 1
default 15:24:16.052691-0400 locationd {"msg":"client not currently authorized for location; sending error", "client":"com.flexibits.fantastical2.mac"}
default 15:24:17.964607-0400 locationd Setting executable: <>, bundle: <com.flexibits.fantastical2.mac>, bundle path: <> authorization to Enabled
error 15:24:17.968260-0400 kernel Sandbox: locationd(91559) deny(1) file-read-data /Applications/Fantastical.app
Any thoughts?
Is there some way to "reset" locationd
to factory settings or equivalent? It seems like it's in a bad state and its configuration is corrupted in some way.
I do not know if it has similar log lines when the TV.app continually asks for location permissions, but my hunch is that they are the same.
Has anyone else had and solved this before?