[Connection Status] No way to detect silent disconnections / connection state

[tom-eberle]

Hi Convex team 👋

I’m running Convex in production with the Swift SDK, and I’m hitting a recurring problem:

• The app will sometimes silently drop the Convex connection (likely the WebSocket getting wedged or a transport error).
• After that, all queries/mutations/subscriptions stop working, but my SubscriptionStore has no idea that the client is disconnected.
• There’s currently no public API in Swift to check connection state or to observe state changes.

In other SDKs there is such an API:

• JS: client.subscribeToConnectionState(cb)
• Rust: with_on_state_change(...)

But in Swift, we only have subscribe, mutation, action, and authState. That means I cannot build health checks or automatically reset the client when the socket goes down.

👉 Request:
Would it be possible to expose a connection state publisher / callback in the Swift SDK, similar to JS and Rust? That would let us reliably detect:

• Connected
• Reconnecting
• Disconnected

Right now the only workaround is to implement my own "heartbeat" query or ping mutations, but this feels like a hack for something the SDK should expose natively.

Thanks a lot! The SDK works great otherwise, this would really improve production stability. 🙏

[dowski]

Hey thanks for taking the time to file the issue! I'm planning on taking a look at this soon.

[pasharayan]

Still running into this issue

[dowski]

Heads up for anyone else who might be experiencing the library becoming unresponsive - we found and fixed a deadlock in the core convex-rs library that the Swift client is built upon. That fix is live in the following release:

https://github.com/get-convex/convex-swift/releases/tag/0.6.1

Still tracking the websocket status API, but wanted to get that fix out there as it could be the true root cause of the unresponsive client.