Reported via support email on 2026-06-10 by a macOS user (details anonymized).

What happens

When an app update is available, the UI shows a link/button to restart the app to apply it. Clicking it does not complete the update: the app comes back with a "Screenpipe is still starting" message and a referral to the Settings page, which doesn't resolve anything. The user has to fully Quit the app and manually relaunch it to get the update applied.

Observed while updating v2.5.24 -> v2.5.27 on macOS.

Expected

Clicking "restart to apply update" quits, applies the update, and relaunches into a working state, no manual quit needed.

Repro

1. Run v2.5.24 with an update available (v2.5.27)
2. Click the in-app "restart to apply update" button
3. App relaunches into "Screenpipe is still starting" with a pointer to Settings, update not applied until a manual Quit + relaunch

Notes for triage

• Smells like the restart races the old process (port/teardown) or the updater relaunches before the old instance fully exits, similar in shape to the known stop->start race on the engine side.
• Worth checking the tauri updater flow's relaunch ordering and whether "still starting" is the new instance failing to bind while the old one lingers.