Feature Request: Document recommended patterns for handling multiple wallet connections in a single app session #1841
Description
Is your feature request related to a problem? Please describe.
Applications using the Coinbase Wallet SDK may support reconnecting, switching accounts, or handling multiple wallet connection attempts within a single app session. However, the documentation does not clearly describe recommended patterns for managing these flows safely and predictably
Developers may be unsure about:
- how to properly reset state between disconnect and reconnect
- whether reusing the same provider instance is recommended
- how to handle multiple connection attempts without leaking listeners
- best practices for managing provider lifecycle in SPAs and mobile-first apps
Describe the solution you'd like
Add a dedicated documentation section titled “Connection Lifecycle & Reconnection Patterns.” This section should explain the recommended approach for initializing, reusing, and disposing of provider instances across multiple connect and disconnect cycles. It should also describe how and when to attach or remove event listeners to avoid duplicated listeners or stale state.
Include simple, framework-agnostic examples that demonstrate safe reconnect handling in single-page applications and mobile-first environments. The guidance should remain high-level and focused on best practices, without prescribing a specific application architecture.
Describe alternatives you've considered
No response
Additional context
No response