Understanding SDK debug messages is crucial for troubleshooting. This section explains how to enable logging and interpret common log messages.

Enabling Debug Logging

Always enable verbose logging during development to see what the SDK is doing.

iOS (Swift)

import RevenueCat

// Enable before configure
Purchases.logLevel = .debug  // Most verbose
// Purchases.logLevel = .verbose  // Alternative

Purchases.configure(withAPIKey: "appl_xxx")

Android (Kotlin)

import com.revenuecat.purchases.LogLevel

// Enable before configure
Purchases.logLevel = LogLevel.DEBUG  // Most verbose
// Purchases.logLevel = LogLevel.VERBOSE  // Alternative

val builder = PurchasesConfiguration.Builder(this, "goog_xxx")
Purchases.configure(builder.build())

Log Levels

• DEBUG: Most verbose, shows everything (use during development).
• VERBOSE: Detailed information about operations.
• INFO: General informational messages.
• WARN: Warnings about potential issues.
• ERROR: Error messages only.

Common Warning Messages

Warning: Products Not Approved (iOS)

[RevenueCat] Warning: RevenueCat SDK is configured correctly, but contains some issues you might want to address
Warnings:
• Your products are configured in RevenueCat but aren't approved in App Store Connect yet.
  This prevents users from making purchases in production.
  Please ensure all products are approved and available for sale in App Store Connect.

What it means:

• Products exist in RevenueCat dashboard.
• But they're not approved in App Store Connect.
• This is normal during development.

Action required:

• If testing: Use StoreKit Configuration File or wait for approval.
• If production: Submit products for review with your app.
• Can be safely ignored during local development.

Warning: Offering Configuration Issues

[RevenueCat] 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
• Package 'annual' references product 'premium_annual' which is not available

What it means:

• Packages in offering reference products that can't be found.
• Products might not exist in store or IDs don't match.

Action required:

1. Verify product IDs match between RevenueCat and store.
2. Check products are active/approved in store.
3. Ensure products are added to StoreKit Configuration (iOS).

Common Error Messages

Error: None of Products Could Be Fetched

[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

What it means:

• SDK tried to fetch products from store but all failed.
• Critical configuration issue.

Action required:

1. Check product IDs match exactly.
2. Verify bundle ID/package name matches.
3. For iOS: Use StoreKit Configuration or wait for product approval.
4. For Android: Verify service account permissions.

See the Fetching Offerings Errors section above for detailed troubleshooting.

Error: Network/API Issues

[RevenueCat] Error: Unable to fetch offerings
NetworkError: The Internet connection appears to be offline
URLError: The request timed out

What it means:

• Device has no network connection.
• Or RevenueCat servers are unreachable.

Action required:

1. Check device internet connection.
2. Test if other apps/websites work.
3. Disable VPN if using one.
4. Implement retry logic in your app.

Error: Invalid API Key

[RevenueCat] Error: Invalid API key
The API key provided is invalid or doesn't have access to this app

What it means:

• API key is wrong or typo.
• Using wrong platform key (iOS key on Android or vice versa).

Action required:

1. Go to RevenueCat dashboard → API keys.
2. Copy the correct key for your platform:
   • iOS: Starts with appl_.
   • Android: Starts with goog_.
3. Update your code.

Understanding Store Error Codes

iOS StoreKit Error Codes

Android Billing Response Codes

Interpreting Purchase Flow Logs

Here's what a successful purchase flow looks like in logs:

[RevenueCat] DEBUG: Fetching offerings from cache
[RevenueCat] DEBUG: Offerings retrieved successfully
[RevenueCat] DEBUG: makePurchase called for package: monthly
[RevenueCat] DEBUG: Starting purchase flow for product: premium_monthly
[RevenueCat] DEBUG: Purchase initiated
[RevenueCat] DEBUG: Finishing purchase transaction
[RevenueCat] DEBUG: Transaction finished successfully
[RevenueCat] INFO: Purchase completed successfully
[RevenueCat] DEBUG: CustomerInfo updated

Key points:

• Shows full purchase lifecycle.
• Transaction finishes automatically.
• CustomerInfo updates after purchase.

Common SDK Messages Quick Reference

Tips for Effective Debugging

1. Always enable debug logging first when troubleshooting.
2. Search logs for "RevenueCat" to filter SDK messages.
3. Look for error and warning symbols to find errors/warnings quickly.
4. Check logs immediately after operations (fetch offerings, purchase, restore).
5. Copy full error messages when asking for support.
6. Disable in production to avoid performance issues.