tauri-knowledge-patch

Tauri v2 migration replaces the v1 allowlist with capability and permission files, requiring clear key remappings and platform scoping to ensure secure defaults. You must create capability files that define permissions for specific windows and webviews.

Tauri 2.0 IPC migration uses Channel-based streaming for event payloads and efficient binary Response returns instead of v1 patterns. You must update Rust command signatures to use the Channel type and Response struct for IPC communication.

Tauri 2.0 plugin migration maps built-in v1 APIs to separate v2 plugins, requiring updated JS import paths and explicit plugin installation in Cargo.toml and registration in your Rust lib. You must install each plugin package and register it with the builder.

Tauri 2.0 mobile entry points require structuring shared libraries for mobile platforms and using the new Emitter and Listener traits for the event system. You must configure mobile-specific initialization in the lib.rs file to support iOS and Android.

Tauri 2.0 migration build failures often stem from avoiding insecure defaults by not properly scoping capabilities and permissions. The new security model requires explicit permission grants in capability files instead of broad allowlist access to prevent runtime issues.