From 294c9ec898497936ea18e3d3bac17b02662e8b3e Mon Sep 17 00:00:00 2001 From: Adam Soltys Date: Wed, 26 Aug 2026 22:27:22 -0700 Subject: The question finally gets asked out loud: the new-wallet confirmation surfaces on the welcome screen too — a first Google sign-in was completing its whole sharding ceremony and then waiting forever on a confirm card only the unlock screen knew how to show MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_019eA8JRq9Wr7z2fRQk99HLi --- src/features/nostrlogin.js | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'src/features') diff --git a/src/features/nostrlogin.js b/src/features/nostrlogin.js index a76e40c..2e659b0 100644 --- a/src/features/nostrlogin.js +++ b/src/features/nostrlogin.js @@ -589,6 +589,11 @@ export function nostrLoginFeature(ctx) { // The welcome screen's sign-in block: Google and passkey act right there; // the Nostr button steps into the wizard's signer list. frontDoorSignin() { + // A mid-flight login state — the "create a wallet for this identity?" + // confirmation — must surface here too: it used to render only on the + // unlock screen's card, which left a first Google sign-in silently + // waiting on a confirm button that was never on screen. + if (ui.nostrLoginNew) return unlockExtra(); return h('div', { class: 'col', style: 'gap:8px' }, ...externalButtons(loginWith, true), h('button', { class: 'btn-block', style: 'padding:14px', onClick: () => { -- cgit v1.2.3