mirror of
https://github.com/keycastr/keycastr.git
synced 2026-05-15 14:15:50 -06:00
[GH-ISSUE #146] Accessibility API access sometimes doesn't work unless using an alias #118
Labels
No labels
bug
compatibility
discussion
documentation
enhancement
help wanted
help wanted
investigation needed
pull-request
release
visualizer
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/keycastr#118
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @luckman212 on GitHub (Oct 20, 2019).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/146
I just downloaded 0.9.7 on a mac mini running 10.15
when I launch it, I get the dialog requesting Accessibility API access
I removed & re-added Keycastr as suggested but the process just repeats
Anyone else having this problem?
@NylonDiamond commented on GitHub (Oct 21, 2019):
Same issue for me as well. I just moved the app to the Documents folder and created an alias to the Applications folder. It works for me for now.
@transducer commented on GitHub (Oct 22, 2019):
The suggestion of @NylonDiamond works. But why? :)
@akitchen commented on GitHub (Oct 24, 2019):
Unsure... It's expected to need to re-grant accessibility API permissions after an update or when the app settings change. This needs to be done by removing the app from the list and re-adding it, not simply re-checking the box.
I haven't been able to test on 10.15 to see if things are significantly different in a way we need to work around. I do know that notarization is increasingly important in macOS Catalina and beyond.
Managing security permissions is an area of KeyCastr I'm keep to improve, and I've been working on code signing and notarization to see if it makes any difference especially for Catalina. But since I'm not able to upgrade yet, I'm limited in being able to test it.
Closing this for now. Next release should be notarized and it will be good to know whether it helps.
@akitchen commented on GitHub (Oct 27, 2019):
I got the app code signed and notarized, and I still see the same issue. And strangely, using an alias seems to work. I'm still on 10.14, so it's not specific to Catalina.
@diegohaz commented on GitHub (Oct 27, 2019):
I'm also having this issue (weirdly got here exactly when @akitchen posted an update lol). Tried creating an alias, but it didn't work for me. Probably I did something wrong.
@akitchen commented on GitHub (Oct 27, 2019):
This problem seemed to fix itself for me after a while, possibly after a restart. I can now use KeyCastr without an alias from its normal place in /Applications
@diegohaz commented on GitHub (Oct 27, 2019):
It worked for me after enabling Input Monitoring:
@WShiBin commented on GitHub (Nov 1, 2019):
@diegohaz thx
@gziolo commented on GitHub (Nov 8, 2019):
@diegohaz, thanks it solved my issue as well 👍
@birkhofflee commented on GitHub (Nov 14, 2019):
Rebooting my macOS solved the issue
@mfekadu commented on GitHub (Feb 16, 2020):
@diegohaz thanks for the tip! It really helped! I hope the README update will help even more people 😄
@elia commented on GitHub (Feb 17, 2020):
Should be fixed by #158, kudos to @mfekadu for putting together the instructions 👍