search

milgra / macmediakeyforwarder

Media Key Forwarder for iTunes and Spotify
The Unlicense
1.26k stars 85 forks source link

App not responding with 3.0 and macOS Catalina #92

Closed quentinlesceller closed 5 years ago

quentinlesceller commented 5 years ago

Not sure if there is any logs that I can use but the app stopped responding when I updated it to 3.0 on macOS Catalina.

2.8 worked fine.

Let me know if I can anything to help debug this.

tomkidd commented 5 years ago

Yeah I just ran into this too and I can't help but wonder if the issue is that iTunes doesn't exist anymore :)

egla89 commented 5 years ago

Not sure if there is any logs that I can use but the app stopped responding when I updated it to 3.0 on macOS Catalina.

2.8 worked fine.

Let me know if I can anything to help debug this.

Does it stop working, or does it not start? You need to launch it with CTRL+Click at first launch to allow it to run

quentinlesceller commented 5 years ago

Does it stop working, or does it not start? You need to launch it with CTRL+Click at first launch to allow it to run

As mentioned above, for some reasons 2.8 worked. Upgraded with brew to 3.0 and suddenly app stop responding when launched.I'll post more debug Xcode log here.

quentinlesceller commented 5 years ago

I don't see any logs that could help. I assume it's a commit after https://github.com/milgra/macmediakeyforwarder/tree/c110aa97312874980dde84d79ff8e67f1feca94f. I've reverted to 2.8 (built locally) and it works fine.

netsap commented 5 years ago

I'm facing the same issue.

netsap commented 5 years ago

I managed to fix the issue by deleting and re adding the app in the accessibility view, adding the app to launch at login and restarting my laptop.

quentinlesceller commented 5 years ago

Same here thanks @netsap ! Closing.

petr-fiala commented 4 years ago

Issue still exists in 3.1 on Catalina, app not responding... Reinstalling app/removing from security>accessibility doesn't help. Downloading older 2.8 solves the problem. Issue shouldn't be closed.

krunk4ever commented 4 years ago

Couldn't get it working either, tried with both the latest version 3.1 as well as 2.8. Kept getting the Not responding error even after granting accessibility privilege for the app. Ended trying an alternative beardedspice which worked for me.