mirror of
https://github.com/keycastr/keycastr.git
synced 2026-05-15 14:15:50 -06:00
[GH-ISSUE #160] "Catastrophic Error Encountered" dialog gets in the way of Input Monitoring permissions dialog #131
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#131
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 @brandonlind on GitHub (Mar 26, 2020).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/160
I've used
homebrew(v2.2.11; core revision 26e1, cask revision 07e7f1) to install the most recent version of KeyCastr (v0.9.8). I'm running macOS 10.15.3 on a 2019 15-inch 8-core MacBook Pro.However, when I open KeyCastr I get a pop-up that says Catastrophic Error Encountered (first screenshot below).
I've tried uninstalling via
homebrew+ removing from SysPrefs>Privacy>Accessibility before reinstalling and reopening, but I get the same message. I've tried removing from Accessibility and readding, but get the same message. In both cases, KeyCastr has had Accessibility access (it has a blue check mark), despite error message (first screenshot).I can't seem to add it to Input Monitoring (see second screenshot), because there is no
+option.The recommendation from 2shortplanks in #89 did not work (dragging and dropping KeyCastr.app from
/Applicationsinto SysPrefs>Privacy>Accessibility./Applicationsis where I can see the app being removed and added byhomebrewvia an open Finder window. Also, mac won't let me drag app into SysPrefs>Privacy>InputMonitoring.Any ideas on how to fix? Thanks in advance!
@ekilah commented on GitHub (Mar 27, 2020):
i'm having the same issue with a fresh install of the 0.9.8 release.
I had 0.9.6 for a long time but it was not working properly this morning (the cast popup would not appear reliably, and would sometimes pop up with lots of keystrokes from several seconds ago occasionally). 0.9.6's update window was experiencing an issue, so I came to download it directly, replaced it with 0.9.8 when dragging to
/Applications, and then ran into this error.OSX 10.13.6 (17G65), 2017 MBP
hope that extra info helps?
@brandonlind commented on GitHub (Mar 31, 2020):
After installing the latest macOS update (updating to 10.15.4 from 10.15.3), KeyCastr works great! Launched without issue and is capturing keystrokes.
@wjv commented on GitHub (Apr 3, 2020):
Having this issue under macOS 10.15.4. No matter how (or how many times) I grant KeyCastr access to Accessibility, it still gives the error. This happens regardless of whether I install the Homebrew cask, or download the zipped app bundle from GitHub.
@wjv commented on GitHub (Apr 3, 2020):
From the system log:
Prompting policy for hardened runtime; service: kTCCServiceAppleEvents requires entitlement com.apple.security.automation.apple-events but it is missing for ACC:{ID: io.github.keycastr, PID[46449], auid: 1789, euid: 1789, binary path: '/Applications/KeyCastr.app/Contents/MacOS/KeyCastr'}, REQ:{ID: com.apple.appleeventsd, PID[509], auid: 55, euid: 55, binary path: '/System/Library/CoreServices/appleeventsd'}@nyaray commented on GitHub (Apr 9, 2020):
I just checked and I'm getting the same error as @wjv, on macOS 10.15.4, running the latest keyCastr, installed via brew cask.
@leshill commented on GitHub (Apr 13, 2020):
FWIW, adding KeyCastr to
Input Monitoringseems to work.@VKondakoff commented on GitHub (Apr 15, 2020):
The same issue. Could not launch KeyCastr: "Catastrophic Error Encountered".
How can one add it to "Input Monitoring"?
@leshill commented on GitHub (Apr 15, 2020):
@VKondakoff It is one of the other choices in the list (in my Privacy preferences list it is directly below Accessibility).
@brandonlind commented on GitHub (Apr 15, 2020):
@leshill see the second screenshot above. Even once it started working for me (after updating to 10.15.4)** there is nothing in the Input Monitoring field, nor any way to manually add an app to the field.
**though 10.15.4 doesn't seem to be a fix-all since others with the update are still experiencing issues
@leshill commented on GitHub (Apr 17, 2020):
@brandonlind Not sure why I have the standard +/- buttons and you would not.
@akitchen commented on GitHub (Apr 19, 2020):
"Catastrophic Error" isn't a very user-friendly error message, but it means that KeyCastr doesn't have the access it needs. This message will be updated in an upcoming release in an attempt to clarify what's wrong and what's needed to fix it on your machine.
Meanwhile, you can remove it from Accessibility & Input Monitoring and macOS will add it back to Input Monitoring on next startup of the app (macOS Catalina only). Otherwise you may need to remove and re-add it to the Accessibility menu yourself on any version of macOS, Catalina included. The need for this can sometimes creep back in if you've reconfigured KeyCastr's dock/menu item preferences.
I've found that restarting macOS can help flush & synchronize these permissions if things really don't seem to be working right, but the need to do that should be rare. This also helps explain why an OS upgrade seemed to help fix it.
@ekilah commented on GitHub (Apr 20, 2020):
Without changing anything except restarting my computer at some point in the last week, this seems to be resolved for me. Must be that a restart after installing is necessary right now for this app.
If this turns out to be the solution, would probably be good to suggest it somewhere in the app / on that error screen / after install. I hardly restart / shut down my mac.
@wjv commented on GitHub (Apr 20, 2020):
I think @ekilah may be correct. I just left KeyCastr in the non-working state (after posting the comment above), since I didn't need it immediately. When I got back to it a couple of days later, it magically just worked. The only significant thing I did in the meantime was to reboot my Mac.
@VKondakoff commented on GitHub (Apr 23, 2020):
Mine started to work after system restart too.
@leshill commented on GitHub (Apr 23, 2020):
I removed KeyCastr from
Input Monitoringand rebooted and it is working as well. Still has double ⌘␣ entries though (and only that).@pagelab commented on GitHub (May 18, 2020):
A simple restart also solved the issue for me.
@adrianoreis-design commented on GitHub (Jul 28, 2020):
Was so frustrated with this but when i installed mine and granted access under the "Accessibility" menu it still didnt work but by going into "Input Monitoring" it worked. Here is a quick gif showing what i did:
@akitchen commented on GitHub (Sep 15, 2020):
I have noticed that the legacy permissions error dialog (the "catastrophic error" message) interferes with the new system dialog for Input Monitoring, making this onboarding step extra confusing and error prone on 10.15+. We'll need to address this in a way which doesn't break 10.14 and previous OSes in the next version of KeyCastr.
For now -- drag the keycastr "Catastrophic Error" dialog to the side and click on the system dialog about Input Monitoring instead, and everything should be "fine"
@akitchen commented on GitHub (Dec 11, 2020):
-> #182