networkError (error code 10): Network error

• iOS: any URLSession failure other than "not connected to the Internet" (which becomes offlineConnectionError) maps here, and so does a request the SDK could not build (NetworkError.swift).
• Android: an IOException or JSONException while performing the request (errors.kt).
• Android: Play Billing NETWORK_ERROR, which Google describes as a network connection problem between the device and Play and says to retry with backoff (Google docs).
• A wrong proxy URL: a typo, http instead of https, a missing port, or localhost on an Android emulator, where localhost is the emulator itself.
• Android blocks cleartext HTTP by default, so an http:// server fails unless you allow it for that host.

• Retrying is safe. The SDK keeps unfinished purchases and posts them again on its own, so the customer does not lose a purchase to a bad connection.
• Show "Check your connection and try again". Keep the screen usable with cached data.
• Do not grant access from the error. The SDK serves cached customer info when it has it.
• Log the underlying error. Many networkErrors from one version of one carrier or country point to a routing or TLS problem.

// Swift
do {
  let result = try await Purchases.shared.purchase(package: package)
} catch let error as ErrorCode where error == .networkError {
  // handle network error
}

// Kotlin
if (error.code == PurchasesErrorCode.NetworkError) { /* ... */ }

On RevenueDot: If RevenueDot is unreachable, the SDK sees a connection error. If it answers 5xx, which it does for its own failures and store outages, the SDK keeps the purchase unfinished and computes access on the device from the product-to-entitlement mapping the server provides. See offline entitlements and 4xx or 5xx on a receipt.