From 11cb3542ee5b900ca065659488a40304577b8d42 Mon Sep 17 00:00:00 2001 From: Gigi Date: Thu, 16 Oct 2025 23:11:08 +0200 Subject: [PATCH] fix: revert forced connect on reconnection to restore signing - Remove connect(undefined, permissions) on restore - Let requireConnection() trigger connect per op - Keeps highlights signing working as before while we debug decrypt --- src/services/nostrConnect.ts | 13 +++---------- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/src/services/nostrConnect.ts b/src/services/nostrConnect.ts index 27c8f359..1a9e5a3f 100644 --- a/src/services/nostrConnect.ts +++ b/src/services/nostrConnect.ts @@ -44,16 +44,9 @@ export async function reconnectBunkerSigner( await account.signer.open() } - // Ensure the signer is connected to the remote signer - // Important: do NOT set isConnected manually; establish connection properly - try { - console.log('[bunker] Connecting to bunker remote...') - // Re-request permissions on reconnect to ensure decrypt is allowed - await account.signer.connect(undefined, getDefaultBunkerPermissions()) - console.log('[bunker] ✅ Connected to bunker remote') - } catch (err) { - console.error('[bunker] ❌ Failed to connect to bunker remote:', err) - } + // Do not force connect here; let requireConnection() run per operation + // For debugging, keep a minimal log of readiness + console.log('[bunker] Signer ready (listening:', account.signer.listening, ')') // Expose nip04/nip44 at account level (like ExtensionAccount does) if (!('nip04' in account)) {