fix(bunker): guarded connect after subscription to enable decrypt

- After opening subscription, call connect() once per session if remote is present
- Helps Amber authorize decrypt ops; safe-guarded and logged
- Keep isConnected=true for subsequent requireConnection() paths
This commit is contained in:
Gigi
2025-10-17 00:19:21 +02:00
parent ec45fbc5e8
commit 4603c5a258

View File

@@ -325,7 +325,16 @@ function App() {
console.log('[bunker] ✅ Signer already listening')
}
// Mark as connected so requireConnection() doesn't call connect() again
// Attempt a guarded reconnect to ensure Amber authorizes decrypt operations
try {
if (nostrConnectAccount.signer.remote && !reconnectedAccounts.has(account.id)) {
console.log('[bunker] Attempting guarded connect() to ensure decrypt perms')
await nostrConnectAccount.signer.connect(undefined, undefined)
console.log('[bunker] ✅ Guarded connect() succeeded')
}
} catch (e) {
console.warn('[bunker] ⚠️ Guarded connect() failed:', e)
}
// Give the subscription a moment to fully establish before allowing decrypt operations
// This ensures the signer is ready to handle and receive responses