-
Notifications
You must be signed in to change notification settings - Fork 23
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
Big Sur #26
Comments
I'm still using this macro on a daily basis and everything is working great with the latest KM version. I'm still running on Catalina so I suspect it's a macOS issue. |
I can get it to run but not find any of the macros in KM... |
@taylornd yeah that's where I get to as well |
Any news on this using Big Sur? Keen to try it but have already upgraded so no going back! |
I use it on Bug Sur, no issues. |
Really? Have you changed anything or done anything to get it to work? I did a fresh install of everything and can get it to run but it doesn't find any macros... |
It is working fine! Many thanks. |
Can you share logs what happens when you search for macros?
Is what I get. |
I get the below. I think it is something to do with automation permissions but I need to find a way for Alfred/KM to request them. What does your Alfred automation permissions look like? e.g. I think it needs system events [12:55:24.733] Logging Started... |
Any idea how to get Alfred/KM to request access to system events? |
Don't know but someone at https://www.alfredforum.com might know or https://forum.keyboardmaestro.com/latest |
I get this error: alfred_workflow_bundleid is not set, alfred_workflow_cache is not set, alfred_workflow_data is not set |
What is strange is that an old version of this workflow seems to work fine. |
I just installed the workflow in Big Sur and it works fine. |
do you have an M1 apple silicon machine? |
No - I have a Hackintosh with an Intel i7 processor. |
m1 mac mini here and big sur - all required permission from above set but unfortunately it does not work. Same settings under old macbook pro 15 2017 and it work flawlessly. Any clue? |
Perhaps try to recompile the go program yourself and run that? |
How? I am not a programmer;) Any instructions? |
I think this is the issue - the go program doesn't work on apple silicon. |
For anyone else struggling, what fixed it for me was installing the workflow, choosing Open in Finder from Alfred's preferences, and right-clicking the "keyboard-maestro" executable. Once I confirmed that I wanted to open it, I was able to run the workflow's command ("km"); it prompted me one more time, but now it's working great. :) |
Has anyone got this working with an M1 Mac? |
Damn. Does not work either for me;/ This is what I'm getting when clicking executable file:
Any idea? |
@almeco I can't confirm this now, but if I ever get my hands on an M1 I'll give it a try! |
I’m using an M1 and I had the exact same issue. When executing the executable, I got the exact same message as @almeco , except that it ends with: Saving session...completed. But now, while writing this I took another look at: Now it works However I'm sure, the checkmark wasn't available when I tried to fix this a few weeks ago. I don't know what made it appear. |
Strange - I'm on M1 and Alfred has access to Keyboard Maestro but it still doesn't work |
Thanks for this - got mine working on a 2015 Catalina MacBook Pro where it was previously stuck in the permission loop. If anyone makes it to this step but still has errors - try holding down |
Mine was not working on my old 2012 Macbook running Catelina, it just wouldn't trigger anything if I used I fixed it by downloading I then tried to activate it again with The first time I just received this message (Notice no Then went to Security and Privacy settings and clicked Then ran it again and got this pop up and which now had an Now all working fine. |
This worked for me. However being on an M1 MacBook Air, I needed to install Rosetta 2 first. The Go binary doesn't run natively on Apple Silicon. |
Works fine for me in Monterey. You just need to validate the binary as "safe" since the developer cannot be verified.
|
If the above is not working for you (maybe you don't have the necessary admin rights since you might have a company notebook). Just clearing the quarantine flag from the workflow files (in a terminal with "xattr -d com.apple.quarantine *" in the workflow dir) solves the issue as well without admin rights. |
Fyi, if none of the above solutions work for you, this workflow may be a good alternative: https://www.thoughtasylum.com/alfred/alfred_conductor_for_keyboard_maestro/#download-conductor= |
This worked for my new Macbook Air M2 chip that's running Ventura (13.2.1). I did have to install Python 3, which it walked me through how to do. |
You posted it two years ago, but it still helpful in 2023, thank you dude 🙇 |
Hi, anyone got this working in Big Sur at all ?
Have it working in Catalina following the advice in #25 but no luck with Big Sur.
Is it broken or just more macOS permission issues ?
Thanks
The text was updated successfully, but these errors were encountered: