configurationError (error code 23): Configuration error

• iOS: none of the products in your offerings could be fetched from App Store Connect, or from the StoreKit configuration file if one is in use. The SDK's own message says so (OfferingsManager.swift).
• An offering exists but has no products for this app's store, or the API key belongs to a store that has no products registered.
• iOS simulator: a known issue with iOS 18.4 simulators makes product requests fail. The SDK suggests another iOS version.
• The backend answered 7000 (invalid platform), 7255 (could not create alias) or 8077 (cannot alias to an authenticated user). Android also maps 7230 (Play invalid package name) here (BackendErrorCode.swift, errors.kt).
• Android: workflows or other optional features were requested but are not enabled.

• Do not retry. The setup stays wrong until you fix it.
• Show a neutral "purchases are not available right now" message and alert yourself. This is not the customer's fault.
• Do not grant access. Customers who already paid keep the access the SDK has cached.

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

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

On RevenueDot: RevenueDot answers HTTP 400 with code 7000 when a secret-key receipt post has no X-Platform header, when a store action does not exist for the app's store, when a hosted checkout is asked for a package that has no web product, and when purchases-js asks for its own Web Billing checkout with an rcb_ key, which RevenueDot does not have. Offerings point at products by their store identifier, so a mismatch there leaves the SDK with no products. See common problems.