github-starred/keycastr

Fork 0

mirror of https://github.com/keycastr/keycastr.git synced 2026-05-15 14:15:50 -06:00

[GH-ISSUE #92] Keycastr can't acquire permissions #78

New issue

Closed

opened 2026-05-05 04:51:47 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 04:51:47 -06:00

Owner

Originally created by @achikin on GitHub (Jul 17, 2017).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/92

When I start an application this screen pops up
screen shot 2017-07-17 at 13 20 47
When I press Grant Access button the password prompt appears and when I enter my password Catastrophic error screen appears again and the process repeats itself.

KeyCastr version 0.9.4 installed with brew cask.

MacOSX 10.12.5

Originally created by @achikin on GitHub (Jul 17, 2017). Original GitHub issue: https://github.com/keycastr/keycastr/issues/92 When I start an application this screen pops up <img width="423" alt="screen shot 2017-07-17 at 13 20 47" src="https://user-images.githubusercontent.com/611419/28268472-15c318ae-6b07-11e7-9f45-31df67c10da0.png"> When I press `Grant Access` button the password prompt appears and when I enter my password `Catastrophic error` screen appears again and the process repeats itself. KeyCastr version 0.9.4 installed with brew cask. MacOSX 10.12.5

gitea-mirror closed this issue

2026-05-05 04:51:50 -06:00

gitea-mirror commented

2026-05-05 04:51:54 -06:00

Author

Owner

@achikin commented on GitHub (Jul 17, 2017):

I managed to reproduce the issue on the app downloaded directly from github.

@achikin commented on GitHub (Jul 17, 2017): I managed to reproduce the issue on the app downloaded directly from github.

gitea-mirror commented

2026-05-05 04:51:55 -06:00

Author

Owner

@achikin commented on GitHub (Jul 17, 2017):

Managed to fix that partially by going to Security & Privacy -> Accessibility and adding KeyCastr to the list manually

@achikin commented on GitHub (Jul 17, 2017): Managed to fix that partially by going to `Security & Privacy` -> `Accessibility` and adding KeyCastr to the list manually ![screen shot 2017-07-17 at 16 17 13](https://user-images.githubusercontent.com/611419/28269720-b6b2d3b8-6b0b-11e7-836d-1bc37df0a489.png)

gitea-mirror commented

2026-05-05 04:51:56 -06:00

Author

Owner

@tsheaff commented on GitHub (Jul 19, 2017):

This is a pretty fundameltal issue, is it recent?

@tsheaff commented on GitHub (Jul 19, 2017): This is a pretty fundameltal issue, is it recent?

gitea-mirror commented

2026-05-05 04:51:58 -06:00

Author

Owner

@achikin commented on GitHub (Jul 20, 2017):

I can't tell exactly. I've installed it for the first time 3 days ago.

@achikin commented on GitHub (Jul 20, 2017): I can't tell exactly. I've installed it for the first time 3 days ago.

gitea-mirror commented

2026-05-05 04:52:00 -06:00

Author

Owner

@akitchen commented on GitHub (Jul 20, 2017):

Changes in recent versions of OS X / macOS are probably a factor here. For example, homebrew cask currently isn't able to automate these permissions either, so one must add the app to the accessibility list manually.

On Jul 20, 2017, at 10:47, Anton Chikin notifications@github.com wrote:

I can't tell exactly. I've installed it for the first time 3 days ago.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@akitchen commented on GitHub (Jul 20, 2017): Changes in recent versions of OS X / macOS are probably a factor here. For example, homebrew cask currently isn't able to automate these permissions either, so one must add the app to the accessibility list manually. > On Jul 20, 2017, at 10:47, Anton Chikin <notifications@github.com> wrote: > > I can't tell exactly. I've installed it for the first time 3 days ago. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub, or mute the thread. >

gitea-mirror commented

2026-05-05 04:52:02 -06:00

Author

Owner

@akitchen commented on GitHub (Jul 22, 2017):

The README has been updated to address this.

@akitchen commented on GitHub (Jul 22, 2017): The README has been updated to address this.