From ddcba79565c797d06d1f1cc066f78197d0e8ce70 Mon Sep 17 00:00:00 2001 From: Adam Soltys Date: Tue, 4 Aug 2026 01:13:33 -0700 Subject: A restored login ends the wizard instead of stalling in it MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signing in mid-wizard with a key whose wallet was restored left you on the sign-in step: the back-button hold matched the restored account and blocked the auto-advance. A login now clears the hold explicitly — and a restored wallet skips the rest of onboarding entirely; it was already onboarded wherever it came from. Co-Authored-By: Claude Fable 5 --- src/app.js | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'src/app.js') diff --git a/src/app.js b/src/app.js index 4d0f9e0..2124927 100644 --- a/src/app.js +++ b/src/app.js @@ -3597,6 +3597,14 @@ const ctx = { getAccount: () => accountSel(), // Open (or create) a wallet from a mnemonic — used by nostr login. openMnemonic: async (mnemonic, passphrase, opts) => enterWallet(mnemonic, passphrase, opts), + // A nostr login that lands mid-wizard: a restored wallet has been through + // onboarding elsewhere, so the wizard ends; a fresh one just releases the + // back-button hold so the wizard advances to naming it. + onbNostrLogin: (restored) => { + if (!ui.onb) return; + if (restored) { ui.onb = null; try { localStorage.removeItem(ONB_STEP_KEY); } catch {} } + else ui.onb.heldFor = null; + }, }; const FEATURES = buildFeatures(ctx); -- cgit v1.2.3