Fetching offerings errors are among the most common issues developers face. These typically occur when RevenueCat can't retrieve product information from the app stores.

Issue 1: "None of the products could be fetched" Error

Error Message

[RevenueCat] 🍎‼️ Error fetching offerings - The operation couldn't be completed.
(RevenueCat.OfferingsManager.Error error 1.)
There's a problem with your configuration. None of the products registered in the RevenueCat dashboard
could be fetched from App Store Connect (or the StoreKit Configuration file if one is being used).
More information: https://rev.cat/why-are-offerings-empty

Common Causes

1. No Products Configured: Products not set up in RevenueCat dashboard.
2. Product ID Mismatch: IDs in RevenueCat don't match store products.
3. Products Not Available in Current Storefront: Testing from unsupported region.
4. Bundle ID / Package Name Mismatch: App identifier doesn't match dashboard.
5. Products Not Approved (iOS): Products pending review in App Store Connect.
6. Service Account Issues (Android): Google Play credentials not configured.

Solution Steps

Step 1: Verify Products Exist in RevenueCat

1. Go to RevenueCat dashboard.
2. Navigate to Product Catalog → Products.
3. Verify you have products listed.
4. If empty, import products or create them manually.

Step 2: Verify Product IDs Match Store

For iOS:

1. Check product IDs in App Store Connect.
2. Compare with RevenueCat dashboard (Product Catalog → Products).
3. Ensure exact match (case-sensitive).

For Android:

1. Check product IDs in Google Play Console.
2. Compare with RevenueCat dashboard.
3. Ensure exact match (case-sensitive).

Step 3: Verify Products Are in an Offering

1. In RevenueCat dashboard, go to Product Catalog → Offerings.
2. Select your offering (usually "default").
3. Check that packages exist and contain products.
4. If no packages, click Edit and add packages with products.

Step 4: Check Platform-Specific Setup

For iOS:

• Verify bundle ID matches in RevenueCat (Apps & providers → App Store).
• Ensure products are approved or use StoreKit Configuration File.
• Check sandbox tester is signed in (if testing in sandbox).

For Android:

• Verify package name matches in RevenueCat (Apps & providers → Google Play).
• Ensure service account is configured and has permissions.
• Verify products are Active in Google Play Console.
• Ensure app is published to at least Internal Testing.

Issue 2: Empty Offerings

Symptoms

• offerings.all is empty.
• offerings.current is nil.
• No error message, but offerings object has no data.

Common Causes

1. No Packages in Offering: Offering exists but has no packages.
2. No Default Offering Set: No offering marked as default.
3. Products Not Attached to Packages: Packages exist but have no products.
4. Offering Identifier Mismatch: Code requests wrong offering identifier.

Solution Steps

Step 1: Verify Offering Has Packages

1. In RevenueCat dashboard, go to Product Catalog → Offerings.
2. Click on your offering (e.g., "default").
3. Verify the Packages section has at least one package.
4. If empty, click Edit and add packages.

Step 2: Verify Packages Have Products

1. For each package in your offering.
2. Verify it has products attached for your platform (iOS or Android).
3. At minimum, each package needs one product ID.

Step 3: Set Default Offering

1. In Product Catalog → Offerings.
2. Find your main offering.
3. Check if "Current" badge is displayed.
4. If not, click the offering → Make Current.

Step 4: Verify Code Uses Correct Identifier

iOS:

let offerings = try await Purchases.shared.offerings()

// Check if current offering exists
if let offering = offerings.current {
    print("Offering: \(offering.identifier)")
    print("Packages: \(offering.availablePackages.count)")
} else {
    print("No current offering set")
}

Android:

val offerings = Purchases.sharedInstance.awaitOfferings()

// Check if current offering exists
offerings.current?.let { offering ->
    Log.d("RC", "Offering: ${offering.identifier}")
    Log.d("RC", "Packages: ${offering.availablePackages.size}")
} ?: Log.d("RC", "No current offering set")

Issue 3: Offering Configuration Warnings

Error Message

warning: The offerings 'default' have configuration issues that may prevent users from
seeing product options or making purchases.
Product Issues:
• Package 'monthly' references product 'premium_monthly' which is not available

Common Causes

1. Missing Product for Platform: Package has iOS product but no Android product (or vice versa).
2. Incorrect Product Association: Product attached to package doesn't exist in store.
3. Platform Filter Issue: Product exists but is filtered out for current platform.

Solution Steps

Step 1: Check Package Configuration

1. In RevenueCat dashboard, go to your offering.
2. For each package, verify it has products for both iOS and Android (if you support both platforms).
3. If you only support one platform, ensure products exist for that platform.

Step 2: Verify Product Exists in Store

1. Copy the problematic product ID from the warning.
2. Check if it exists in App Store Connect or Google Play Console.
3. If it doesn't exist, either:
   • Create the product in the store, OR
   • Remove/update the product reference in RevenueCat.

Issue 4: Network and API Errors

Error Message

Error: Unable to fetch offerings
NetworkError: The Internet connection appears to be offline
Error: Request timed out

Common Causes

1. No Network Connection: Device has no internet access.
2. Firewall/VPN Blocking: Corporate network or VPN blocks RevenueCat servers.
3. Invalid API Key: Wrong API key configured.
4. Server Issues: Rare RevenueCat service disruption.

Solution Steps

Step 1: Verify Network Connection

1. Test internet connectivity on device/simulator.
2. Try opening a website in browser.
3. Check Wi-Fi/cellular data is enabled.

Step 2: Check API Key

// Verify you're using the correct API key for your platform
// iOS: Should start with "appl_"
// Android: Should start with "goog_"

Purchases.configure(withAPIKey: "appl_xxxxxxxxxxx")

Step 3: Test Without VPN/Proxy

1. Temporarily disable VPN or proxy.
2. Test if offerings fetch successfully.
3. If successful, configure VPN/firewall to allow RevenueCat domains.

Step 4: Implement Retry Logic

func fetchOfferingsWithRetry(maxRetries: Int = 3) async throws -> Offerings {
    var lastError: Error?

    for attempt in 1...maxRetries {
        do {
            return try await Purchases.shared.offerings()
        } catch {
            lastError = error
            if attempt < maxRetries {
                // Wait before retrying (exponential backoff)
                try await Task.sleep(nanoseconds: UInt64(pow(2.0, Double(attempt))) * 1_000_000_000)
            }
        }
    }

    throw lastError ?? NSError(domain: "Offerings", code: -1)
}

Common Issues Quick Reference

Debugging Checklist for Offerings Issues

• ☐ Products exist in RevenueCat dashboard.
• ☐ Product IDs match exactly with store (case-sensitive).
• ☐ Offering has packages with products attached.
• ☐ Default offering is set.
• ☐ Bundle ID / Package name matches.
• ☐ API key is correct for platform (appl_ or goog_).
• ☐ Network connection is available.
• ☐ Products are approved (iOS) or Active (Android).
• ☐ Debug logging is enabled.
• ☐ Testing with valid credentials (sandbox or Test Store).