Network Client

By default each Descope mobile SDK performs its own HTTP requests using the platform's standard networking stack. The Swift, Kotlin, and Flutter SDKs let you replace that stack with your own implementation by setting a network client on the SDK configuration.

When to Use It

• Unit testing. Supply a client that returns canned responses or throws, so tests that exercise your Descope integration make no real network calls.
• Reusing your app's HTTP stack. Route Descope requests through the same session, connection pool, or client instance the rest of your app already uses.
• Instrumentation. Observe request timing or attach your own tracing around the calls the SDK makes.

Implementing a Network Client

Each platform defines the client differently, so the method you implement and the values you return are not the same across SDKs.

public protocol DescopeNetworkClient: Sendable {
    func call(request: URLRequest) async throws -> (Data, URLResponse)
}

Descope.setup(projectId: "__ProjectID__") { config in
    config.networkClient = AppNetworkClient(appSession)
}

class AppNetworkClient: DescopeNetworkClient {
    let session: URLSession

    init(_ session: URLSession) {
        self.session = session
    }

    func call(request: URLRequest) async throws -> (Data, URLResponse) {
        return try await session.data(for: request)
    }
}

final class FailingNetworkClient: DescopeNetworkClient {
    let error: DescopeError = .networkError

    func call(request: URLRequest) async throws -> (Data, URLResponse) {
        throw error
    }
}