2 Commits

Author	SHA1	Message	Date
HolgerHatGarKeineNode	7e491326a9	Build the Nostr signer URI in the browser, not server-side ... Server-side percent-encoding (rawurlencode/http_build_query) produced a nostrsigner: URI that Amber rejected as malformed. The launcher view now assembles it in JS with encodeURIComponent(JSON.stringify(event)) — the exact encoding Amber accepts (verified working earlier in the session). The controller only passes k1 and the callback URL.	2026-06-11 22:40:57 +02:00
HolgerHatGarKeineNode	58c7e410b0	Add headless Nostr launcher page for the mobile app ... A direct ACTION_VIEW intent to nostrsigner: (Browser::open from the app) lacks category.BROWSABLE, so Amber routes it into its app-to-app path and rejects it as malformed. The app instead opens /auth/mobile/nostr in an in-app browser; that page fires the signer via window.location, so the intent carries BROWSABLE and Amber uses its web-signing flow. No visible login UI, local signing, token returned via the App Link.	2026-06-11 22:08:17 +02:00