From 27ff4cef22d86512474d07f1186ed76242e29a7c Mon Sep 17 00:00:00 2001
From: Gigi <dergigi@pm.me>
Date: Thu, 16 Oct 2025 22:55:17 +0200
Subject: [PATCH] fix: properly connect NostrConnectSigner on reconnection

- Call signer.connect() instead of forcing isConnected
- Add [bunker] logs for connect lifecycle
- Should unblock nip44/nip04 decrypt calls that were timing out
---
 src/services/nostrConnect.ts | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/src/services/nostrConnect.ts b/src/services/nostrConnect.ts
index 3cbc36dc..3a3b197b 100644
--- a/src/services/nostrConnect.ts
+++ b/src/services/nostrConnect.ts
@@ -43,9 +43,16 @@ export async function reconnectBunkerSigner(
   if (!account.signer.listening) {
     await account.signer.open()
   }
-  
-  // Mark as connected (bunker remembers permissions from initial connection)
-  account.signer.isConnected = true
+
+  // 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...')
+    await account.signer.connect()
+    console.log('[bunker] ✅ Connected to bunker remote')
+  } catch (err) {
+    console.error('[bunker] ❌ Failed to connect to bunker remote:', err)
+  }
   
   // Expose nip04/nip44 at account level (like ExtensionAccount does)
   if (!('nip04' in account)) {