fulldecent
Feedback: v4.0.6 working for me; for everyone else as well?
🆗
I'm still on an Intel Mac, but version 4.0.6 worked here. The app was placed into /Applications, I checked the bundle, and an adhoc signature had been applied, I removed the quarantine extended attribute, and ran the symlinked executable in /usr/local/bin, the system asked to allow Location Services in a UI prompt, which I did, and then everything worked as it should. 🎉
🆗
Did another test: disabled access to Location Services for CoreLocationCLI v4.0.6, uninstalled v4.0.6, reinstalled it, but then did not remove the quarantine extended attribute. When running CoreLocationCLI in terminal, the result was CoreLocationCLI: ❌ Location services are disabled or location access denied. Please visit System Settings > Privacy & Security > Location Services. I did just that, enabled Location Services for v4.0.6, and then it worked fine, i.e. there is no need to remove the quarantine extended attribute that is added by Homebrew Cask. Since the app is ad-hoc signed locally, this approach should also work on Apple Silicon Macs. On Intel Macs, the app/CLI with the ad-hoc signature is definitely Gatekeeper-friendly. (It also means that if the quarantine XA is not removed manually before running the program for the first time, the macOS UI will stay quiet, i.e. there will be no window asking the user to allow Location Services. The reference to System Settings would then only appear in the Terminal, but that's the important thing anyway.)
MacOS: Tahoe 26.0.1 Chip: Apple M4
Downloaded the latest release. Worked absolutley fine (Run ./CoreLocationCLI.app/Contents/MacOS/CoreLocationCLI. This could be a bit clearer in the documentation, ended up having to see what the old symlink in Homebrew was for it.)
What's blocking the removal of the deprecated tag on Homebrew?
I tested this on an M4 Mac Mini, and this didn't work as smoothly as on an Intel Mac: macOS Gatekeeper didn't want to execute it, neither in the UI nor in Terminal. The only way to get it to work was to run xattr -cr /Applications/CoreLocationCLI.app. (Note: removing only the quarantine extended attribute would surely have also worked.) Then it was fine, and I could allow the app to use Location Services in the UI, and it was auto-enabled in System Settings.
So it seems like an ad-hoc signature won't suffice, unless the extended attributes are cleared as well. Otherwise it won't get past Gatekeeper.
@JayBrown I didn't have any behaviour like this but I also set up the old version of CoreLocationCLI ages ago and may have enabled something. Is there a debug script or something I can use to show you the output of mine?
Yes, I had noticed similar things in the past on my Intel Mac. Once it's enabled for Location Services, the behavior for subsequent updates seems to be different.
I see that the settings preference in System Settings has moved to a different name and I updated this in the README for now.
