-
-
Notifications
You must be signed in to change notification settings - Fork 1
Permission issues #9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Found your answer to what seems to be the same problem in a closed issue here. IIUC, you are saying to open a finder window, open the calendar permissions in system settings and manually drag and drop src/calpp into it. I tried doing that but it doesn't do anything. |
Hey @glpayson Thank you for the detailed report. I'm unsure what changed in macOS 14 regarding the process of manually granting full calendar access to an app. However, it's clear that the process has become much stricter. Perplexity suggests that any app that has requested access at least once should appear in the list. Alas, I don't see either Alfred or Calendarpp in your list, despite Alfred's response indicating calpp attempted to request access and failed.
Nvm, it seems to you've already checked that.
Since running the AppleScript via iTerm caused it to appear in your list of apps that are eligible to request access, you could try a hacky approach. Create a Run Script object (triggered with a temporary keyword input). Then, paste the terminal command you already used into the script. This way, macOS should recognize Alfred as the application requesting permissions instead of iTerm. Or just connect a temporary keyword input to the existing Run Script object that has the note "Open Calendar at Date". ![]() Another idea: Perhaps trying to open the calpp executable directly from the finder will make it show up?
This just means that the quarantine has already been removed, so that's expected.
I'm also just noticing this error, but I think this is because calpp never got around to creating the image before bailing. You can keep an eye on the cache btw. via Also new is the warning visible in your GIF that the workflow has been edited since showing the Dialog. I suspect this being due to Alfred 5.5.1 fixing a long standing bug that required refreshing the workflow manually after modifying an environment variable.
Probably also unrelated, but another thing to keep an eye out for if the problem persists. |
Hi @zeitlings, thanks so much for your quick and detailed response. Your 'hacky approach' worked, with an extra step. Let me write out the steps I took so other people that run into this issue can follow along:
Thanks again for your prompt help with this. I'm looking forward to using the workflow. |
Thanks for elaborating on your solution! |
Hello, I was trying to install and try out your workflow but I'm running into permission problems.
I downloaded Calendar++ v2.1.1 on Sonoma 14.2.1. I'm using Alfred 5.5.1. I normally run Fish shell but I changed with
chsh -s /bin/zsh
before installing.I imported the workflow, clicked install, typed 'cc ' and got a permission popup.
Clicking "Grant Permission" plays a warning noise and causes the pop up to appear again. Clicking "Grant Permission" a second time causes the popup to disappear and nothing else to happen. When I type 'cc ' again I see:
Here is the debugger output:
If I navigate to the folder, I can see that it seems like "allowed" is set to 1 in info.plist (see screenshot).
Running
xattr -d com.apple.quarantine ./src/calpp
manually gives me:No such xattr: com.apple.quarantine
I'm able to manually run the calendar .scpt's. Doing so prompts me to give Calendar permission to iTerm. I never got any similar request for permission to Calendar for Alfred.
If I look at System Settings > Privacy & Security, Alfred has permission on Contacts, Automation, Files and Folders, Full DIsk Access, and Accessibility but not Calendars. I don't see any option to manually add Alfred to the Calendar permissions and there doesn't seem to be a way to do it from the command line afaict.
Any idea what I'm missing?
The text was updated successfully, but these errors were encountered: