Common desktop-template failures, causes, and fixes.
Mode note: This page documents shared product behavior and the existing Standalone provider details. Unified builds keep the same UI through backend-neutral services and use the provider configuration in Unified / Soar API Setup. Configuration errors never fall back silently.
Use this as a quick symptom → cause → fix index. The Logs
page and pnpm dev terminal are the first places to look for the underlying error.
Auth is on while the Supabase URL/key are missing or invalid
Set VITE_SUPABASE_URL and VITE_SUPABASE_PUBLISHABLE_KEY, or disable auth. See Authentication.
Auth or billing return does not open the app
Scheme is not registered, or redirect is not configured
Check the rebranded scheme in tauri.conf.json and Supabase Auth URL Configuration. On Windows development, test an installed build or use the documented run-once workaround. See Deep Links.
Billing is absent or locked
Flag, product IDs, webhook, or entitlement row is missing
Enable VITE_BILLING_ENABLED, set product IDs, then confirm the webhook writes subscriptions. See Creem Setup.
Webhook signature fails
Wrong Edge secret
Reset CREEM_WEBHOOK_SECRET with supabase secrets set; it must not be in app .env.
