#2314
[BUG] macOS: shortcut silently doesn't work without Accessibility
handy-keys error is swallowed, Tauri fallback never runs
Without Accessibility, HotkeyManager::new_with_blocking() fails inside the spawned manager thread (handy_keys.rs:114), which just logs it and exits. HandyKeysState::new has already returned Ok, so init_shortcuts never sees the error. Each register then fails on the dead channel and is only logged. The result is that the Tauri fallback in shortcut/mod.rs:42-55 never runs, so the user has no working shortcut and sees no error.
Activity
3
cjpais7d agoI do not assign issues. You work on it and submit a PR and I review the PR.
utpalsinghdev7d agoThanks for clarifying. I'll pick this up and submit a PR once I've tested the fix.
Hi @cjpais, I'd like to work on this. My plan is to pass the manager thread's startup error back to the caller so Handy can try the existing Tauri fallback.
I'll add a test for the startup failure and check shortcut behavior with Accessibility permission off and on. I'll keep this separate from the onboarding changes. Does that approach sound right? If nobody has picked it up, could you assign it to me?