Wallet Disconnects After Pairing – No Dapp Request Received (v1.6.5). -

[nirmalpatidar123]

Hi Reown team,

We're encountering an issue with WalletKit v1.6.5 from the reown-swift GitHub repo in our Swift-based iOS wallet. After pairing, the wallet sometimes shows as connected, but no actual request is received from the Dapp. Instead, we only see an RPCRequest log — the request never reaches our handler.

Environment: testnet

Observations:
Device A: iPhone 12, iOS 18.3.1 — issue occurs frequently.
Device B: iPhone X, iOS 16.7.10 — issue occurs rarely.

The issue is more likely after the app has been in the background for some time, though it doesn't happen every time. The behavior is non-deterministic.

Wallet appears connected, but:
sessionRequestPublisher does not receive the request.
socketConnectionStatusPublisher shows no disconnect — remains .connected.
Manual tryReconnect() does not help.
Killing and restarting the app causes the previously "stuck" Dapp request to be received normally.

Relevant Code:
WalletConnect Session Setup:

`func setupWalletConnectSession() {
guard !walletConnectSessionInitialized else { return }
walletConnectSessionInitialized = true

WalletKit.instance.sessionProposalPublisher
    .receive(on: DispatchQueue.main)
    .sink { [weak self] session in
        self?.onSessionProposal(session.proposal, session.context)
    }.store(in: &publishers)

WalletKit.instance.sessionRequestPublisher
    .receive(on: DispatchQueue.main)
    .sink { [weak self] session in
        _ = AppDelegate.getInstance().appCoordinator.redirectManager
            .onReceiveWCSessionRequest(session.request)
    }.store(in: &publishers)

WalletKit.instance.socketConnectionStatusPublisher
    .receive(on: DispatchQueue.main)
    .sink { [weak self] status in
        switch status {
        case .connected:
            Logger.instance.log(message: "WalletConnect socket connected", event: .i)
        case .disconnected:
            Logger.instance.log(message: "WalletConnect socket disconnected try reconnect", event: .i)
            self?.tryReconnect()
        }
    }.store(in: &publishers)

}
`

Reconnection Attempt:

func tryReconnect() { Logger.instance.log(message: "checking", event: .i) Task { let sessions = await WalletKit.instance.getSessions() Logger.instance.log(message: "🧩 Reconnected sessions: \(sessions.count)", event: .i) } }

Question:
Is there anything we might be missing in our lifecycle or reconnection handling, especially after the app returns from the background?
We’re wondering if an additional socket refresh or session check is needed manually when the app becomes active again.

Summary:
Likely a socket/session sync issue after backgrounding.
No disconnect reported, but Dapp requests silently fail to reach sessionRequestPublisher.
A cold restart of the app resolves the issue.

We would appreciate any guidance, known workarounds, or confirmation if this is a known issue in v1.6.5 of the reown-swift SDK.

Thanks in advance for your support!