github-starred/keycastr

Fork 0

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

[GH-ISSUE #18] "Enable access for assistive devices and applications #18

New issue

Closed

opened 2026-05-05 04:43:19 -06:00 by gitea-mirror · 11 comments

gitea-mirror commented

2026-05-05 04:43:19 -06:00

Owner

Originally created by @alexhernandez on GitHub (Nov 18, 2014).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/18

When activating app, even with access for assistive devices enabled for Keycastr, the application errors out and quits. See screenshots.

Originally created by @alexhernandez on GitHub (Nov 18, 2014). Original GitHub issue: https://github.com/keycastr/keycastr/issues/18 When activating app, even with access for assistive devices enabled for Keycastr, the application errors out and quits. See screenshots. ![screen shot 2014-11-17 at 4 57 12 pm](https://cloud.githubusercontent.com/assets/2424355/5080852/d3526cd0-6e7a-11e4-907e-817560167473.png) ![screen shot 2014-11-17 at 4 55 35 pm](https://cloud.githubusercontent.com/assets/2424355/5080829/9714c8e4-6e7a-11e4-9a5b-bdd77c0501e0.png)

gitea-mirror closed this issue

2026-05-05 04:43:22 -06:00

gitea-mirror commented

2026-05-05 04:43:24 -06:00

Author

Owner

@utkarshkukreti commented on GitHub (Nov 27, 2014):

I'm getting the same error on OSX 10.9.5.

@utkarshkukreti commented on GitHub (Nov 27, 2014): I'm getting the same error on OSX 10.9.5.

gitea-mirror commented

2026-05-05 04:43:26 -06:00

Author

Owner

@ts commented on GitHub (Dec 1, 2014):

Same issue on 10.10

@ts commented on GitHub (Dec 1, 2014): Same issue on 10.10

gitea-mirror commented

2026-05-05 04:43:27 -06:00

Author

Owner

@seventhsense commented on GitHub (Dec 15, 2014):

I got same issue.
I unchecked Keycaster in accessibility, and check again, finaly I managed to make start Keycaster without this error.

Off course, It's not a fundamental solution.

@seventhsense commented on GitHub (Dec 15, 2014): I got same issue. I unchecked Keycaster in accessibility, and check again, finaly I managed to make start Keycaster without this error. Off course, It's not a fundamental solution.

gitea-mirror commented

2026-05-05 04:43:29 -06:00

Author

Owner

@elmimmo commented on GitHub (Dec 18, 2014):

I get the same issue. The Console app displays the following messages:

18/12/14 11:04:10,688 amfid[260]: /Applications/KeyCastr.app/Contents/MacOS/KeyCastr signature not valid: 0xfffefa2a
18/12/14 11:04:10,000 kernel[0]: proc 3593: load code signature error 4 for file "KeyCastr"
18/12/14 11:04:11,387 KeyCastr[3593]: *** <QCNodeManager | namespace = "com.apple.QuartzComposer" | 386 nodes>: Could not load bundle at path "/Users/jorge/Library/Graphics/Quartz Composer Patches/Origami.plugin" (Error Domain=NSCocoaErrorDomain Code=3585 "The bundle “Origami” couldn’t be loaded because it doesn’t contain a version for the current architecture." (dlopen_preflight(/Users/jorge/Library/Graphics/Quartz Composer Patches/Origami.plugin/Contents/MacOS/Origami): no suitable image found.  Did find:
    /Users/jorge/Library/Graphics/Quartz Composer Patches/Origami.plugin/Contents/MacOS/Origami: mach-o, but wrong architecture) UserInfo=0x7bfc1540 {NSLocalizedRecoverySuggestion=Try installing a universal version of the bundle., NSFilePath=/Users/jorge/Library/Graphics/Quartz Composer Patches/Origami.plugin/Contents/MacOS/Origami, NSLocalizedFailureReason=The bundle doesn’t contain a version for the current architecture., NSLocalizedDescription=The bundle “Origami” couldn’t be loaded because it doesn’t contain a version for the current architecture., NSDebugDescription=dlopen_preflight(/Users/jorge/Library/Graphics/Quartz Composer Patches/Origami.plugin/Contents/MacOS/Origami): no suitable image found.  Did find:
    /Users/jorge/Library/Graphics/Quartz Composer Patches/Origami.plugin/Contents/MacOS/Origami: mach-o, but wrong architecture, NSBundlePath=/Users/jorge/Library/Graphics/Quartz Composer Patches/Origami.plugin})
18/12/14 11:04:11,743 tccd[194]: Unable to verify code signing identity of net.stephendeken.KeyCastr:  la identidad del código se ha invalidado

The last sentence is due to my OS locale being Spanish. It translates to “The identity of the code has been invalidated”.

@elmimmo commented on GitHub (Dec 18, 2014): I get the same issue. The **Console** app displays the following messages: ``` 18/12/14 11:04:10,688 amfid[260]: /Applications/KeyCastr.app/Contents/MacOS/KeyCastr signature not valid: 0xfffefa2a 18/12/14 11:04:10,000 kernel[0]: proc 3593: load code signature error 4 for file "KeyCastr" 18/12/14 11:04:11,387 KeyCastr[3593]: *** <QCNodeManager | namespace = "com.apple.QuartzComposer" | 386 nodes>: Could not load bundle at path "/Users/jorge/Library/Graphics/Quartz Composer Patches/Origami.plugin" (Error Domain=NSCocoaErrorDomain Code=3585 "The bundle “Origami” couldn’t be loaded because it doesn’t contain a version for the current architecture." (dlopen_preflight(/Users/jorge/Library/Graphics/Quartz Composer Patches/Origami.plugin/Contents/MacOS/Origami): no suitable image found. Did find: /Users/jorge/Library/Graphics/Quartz Composer Patches/Origami.plugin/Contents/MacOS/Origami: mach-o, but wrong architecture) UserInfo=0x7bfc1540 {NSLocalizedRecoverySuggestion=Try installing a universal version of the bundle., NSFilePath=/Users/jorge/Library/Graphics/Quartz Composer Patches/Origami.plugin/Contents/MacOS/Origami, NSLocalizedFailureReason=The bundle doesn’t contain a version for the current architecture., NSLocalizedDescription=The bundle “Origami” couldn’t be loaded because it doesn’t contain a version for the current architecture., NSDebugDescription=dlopen_preflight(/Users/jorge/Library/Graphics/Quartz Composer Patches/Origami.plugin/Contents/MacOS/Origami): no suitable image found. Did find: /Users/jorge/Library/Graphics/Quartz Composer Patches/Origami.plugin/Contents/MacOS/Origami: mach-o, but wrong architecture, NSBundlePath=/Users/jorge/Library/Graphics/Quartz Composer Patches/Origami.plugin}) 18/12/14 11:04:11,743 tccd[194]: Unable to verify code signing identity of net.stephendeken.KeyCastr: la identidad del código se ha invalidado ``` The last sentence is due to my OS locale being Spanish. It translates to “The identity of the code has been invalidated”.

gitea-mirror commented

2026-05-05 04:43:32 -06:00

Author

Owner

@paulirish commented on GitHub (Jan 20, 2015):

what worked for me:

Put keycastr.app in your Applications folder
open up the security/privacy/accessibility preferences that are in the top screenshot (https://github.com/keycastr/keycastr/issues/18#issue-49166722)
click the lock to unlock this pane (bottom left)
drag the keycastr app into the app list

it seems that it's important for the app to be in /Applications

@paulirish commented on GitHub (Jan 20, 2015): what worked for me: - Put keycastr.app in your Applications folder - open up the security/privacy/accessibility preferences that are in the top screenshot (https://github.com/keycastr/keycastr/issues/18#issue-49166722) - click the lock to unlock this pane (bottom left) - drag the keycastr app into the app list it seems that it's important for the app to be in `/Applications`

gitea-mirror commented

2026-05-05 04:43:35 -06:00

Author

Owner

@jasonhemann commented on GitHub (Jan 22, 2015):

For me this same error issue emerged after changing the display from Dock and Menu Bar to only Menu Bar.

OS X 10.10.1
keycastr-0.8.2-bezel, installed via homebrew-caskroom.

Uninstalling and reinstalling seemed to resolve the issue, while maintaining my preferred settings.

@jasonhemann commented on GitHub (Jan 22, 2015): For me this same error issue emerged after changing the display from Dock and Menu Bar to only Menu Bar. OS X 10.10.1 keycastr-0.8.2-bezel, installed via homebrew-caskroom. Uninstalling and reinstalling seemed to resolve the issue, while maintaining my preferred settings.

gitea-mirror commented

2026-05-05 04:43:38 -06:00

Author

Owner

@ELLIOTTCABLE commented on GitHub (Feb 1, 2015):

General solution is removing it from assistive preferences, and then re-adding it, solves this problem. Can verify. (Same as @jasonhemann, happened to me after changing it to menu-bar only.)

@ELLIOTTCABLE commented on GitHub (Feb 1, 2015): General solution is removing it from assistive preferences, and then re-adding it, solves this problem. Can verify. (Same as @jasonhemann, happened to me after changing it to menu-bar only.)

gitea-mirror commented

2026-05-05 04:43:40 -06:00

Author

Owner

@ashfinal commented on GitHub (Feb 15, 2015):

Same issue on 10.10.2. Seems every time you change the settings, you have to re-add it to the list of assistive preferences to avoid this error. Though not a big problem, still hope guys can fix it.

@ashfinal commented on GitHub (Feb 15, 2015): Same issue on 10.10.2. Seems every time you change the settings, you have to re-add it to the list of assistive preferences to avoid this error. Though not a big problem, still hope guys can fix it.

gitea-mirror commented

2026-05-05 04:43:43 -06:00

Author

Owner

@bcherny commented on GitHub (Jun 5, 2015):

@paulirish that worked well for me on OSX 10.10.2. thanks!

@bcherny commented on GitHub (Jun 5, 2015): @paulirish that worked well for me on OSX 10.10.2. thanks!

gitea-mirror commented

2026-05-05 04:43:46 -06:00

Author

Owner

@akitchen commented on GitHub (Jun 7, 2015):

@ELLIOTTCABLE is right - sometimes you have to re-add it. In v0.8.4 the error message is updated to be more relevant for later versions of OS X.

@akitchen commented on GitHub (Jun 7, 2015): @ELLIOTTCABLE is right - sometimes you have to re-add it. In v0.8.4 the error message is updated to be more relevant for later versions of OS X.

gitea-mirror commented

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

Author

Owner

@ELLIOTTCABLE commented on GitHub (Feb 18, 2016):

Just pointing out that on two different machines, this is still necessary every single time you launch. No other app requiring accessibility access (I have … about ten?) has this issue. )=

A real fix would be ideal, and this shouldn't be closed.

(Meantime: In addition to the notice at launch-time, until this is fixed, you should also add a notice when changing the dock/menubar setting, as this causes a relaunch.)

@ELLIOTTCABLE commented on GitHub (Feb 18, 2016): Just pointing out that on two different machines, this is _still_ necessary _every single time you launch_. No other app requiring accessibility access (I have … about ten?) has this issue. )= A real fix would be ideal, and this shouldn't be closed. (Meantime: In addition to the notice at launch-time, _until_ this is fixed, you should also add a notice when changing the dock/menubar setting, as this causes a relaunch.)