From c62aed4e0c220c3a8e49e4734713cb61bc519062 Mon Sep 17 00:00:00 2001 From: Stefan Ceriu Date: Thu, 13 Aug 2026 17:48:02 +0300 Subject: [PATCH] Detach the Client's `cacheAccountURL` call So it doesn't block service state transitions while hitting the network. --- ElementX/Sources/Services/Client/ClientProxy.swift | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/ElementX/Sources/Services/Client/ClientProxy.swift b/ElementX/Sources/Services/Client/ClientProxy.swift index 798dbef54..2b70e91b5 100644 --- a/ElementX/Sources/Services/Client/ClientProxy.swift +++ b/ElementX/Sources/Services/Client/ClientProxy.swift @@ -1177,7 +1177,8 @@ class ClientProxy: ClientProxyProtocol { // If we are using OAuth we want to cache the account management URL in volatile memory on the SDK side. // To avoid the cache being invalidated while the app is backgrounded, we cache at every sync start. - await cacheAccountURL() + // Fire and forget as it might hit the network. + Task { await cacheAccountURL() } // Nudge the send queue listener to re-evaluate now that we're running; a resume doesn't otherwise // emit, and the SDK only re-enables queues when client.resume() runs (gated behind the flag).