Bugfix: What Rust/Tauri config issues must be resolved for a product...

Documentation for Sessions

🐛 Bugfix: What Rust/Tauri config issues must be resolved for a product...

Date: 2026-02-25
Time: 16:21:43 UTC
Session: gspace1-141.6
Agent: angular
Confidence: 97%
Status: ✅ Documented

📋 Decision Context

Question:

What Rust/Tauri config issues must be resolved for a production build with signing?

Task: Vitto desktop production build signing verification

🎯 Decision Made

Chosen:

Four fixes required: (1) add url = "2" crate explicitly, (2) use tauri-plugin-opener instead of deprecated shell.open(), (3) add createUpdaterArtifacts: "v1Compatible" to bundle config, (4) use single quotes in zsh for passwords with special chars

Options Considered:

Fix all four issues
Use shell plugin with suppress warning
Skip signing verification locally

💭 Reasoning

Root causes: url crate is used directly via url::Url in parse_auth_deep_link() but tauri-plugin-deep-link does not re-export it publicly — must be explicit in Cargo.toml. tauri_plugin_shell::Shell::open() was deprecated in favor of tauri-plugin-opener in Tauri v2.5+. createUpdaterArtifacts is NOT included in bundle targets:all by default — must be set to v1Compatible to generate .app.tar.gz.sig for the auto-updater. zsh treats ! as history expansion in double-quoted strings — single quotes prevent this. All four must pass for a verified signed build.

📁 Files Involved

apps/vitto-desktop/src-tauri/Cargo.toml
apps/vitto-desktop/src-tauri/src/lib.rs
apps/vitto-desktop/src-tauri/tauri.conf.json

🔗 Related

Decision ID: dev_1772036503893_3cafzob
Session: 141
Workspace: gspace1

Auto-generated by MCP Smart Consolidation