[GH-ISSUE #66] I get catastrophic error encountered even after reinstalling the app #57

Closed
opened 2026-05-05 04:49:15 -06:00 by gitea-mirror · 9 comments
Owner

Originally created by @nikivdev on GitHub (Aug 31, 2016).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/66

I get this screen every time the app starts up now :

2016-08-31 at 18 44

I have activated the accessibility setting for the app and this error is still there.

What should I do?

Originally created by @nikivdev on GitHub (Aug 31, 2016). Original GitHub issue: https://github.com/keycastr/keycastr/issues/66 I get this screen every time the app starts up now : ![2016-08-31 at 18 44](https://cloud.githubusercontent.com/assets/6391776/18137957/e7084424-6faa-11e6-866e-ad1528aaa348.png) I have activated the accessibility setting for the app and this error is still there. What should I do?
Author
Owner

@akitchen commented on GitHub (Aug 31, 2016):

As the instructions in the dialog box indicate, you need to re-add KeyCastr
to the list of apps allowed to control your computer.

Modern versions of OS X require this whenever the settings of the app
change, and we haven't yet gotten around to automating it.

On Wed, Aug 31, 2016 at 9:45 AM, Nikita Voloboev notifications@github.com
wrote:

I get this screen every time the app starts up now :

[image: 2016-08-31 at 18 44]
https://cloud.githubusercontent.com/assets/6391776/18137957/e7084424-6faa-11e6-866e-ad1528aaa348.png

I have activated the accessibility setting for the app and this error is
still there.

What should I do?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/keycastr/keycastr/issues/66, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXHGKRs7J-oduXRdHY2Ka5PnVKuuprXks5qla-bgaJpZM4Jx0tL
.

<!-- gh-comment-id:243849619 --> @akitchen commented on GitHub (Aug 31, 2016): As the instructions in the dialog box indicate, you need to re-add KeyCastr to the list of apps allowed to control your computer. Modern versions of OS X require this whenever the settings of the app change, and we haven't yet gotten around to automating it. On Wed, Aug 31, 2016 at 9:45 AM, Nikita Voloboev notifications@github.com wrote: > I get this screen every time the app starts up now : > > [image: 2016-08-31 at 18 44] > https://cloud.githubusercontent.com/assets/6391776/18137957/e7084424-6faa-11e6-866e-ad1528aaa348.png > > I have activated the accessibility setting for the app and this error is > still there. > > What should I do? > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > https://github.com/keycastr/keycastr/issues/66, or mute the thread > https://github.com/notifications/unsubscribe-auth/AAXHGKRs7J-oduXRdHY2Ka5PnVKuuprXks5qla-bgaJpZM4Jx0tL > .
Author
Owner

@nikivdev commented on GitHub (Aug 31, 2016):

Isn't this the place where you add it?

2016-08-31 at 20 06

I have it ticked and yet the error still shows.

<!-- gh-comment-id:243850185 --> @nikivdev commented on GitHub (Aug 31, 2016): Isn't this the place where you add it? ![2016-08-31 at 20 06](https://cloud.githubusercontent.com/assets/6391776/18140581/763fa604-6fb6-11e6-854e-feaa30bf0a35.png) I have it ticked and yet the error still shows.
Author
Owner

@akitchen commented on GitHub (Aug 31, 2016):

Yes, however you need to remove the icon and re-add it by dragging it in. Un-ticking/re-ticking the box isn't enough, unfortunately.

On Aug 31, 2016, at 11:07, Nikita Voloboev notifications@github.com wrote:

Isn't this the place where you add it?

I have it ticked and yet the error still shows.


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

<!-- gh-comment-id:243894037 --> @akitchen commented on GitHub (Aug 31, 2016): Yes, however you need to remove the icon and re-add it by dragging it in. Un-ticking/re-ticking the box isn't enough, unfortunately. > On Aug 31, 2016, at 11:07, Nikita Voloboev notifications@github.com wrote: > > Isn't this the place where you add it? > > I have it ticked and yet the error still shows. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub, or mute the thread.
Author
Owner

@nikivdev commented on GitHub (Aug 31, 2016):

This works, thank you. This is a really great little utility.

<!-- gh-comment-id:243899983 --> @nikivdev commented on GitHub (Aug 31, 2016): This works, thank you. This is a really great little utility.
Author
Owner

@gozyf commented on GitHub (Nov 26, 2019):

OS Catalina: the same problem, even if I re-add it by dragging, it shows the error

<!-- gh-comment-id:558439958 --> @gozyf commented on GitHub (Nov 26, 2019): OS Catalina: the same problem, even if I re-add it by dragging, it shows the error
Author
Owner

@dtkachev commented on GitHub (Dec 23, 2019):

To resolve this error you need to add permissions in:
Privacy -> Accessibility -> KeyCastr
Privacy -  Accessibility -  KeyCastr
Privacy -> Input Monitoring -> KeyCastr
Privacy -  Input Monitoring -  KeyCastr

<!-- gh-comment-id:568460106 --> @dtkachev commented on GitHub (Dec 23, 2019): To resolve this error you need to add permissions in: Privacy -> Accessibility -> KeyCastr <img width="584" alt="Privacy - Accessibility - KeyCastr" src="https://user-images.githubusercontent.com/2193089/71357492-0c9b1180-2597-11ea-9e9a-4d59a2b8afe5.png"> Privacy -> Input Monitoring -> KeyCastr <img width="581" alt="Privacy - Input Monitoring - KeyCastr" src="https://user-images.githubusercontent.com/2193089/71357491-0c9b1180-2597-11ea-9385-f4ed19b33e7c.png">
Author
Owner

@fjoachim commented on GitHub (Feb 9, 2020):

Seeing the error dialog even after adding KeyCastr to both Accessibility and Input Monitoring on macOS 10.15.4.

<!-- gh-comment-id:583881663 --> @fjoachim commented on GitHub (Feb 9, 2020): Seeing the error dialog even after adding KeyCastr to both **Accessibility** and **Input Monitoring** on macOS 10.15.4.
Author
Owner

@akitchen commented on GitHub (Feb 9, 2020):

Input Monitoring shouldn't be necessary, it works fine for me without it.

I have seen this issue go away in Catalina after rebooting, but I'm not sure that's the solution. Perhaps those changes in settings aren't always applied immediately.

<!-- gh-comment-id:583890893 --> @akitchen commented on GitHub (Feb 9, 2020): Input Monitoring shouldn't be necessary, it works fine for me without it. I have seen this issue go away in Catalina after rebooting, but I'm not sure that's the solution. Perhaps those changes in settings aren't always applied immediately.
Author
Owner

@akitchen commented on GitHub (Feb 23, 2020):

On Catalina, I did the following to reset the permissions:

  • remove KeyCastr from the list of applications with Accessibility permissions
  • double-check that KeyCastr isn't in the list of applications with Input Monitoring permissions
  • reboot to ensure all internal permissions updates are applied/synchronized

After rebooting, when starting KeyCastr it shows the error screen and offers to open the Security & Privacy preferences pane as expected. MacOS also displays an additional prompt about Input Monitoring. KeyCastr is already listed in the Input Monitoring list, but isn't selected. After checking the box next to KeyCastr in the Input Monitoring list, everything works fine on next app startup.

It should be possible to refactor the app startup routine to handle this more gracefully, which we'll do in an upcoming release.

<!-- gh-comment-id:590103388 --> @akitchen commented on GitHub (Feb 23, 2020): On Catalina, I did the following to reset the permissions: - remove KeyCastr from the list of applications with Accessibility permissions - double-check that KeyCastr isn't in the list of applications with Input Monitoring permissions - reboot to ensure all internal permissions updates are applied/synchronized After rebooting, when starting KeyCastr it shows the error screen and offers to open the Security & Privacy preferences pane as expected. MacOS also displays an additional prompt about Input Monitoring. KeyCastr is already listed in the Input Monitoring list, but isn't selected. After checking the box next to KeyCastr in the Input Monitoring list, everything works fine on next app startup. It should be possible to refactor the app startup routine to handle this more gracefully, which we'll do in an upcoming release.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/keycastr#57
No description provided.