[GH-ISSUE #321] KeyCastr won't launch on macOS < 11.0 #275

New issue

Closed

opened 2026-05-05 05:11:14 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 05:11:14 -06:00

Owner

Originally created by @sdeken on GitHub (Mar 25, 2025).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/321

Filing a bug report on behalf of someone who reached out to me directly:

Hi! KeyCastr used to work great on my late Mac, but I just installed it on my "new" one, and it won't launch. The icon reacts to the double-click, but it doesn't even make it to the point of appearing in the Dock; absolutely nothing happens.

I'm running OS 10.14.6 (Mojave) and have given KeyCastr permission to run my computer in the Privacy System Preferences:

Any idea what the problem could be?

Originally created by @sdeken on GitHub (Mar 25, 2025). Original GitHub issue: https://github.com/keycastr/keycastr/issues/321 Filing a bug report on behalf of someone who reached out to me directly: > Hi! KeyCastr used to work great on my late Mac, but I just installed it on my "new" one, and it won't launch. The icon reacts to the double-click, but it doesn't even make it to the point of appearing in the Dock; absolutely nothing happens. > > I'm running OS 10.14.6 (Mojave) and have given KeyCastr permission to run my computer in the Privacy System Preferences: > > ![Image](https://github.com/user-attachments/assets/f5b9aedd-5aee-4625-8782-48bf698ce295) > > Any idea what the problem could be?

gitea-mirror closed this issue

2026-05-05 05:11:18 -06:00

gitea-mirror commented

2026-05-05 05:11:22 -06:00

Author

Owner

@akitchen commented on GitHub (Mar 25, 2025):

I think this is the same as what was reported in #318 . I happen to have an older mac also running 10.14.6, so I fired it up to see what's going on.

Although the app is built with a deployment target of 10.13, in the latest release the KCVisualizer framework has a deployment target of 11.0 according to a console log entry related to the failed startup. It looks like the internal frameworks' configuration got reset to use a MACOSX_DEPLOYMENT_TARGET of RECOMMENDED_MACOSX_DEPLOYMENT_TARGET which was 11.0 at the time this build was created.

This is already fixed locally as a part of the work I was doing to try to prep the minimal visualizer for an upcoming release. I haven't had much time for that lately so I'll look into creating a small bugfix release for this. I doubt there are many users on this version of OS X but I'm happy to hear there are some!

@akitchen commented on GitHub (Mar 25, 2025): I think this is the same as what was reported in #318 . I happen to have an older mac also running 10.14.6, so I fired it up to see what's going on. Although the app is built with a deployment target of 10.13, in the latest release the KCVisualizer framework has a deployment target of 11.0 according to a console log entry related to the failed startup. It looks like the internal frameworks' configuration got reset to use a MACOSX_DEPLOYMENT_TARGET of RECOMMENDED_MACOSX_DEPLOYMENT_TARGET which was 11.0 at the time this build was created. This is already fixed locally as a part of the work I was doing to try to prep the minimal visualizer for an upcoming release. I haven't had much time for that lately so I'll look into creating a small bugfix release for this. I doubt there are many users on this version of OS X but I'm happy to hear there are some!

gitea-mirror commented

2026-05-05 05:11:24 -06:00

Author

Owner

@akitchen commented on GitHub (Mar 25, 2025):

cc @alltiagocom

@akitchen commented on GitHub (Mar 25, 2025): cc @alltiagocom

gitea-mirror commented

2026-05-05 05:11:26 -06:00

Author

Owner

@sdeken commented on GitHub (Mar 25, 2025):

Yep - I forwarded him your comments from #318 to see if that helped him, but haven't heard back. His message actually got lost in my inbox - he sent the original note back in December and I didn't see it until today.

At some point I swear I'll dig out my MacBook and see if I can help knock down some of the backlog 😅

@sdeken commented on GitHub (Mar 25, 2025): Yep - I forwarded him your comments from #318 to see if that helped him, but haven't heard back. His message actually got lost in my inbox - he sent the original note back in December and I didn't see it until today. At some point I swear I'll dig out my MacBook and see if I can help knock down some of the backlog 😅