The macOS Dev Binary That Won't Take Focus

"You'll type a sentence into your beautiful new window and watch it appear in your terminal. Here's why — and why it's not your fault."

The Symptom

On macOS you run tauri dev, the window appears, you click into a text field, you start typing — and nothing lands. The keystrokes go to whatever app was focused before (often your terminal or editor). Mouse clicks work; keyboard input doesn't. It feels like a Tauri bug. It isn't, exactly.

The Cause: It's Not a Real App Yet

When you run tauri dev, macOS launches a bare cargo debug binary — not a packaged .app bundle. A bare binary isn't registered with macOS LaunchServices the way a real app is, so on some macOS versions it never gets promoted to the frontmost application. A window that isn't owned by the frontmost app can receive mouse events but won't become the key window — and only the key window's webview receives keyboard events. That's the whole bug, and it's specific to dev mode.

The Good News and the Fix

Your built .app does not have this problem — it's a proper bundle, registered normally, frontmost like any app. So this never reaches your users. For the dev loop, the quick workaround is to Cmd-Tab to the app after it launches. The real fix is a small setup() hook that nudges macOS to promote the process and activate it. This bug bit Cinder during development; the full Cocoa-level fix lives in the windows track lesson on native activation — for now, just recognize the symptom so it doesn't cost you an afternoon.

Code

First aid: ask macOS to treat the dev process as a real app·rust

// The Tauri-level lever (declarative). This alone is often not enough on
// a bare dev binary — the deep Cocoa fix is in the windows track — but
// it's the first thing to know exists.
use tauri::{ActivationPolicy, Manager};

tauri::Builder::default()
    .setup(|app| {
        #[cfg(target_os = "macos")]
        app.set_activation_policy(ActivationPolicy::Regular);

        if let Some(w) = app.get_webview_window("main") {
            let _ = w.set_focus();
        }
        Ok(())
    });

Exercise

If you're on a Mac, reproduce it: run tauri dev, click the window, and try typing without Cmd-Tabbing first. Note whether your keystrokes land. Then Cmd-Tab to the app and try again. Whether or not you hit the bug (it's macOS-version-dependent), write one sentence explaining WHY a bare dev binary behaves differently from a packaged .app.

Hint

The key concept is 'frontmost app' + 'key window.' A bare binary isn't registered with LaunchServices like a real .app, so macOS may not promote it to frontmost — and only the key window's webview gets keyboard events.