Repository navigation
bug(macos): WhatsApp reconnect flow on Mac (needs repro) #1346
Description
Parent: #830 (chat leftovers, 9 Sep report). Needs repro. platform: macOS. Verified against main @ 8e39053.
Report
WhatsApp reconnection is confusing or broken on Mac.
What we know
- The reconnect logic is unchanged since the report:
main/services/whatsapp.ts~L915-945. A 401 (logged out) wipes the auth and forces a re-pair (new QR). Anything else auto-reconnects afterRECONNECT_DELAY_MS. - Commits touching
whatsapp.tssince then (feat(reports): dispatch cash close via whatsapp #940, feat(settings): owner-only Offline mode that closes every optional outbound connection #1306 Offline mode, feat: add WhatsApp message templates, automated rules, and safety controls #1315, fix(main): harden WhatsApp offline abort, split-bill deduplication, loyalty rounding, and auto-settlement automation #1323) are not Mac-specific.
Steps to try (macOS, DMG and Mac App Store builds)
- Pair, quit the app, reopen. Does it reconnect without a QR?
- Pair, put the Mac to sleep for at least 10 minutes, then wake it.
- Pair, then unlink the device from the phone. Is the re-pair QR shown clearly?
- On the MAS build, check that auth files persist in the sandbox container.
Acceptance
- A repro and fix, plus a clear UI state for "reconnecting" vs "re-pair needed". Or cannot reproduce on 3.13.0, and close.
Activity
khaira777 commentedon Oct 26, 2026
Looking into this issue now.
khaira777 commentedon Oct 26, 2026
Reproduction and verification results for macOS WhatsApp reconnect and re-pair flow (addressed in #1385):
515 restartRequired& app quit):queueCredentialWrite()queuedsaveCreds()asynchronously oncreds.update, allowing an immediate515 restartRequiredreconnect orrequestShutdown()to read stale/incomplete auth state before the write flushed.flushCredentialWrites()is now awaited before reconnect and during shutdown.515 restartRequiredvs408unpaired QR timeout:515now triggers an immediate ~250ms reconnect without incrementingreconnectAttemptsor settinglastError.408occurs with no registered credentials (creds.me?.idabsent), the service stops background retry loops and transitions cleanly todisconnectedso the user can explicitly generate a new QR code.hasRegisteredCredentialsso the UI distinguishes transient reconnects from unpaired re-pair flows.waiting_pairingand restorespairingModecleanly if a pairing-code request fails.