caleb531 / open-conference-url

An Alfred workflow to open the Zoom/Meet/etc. URL for your next meeting
MIT License
46 stars 6 forks source link

Coudn't add permission on macOS Sonoma #27

Closed galillei closed 1 year ago

galillei commented 1 year ago

Hi I tried to use your workflow, but on the step to give permissions for the workflow I am not able to do it. I just don't see alfred in the calendar's permission options

Screenshot 2023-10-02 at 08 53 37
caleb531 commented 1 year ago

@elephant87 Hm, have you tried running the conf keyword at least once to see if you can trigger the macOS permission prompt within Alfred? I would think that is the only way to trigger Alfred's request for calendar access.

tasbouz commented 1 year ago

@caleb531 Upon running the conf keyword the following message comes up:

Screenshot 2023-10-03 at 09 17 25

And when I click OK it opens the the Privacy & Security panel in Settings but no option to add Alfred is given.

image

I recall that in previous macOS there were options to manually add application in Privacy & Security but in Sonoma it seems that this option is not there anymore. Maybe a solution is to make Alfred ask for calendar permissions directly (and not through a workflow) ?

galillei commented 1 year ago

@elephant87 Hm, have you tried running the conf keyword at least once to see if you can trigger the macOS permission prompt within Alfred? I would think that is the only way to trigger Alfred's request for calendar access.

Yes, I did, but unfortunately I didn't see any options to add alfred to calender as described below

caleb531 commented 1 year ago

@elephant87 @tasbouz That "Access must be given" permission prompt is a custom prompt from the default AppleScript-based mode, but you can bypass that custom prompt entirely by using the icalBuddy integration:

  1. brew install ical-buddy
  2. Enable the "Use icalBuddy" setting in the workflow configuration

This should also be a little more performant as well when fetching events. But in the meantime, please try the below beta version of the workflow (which has the custom prompt removed) to see if that fixes the default (non-icalBuddy) mode:

https://github.com/caleb531/open-conference-url/releases/tag/v7.1.2-beta.1

tasbouz commented 1 year ago

@caleb531 Tried the beta version. I don't get the prompt anymore, however I don't think the workflow can actually see the calendars. I created an event in my calendar to check it out however it could not find it:

[06:48:32.845] Open Conference URL[Script Filter] Queuing argument '(null)'
[06:48:33.282] Open Conference URL[Script Filter] Script with argv '(null)' finished
[06:48:33.289] Open Conference URL[Script Filter] {
  "items": [
    {
      "title": "No Results",
      "subtitle": "No meetings for today",
      "valid": "no"
    }
  ]
}
galillei commented 1 year ago

yes, the same behavior after updated to beta. I definitely has meetings today, but workflow doesn't see it

caleb531 commented 1 year ago

@elephant87 Well, the workflow is designed to only show calendar events with a Zoom/Meet/Teams URL somewhere in the invite. If a calendar event has no meeting URL, it will not be counted.

I'm still looking into this, so please bear with me! But I definitely want to get it fixed if I can!

caleb531 commented 1 year ago

@elephant87 @tasbouz Good news! I figured out the issue, and was able to replicate the macOS permissions prompt for the default AppleScript-based mode. Please try the following beta and let me know how it works for you:

https://github.com/caleb531/open-conference-url/releases/tag/v7.1.2-beta.2

Here's the prompt I received. I think there might still be an issue with the prompt not triggering for the icalBuddy mode, but it should be fixed for the default AppleScript mode:


Screenshot 2023-10-04 at 3 45 51 PM
galillei commented 1 year ago

yes-yes-yes

it works now as a charm!

galillei commented 1 year ago

Thank you very much!

tasbouz commented 1 year ago

It works! You're the best.

caleb531 commented 1 year ago

Aw thanks for the kind words! Glad the workflow is working well now.

And with that, I've just pushed the stable v7.1.2 release (same contents as beta 2, but just in case you want to be on a stable release with a seal of approval:

https://github.com/caleb531/open-conference-url/releases/tag/v7.1.2

Since the issue is resolved, I'll be closing this thread now. But please reach out if you run into any more snags!