fix(desktop): wrap get_dev_key invoke in try/catch for release builds

[FSM1]

Summary

• get_dev_key is only registered as a Tauri command in debug builds (#[cfg(debug_assertions)] in main.rs), but the webview JS called await invoke('get_dev_key') without try/catch
• In release builds (e.g. staging DMG), the promise rejects immediately, silently aborting the entire init() function — leaving the app stuck on "Initializing CipherBox..." forever
• Fix: wrap the invoke in try/catch so it gracefully returns null in release builds

Test plan

• Desktop release build (staging DMG) progresses past "Initializing CipherBox..." to the login screen
• Desktop debug build with --dev-key still works as before

🤖 Generated with Claude Code

Summary by CodeRabbit

Bug Fixes

• Enhanced application stability by gracefully handling missing development key features in release builds, preventing potential crashes when development tools are unavailable.

[coderabbitai]

Walkthrough

The change adds try/catch error handling around a dev-key retrieval call in the main application initialization, initializing the devKey variable to null and gracefully handling cases where the command is unavailable in certain build configurations.

Changes

Cohort / File(s)	Summary
Error Handling for Dev-Key Retrieval apps/desktop/src/main.ts	Wrapped dev-key retrieval in try/catch block with null initialization to prevent unhandled rejections when the command is not registered (e.g., in release builds).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: wrapping get_dev_key invoke in try/catch for release builds, which is exactly what the PR accomplishes.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/desktop-init-and-isloading

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

apps/desktop/src/main.ts (1)

51-58: Fix is correct; consider a debug-mode fallback log in the catch.

The try/catch properly resolves the release-build regression. One minor gap: the bare catch {} silently discards all errors, including unexpected IPC failures in debug builds. If get_dev_key fails for a reason unrelated to "command not registered" (e.g., a Tauri IPC misconfiguration during development), the error disappears and the dev has no signal that the --dev-key flow was skipped unexpectedly.

♻️ Optional: surface unexpected errors in debug builds

-  try {
-    devKey = await invoke('get_dev_key');
-  } catch {
-    // Expected in release builds where the command isn't registered
-  }
+  try {
+    devKey = await invoke<string | null>('get_dev_key');
+  } catch (err) {
+    // Expected in release builds where the command isn't registered.
+    // Log in debug so unexpected IPC failures don't silently drop --dev-key.
+    if (import.meta.env.DEV) {
+      console.warn('get_dev_key invoke failed (expected in release builds):', err);
+    }
+  }

The explicit invoke<string | null> generic is also slightly clearer than relying on contextual type inference from the devKey assignment, though both compile correctly.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@apps/desktop/src/main.ts` around lines 51 - 58, The empty catch swallows all
IPC errors; change the invoke call to invoke<string | null>('get_dev_key') and
in the catch block log unexpected errors when in debug/dev mode (e.g., check a
debug flag or NODE_ENV) so IPC failures during development are surfaced, while
still allowing a silent fallback in release builds; reference the devKey
variable, the invoke('get_dev_key') call and the surrounding try/catch to locate
where to add the conditional debug log.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@apps/desktop/src/main.ts`:
- Around line 51-58: The empty catch swallows all IPC errors; change the invoke
call to invoke<string | null>('get_dev_key') and in the catch block log
unexpected errors when in debug/dev mode (e.g., check a debug flag or NODE_ENV)
so IPC failures during development are surfaced, while still allowing a silent
fallback in release builds; reference the devKey variable, the
invoke('get_dev_key') call and the surrounding try/catch to locate where to add
the conditional debug log.