English

SpaceLauncher for macOS

Why SpaceLauncher’s Shortcuts Pause: macOS Secure Input

What’s happening

If SpaceLauncher’s keyboard shortcuts suddenly stop responding, check whether macOS Secure Input is on. When Secure Input is the cause, the pause is usually expected behavior rather than a problem with SpaceLauncher.

Secure Input is a macOS protection for sensitive typing, such as passwords. While it’s on, macOS can prevent SpaceLauncher from receiving the keyboard events it needs. Text expanders and keyboard automation tools that handle keyboard input in the same way can also be affected. Since SpaceLauncher can’t see your keys during this time, it pauses your shortcuts and resumes by itself as soon as Secure Input turns off, provided SpaceLauncher is enabled. While the pause lasts, SpaceLauncher shows a notice on its menu bar icon.

When Secure Input is off, SpaceLauncher recognizes your shortcuts locally on your Mac. It doesn’t record what you type. You can read more in the Privacy Policy.

Secure Input typically turns on in situations like these:

Most of the time it turns off again as soon as you finish typing, so you’ll barely notice the pause. Sometimes, though, the app that turned it on forgets to turn it off. macOS then keeps blocking SpaceLauncher’s shortcuts even though you’re not typing anything sensitive. When that happens, the cause is that app or macOS, not SpaceLauncher.

Is this normal?

If you’re typing a password or other sensitive information, yes. Shortcuts pause while you type and come back on their own if SpaceLauncher is enabled, so there’s nothing to do. Entering your password on the lock screen counts too: SpaceLauncher’s diagnostics may show it as loginwindow, the part of macOS that handles the lock screen and sign-in.

If you aren’t typing anything sensitive and your shortcuts are still paused, Secure Input may be stuck. When SpaceLauncher is enabled, the pause badge on its menu bar icon tells you whether Secure Input is affecting your shortcuts right now.

Things you can try

These are common suggestions for apps affected by Secure Input, SpaceLauncher included. They may not work on your Mac, since the cause differs from case to case, so treat them as things to try, roughly from easiest to most disruptive.

  1. Finish or close anything asking for a password or sign-in. Check your browser, password manager, VPN, and any system prompt, including ones hidden behind other windows or on another desktop.
  2. Turn off Secure Keyboard Entry in Terminal. Open the Terminal menu and make sure Secure Keyboard Entry is unchecked, unless you need it. Other terminal apps may have a similar setting.
  3. Quit and reopen apps you suspect. Save your work first. Apps that handle passwords or sign-ins are good candidates, and so is any app you opened just before the problem began. If the problem comes back as soon as you reopen one, that app is a likely cause.
  4. Lock your Mac, then unlock it with your password rather than Touch ID. This sometimes clears it.
  5. Log out and back in, or restart your Mac. This is the most disruptive option, so save your work first and keep it as a last resort. If you restart, you can untick “Reopen windows when logging back in” so the app that caused the problem doesn’t open again right away.

Please don’t force-quit system processes such as loginwindow or WindowServer. Use a normal log out or restart instead.

What SpaceLauncher can and can’t do

SpaceLauncher can tell when Secure Input is on, and it pauses and resumes your shortcuts accordingly. What it can’t do is turn Secure Input off. Only the app, or the part of macOS, that turned it on can release it. SpaceLauncher isn’t the one holding it, so quitting and reopening SpaceLauncher, reinstalling it, or granting it permissions again won’t help.

macOS provides a process clue that can be read in code or with command-line tools such as ioreg. SpaceLauncher’s diagnostics show the same system record. The clue isn’t reliable, though. It may name the app that was in front when Secure Input turned on, and sometimes one that has already quit, so it can’t tell you who is really responsible.

If you find which app turns Secure Input on and leaves it on, or anything else that helped, please tell me through Support, along with how to trigger it if you know, so I can add it here for other users.

Further reading

Other apps that run into the same macOS restriction have written about it: