Skip to content

· 12 min read · Nadeera Silva

Mobile

RevenueCat Offerings Empty in Flutter: Fix Error 23

Why RevenueCat offerings come back empty or current is null in Flutter, what error 23 means, and how to find and fix the store setup behind it.

Two smartphones on a pale wooden tray on a grey sofa: the left shows a loaded paywall with pale plan cards and a glowing teal button, the right is a blank off-white screen with a faint spinner, like a RevenueCat paywall stuck with empty offerings

Your Flutter paywall opens and shows nothing but a spinner. In the debug console, purchases_flutter prints "There is an issue with your configuration. Check the underlying error for more details." and, a few lines up, "None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect". This post explains why RevenueCat offerings are empty (or offerings.current is null) in a Flutter app, how to find the cause from the logs, and the Dart code I use so a broken store setup never leaves users on a blank screen.

Quick answer

RevenueCat offerings come back empty when the SDK gets your product IDs from RevenueCat but the App Store or Google Play returns no matching products on that device, or when no products are attached to an offering at all. In Flutter this surfaces as a PlatformException with code 23 (PurchasesErrorCode.configurationError) or as offerings.current == null. Fix it in the stores and the RevenueCat dashboard, not in Dart: check the Paid Apps Agreement and banking, the bundle ID or package name, product status and IDs, the platform API key (appl_ for iOS, goog_ for Android), a Default offering with packages, and a real test setup (sandbox account on iOS, testing track or license tester on Android).

What this means for your app or business

An empty RevenueCat paywall means nobody can pay you.

  • Lost revenue: every user who reaches the paywall is a sale you cannot take, and in production it hits everyone on that platform at once.
  • App Review risk: App Review Guideline 2.1(b) says in-app purchases must be "complete, up-to-date, visible to the reviewer and functional". A blank paywall during review usually means a Guideline 2.1 rejection and another review round (see Guideline 2.1 Information Needed).
  • How long the fix takes: finding the cause usually takes under an hour and most fixes are a setting change. The slow ones are business steps: RevenueCat says agreement and banking changes can take up to 24 hours to propagate, and Google says a new testing track release can take a few hours to reach testers.
  • When to get help: if it works on one platform only, broke right after a release, or nobody on the team can open App Store Connect's Business section.

What does the "There is an issue with your configuration" error mean?

It is the generic message for RevenueCat error 23, CONFIGURATION_ERROR, which Flutter throws as a PlatformException with code "23". The useful part is in e.details['underlyingErrorMessage']. The two common ones in the iOS SDK source are:

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

You have configured the SDK with an App Store API key, but there are no App Store products registered in the RevenueCat dashboard for your offerings.

On Android the first ends with "could be fetched from the Play Store." They point to different places:

  • "None of the products ... could be fetched": the store returned nothing for your product IDs. Look at App Store Connect, the Play Console or your test device.
  • "No ... products registered ... for your offerings": your offerings have no products for this platform. Look at the RevenueCat dashboard or the API key.

A third case has no error: getOfferings() succeeds but offerings.current is null or has no packages. The SDK drops packages whose store product did not load, and current is null without a Default offering. The log says "No packages could be found for offering with identifier ...".

Decision flow for RevenueCat offerings empty in Flutter: error 23 with no products registered means fix the RevenueCat dashboard, error 23 with none of the products fetched means fix the store setup, and no error with a null current offering means set a Default offering and compare product IDs
Which RevenueCat log line you see tells you where to look

Why are RevenueCat offerings empty? The causes I check

The SDK fetches your product IDs from RevenueCat, then asks the store on the device for those products. Any mismatch breaks the last step. These are the causes I confirmed in RevenueCat, Apple and Google docs.

CauseWhere to checkFix
Paid Apps Agreement not Active, or banking or tax incompleteApp Store Connect > BusinessAccount Holder signs the latest agreement and completes banking and tax, then wait up to 24 hours
Product metadata missing (price, localization)App Store Connect > the product pageAdd price and localization so the product shows as Ready to Submit in RevenueCat
Bundle ID or package name mismatchRevenueCat app settings, Xcode, Play ConsoleMake all three identical, case included, per environment
Product ID typoRevenueCat Products vs the storeCopy the exact IDs from the store
Wrong API key for the platformPurchases.configureUse the appl_ key on iOS and the goog_ key on Android
No products attached to an offering, or no Default offeringRevenueCat > Product catalog > OfferingsAttach products to packages and mark one offering as Default
App-Specific Shared Secret or In-App Purchase Key missingRevenueCat app settings (iOS)Add both, as RevenueCat's troubleshooting guide asks
Android app not on a testing track, or tester not a license testerPlay Console > Testing, Monetization settings > License testingPublish to a closed track and add the device's Google account
StoreKit Configuration file still selected in the Xcode schemeXcode > Scheme > Run > OptionsSet StoreKit Configuration to None to test against the sandbox
Testing on a simulator or with a real Apple AccountThe test deviceUse a physical device signed in to a sandbox account
Products released in the last 24 hoursStore release dateWait, RevenueCat says new products can take up to 24 hours

Why does the platform API key matter?

Each app in a RevenueCat project gets its own public SDK key. The SDK source checks the prefix: appl_ (and mac_) for Apple, goog_ for Google Play, amzn_ for Amazon and test_ for RevenueCat's Test Store. RevenueCat's troubleshooting guide warns that a Google key on iOS retrieves the wrong product configuration, so the products can never be fetched. In Flutter it is an easy mistake because one Dart file configures both platforms.

Do iOS products need to be approved first?

No. Apple's TN3186 says testing in the sandbox does not require submitting your in-app purchases for review. What they need is a price and localizations. RevenueCat adds that a product with complete metadata loads in sandbox and shows as Ready to Submit in its dashboard. TN3186 also lists signing problems that hide products: In-App Purchase capability disabled, a wildcard App ID, or an invalid provisioning profile. Your first in-app purchase must be submitted together with an app version.

What does Google Play need before products load?

Google's billing test guide says the Play Billing Library is blocked for apps that are not signed and uploaded to Google Play. License testers can bypass that and sideload debug builds, as long as the package name matches the Play Console app and the Google account on the device is a license tester. RevenueCat recommends a closed track as well, and Google says a new testing track release can take a few hours to reach testers.

The Google Play service account JSON is a different thing. RevenueCat's error docs tie missing Play credentials to errors during the purchase flow, not to empty offerings, so set it up but do not expect it to fix an empty paywall.

Why do offerings work in the simulator but not on a device (or the reverse)?

Simulators do not reach the live App Store, so there products only load from a StoreKit Configuration file. On a device, a StoreKit file still selected in the scheme overrides the sandbox. The iOS SDK also logs a known issue where products are not found on the iOS 18.4 simulator.

How do I fix it step by step in Flutter?

Step 1: configure with the right key per platform and turn on debug logs

I pass keys with --dart-define. The asserts catch a swapped key in debug builds.

import 'dart:io' show Platform;

import 'package:flutter/foundation.dart';
import 'package:purchases_flutter/purchases_flutter.dart';

// Public SDK keys from RevenueCat > Project > API keys.
// flutter run --dart-define=RC_APPLE_KEY=appl_xxx --dart-define=RC_GOOGLE_KEY=goog_xxx
const _appleKey = String.fromEnvironment('RC_APPLE_KEY');
const _googleKey = String.fromEnvironment('RC_GOOGLE_KEY');

Future<void> initRevenueCat() async {
  if (kDebugMode) {
    await Purchases.setLogLevel(LogLevel.debug);
  }

  final String apiKey;
  if (Platform.isIOS || Platform.isMacOS) {
    apiKey = _appleKey;
    assert(apiKey.startsWith('appl_'), 'iOS needs the appl_ key, not $apiKey');
  } else if (Platform.isAndroid) {
    apiKey = _googleKey;
    assert(
      apiKey.startsWith('goog_'),
      'Android needs the goog_ key, not $apiKey',
    );
  } else {
    return; // No store on this platform.
  }

  await Purchases.configure(PurchasesConfiguration(apiKey));
}

Call initRevenueCat() once in main() after WidgetsFlutterBinding.ensureInitialized().

Step 2: load offerings and handle every empty case

This loader returns a state the paywall can render, logs the underlying message for code 23, and only offers a retry when it can help.

import 'package:flutter/foundation.dart';
import 'package:flutter/services.dart';
import 'package:purchases_flutter/purchases_flutter.dart';

sealed class PaywallState {
  const PaywallState();
}

class PaywallReady extends PaywallState {
  const PaywallReady(this.offering);
  final Offering offering;
}

class PaywallUnavailable extends PaywallState {
  const PaywallUnavailable(this.reason, {this.canRetry = false});
  final String reason;
  final bool canRetry;
}

Future<PaywallState> loadPaywall() async {
  try {
    final offerings = await Purchases.getOfferings();
    final current = offerings.current;

    if (current == null) {
      // No Default offering, or its packages were dropped
      // because the store products could not be fetched.
      debugPrint(
        'RC: offerings.current is null. '
        'All offerings: ${offerings.all.keys.toList()}',
      );
      return const PaywallUnavailable('No current offering');
    }
    if (current.availablePackages.isEmpty) {
      debugPrint('RC: offering ${current.identifier} has no packages');
      return const PaywallUnavailable('Offering has no packages');
    }
    return PaywallReady(current);
  } on PlatformException catch (e) {
    final code = PurchasesErrorHelper.getErrorCode(e);
    final details = e.details;
    final underlying = details is Map
        ? details['underlyingErrorMessage']
        : null;
    final readable = details is Map ? details['readableErrorCode'] : null;

    debugPrint(
      'RC getOfferings failed: $code ($readable)\n'
      '  message: ${e.message}\n'
      '  underlying: $underlying',
    );

    switch (code) {
      case PurchasesErrorCode.configurationError:
        // Store setup problem. Retrying will not help.
        return const PaywallUnavailable('Store products unavailable');
      case PurchasesErrorCode.networkError:
      case PurchasesErrorCode.offlineConnectionError:
        return const PaywallUnavailable('No connection', canRetry: true);
      default:
        return const PaywallUnavailable('Could not load plans', canRetry: true);
    }
  }
}

For PaywallUnavailable, show "Plans are not available right now" with a close button, and a retry button only when canRetry is true. RevenueCat's error docs say retrying with the same arguments will not succeed except for network and store problems.

Step 3: fix the cause the log points to

Read the line the SDK prints before the error and use the table above: "could be fetched" means the store side, "no products registered" means the RevenueCat dashboard, and "no packages could be found for offering" means comparing that offering's product IDs with the store. The store checks are the same as in Flutter in-app purchase product not found, because RevenueCat calls the same StoreKit and Play Billing APIs underneath.

How do I verify the fix?

  1. Delete and reinstall the app so no cached offerings are used, then run a debug build on a physical device with LogLevel.debug.
  2. Check the log has no "problem with your configuration" lines.
  3. In the RevenueCat dashboard, check each product's status in Product catalog.
  4. Confirm loadPaywall() returns PaywallReady and every package shows a store price.
  5. Start a purchase: iOS should show the sandbox sheet, Android the test purchase notice for your license tester.
  6. Repeat on the other platform. One working platform proves nothing about the other.

I tested the Dart above with flutter analyze (no issues) and three unit tests that mock the plugin channel: code 23 returns no retry, code 10 returns a retry, and current: null returns "No current offering". For purchases and entitlements, see my Flutter RevenueCat integration guide.

How do I prevent empty offerings next time?

  • Keep a per-environment sheet of bundle ID, package name, API key prefix and product IDs.
  • Have the Account Holder check App Store Connect > Business before each release, and keep the Developer Program on auto-renew.
  • Add price and localization to every new product before you attach it to an offering.
  • Always keep one offering marked as Default.
  • Assert the key prefix per platform and never ship a test_ key.
  • Clear the StoreKit Configuration file from the scheme before sandbox testing.
  • Keep the Android app on a closed track with license testers added.
  • Log offerings.current == null and code 23 as analytics events.
  • Test the paywall on real devices on both platforms before Submit for Review.

Frequently asked questions

Why are my RevenueCat offerings empty in Flutter?

The SDK got your product IDs from RevenueCat but the App Store or Google Play returned no matching products on that device, or no products are attached to your offerings. Common causes are an inactive Paid Apps Agreement, a bundle ID or package name mismatch, missing product metadata, the wrong platform API key, or an Android app that is not on a testing track.

What is RevenueCat error 23?

Error 23 is CONFIGURATION_ERROR, shown as "There is an issue with your configuration. Check the underlying error for more details." In Flutter it is a PlatformException with code 23, and the underlying message in the exception details tells you whether the store returned no products or the offerings have none registered.

Why is offerings.current null in RevenueCat?

Current is null when your project has no Default offering, or when every package in it was dropped because its store product could not be fetched. Mark one offering as Default in the RevenueCat dashboard and check the product IDs in that offering against the store.

Do App Store products need to be approved before RevenueCat can fetch them?

No. Apple says sandbox testing does not require submitting in-app purchases for review. Each product needs a price and localization, and RevenueCat shows products with complete metadata as Ready to Submit.

Which RevenueCat API key should I use in Flutter?

Use the public app-specific key for each platform: the key starting with appl_ on iOS and the one starting with goog_ on Android. A Google key on iOS fetches the wrong product configuration, and a secret sk_ key must never be in the app.

Why do RevenueCat offerings work on a simulator but not on my iPhone?

On a simulator products only load from a StoreKit Configuration file, so the simulator can work while the real App Store Connect setup is still broken. On a device, sign in with a sandbox account and make sure the scheme's StoreKit Configuration is set to None.

Does the Google Play service account fix empty offerings?

Usually not. RevenueCat uses the service account to validate purchases with Google, and its error docs link missing Play credentials to errors during the purchase flow. Empty offerings on Android usually come from the testing track, license testers, the package name or product IDs.

Sources

  1. Troubleshooting Offerings (Why are offerings or products empty?) (RevenueCat Docs)
  2. Displaying Products (RevenueCat Docs)
  3. Error Handling (RevenueCat Docs)
  4. Authentication (API keys) (RevenueCat Docs)
  5. Flutter installation (RevenueCat Docs)
  6. purchases_flutter 11.0.2 (pub.dev, 2026-11-13)
  7. purchases_flutter CHANGELOG (pub.dev, 2026-11-13)
  8. OfferingStrings.swift (SDK log messages) (RevenueCat on GitHub)
  9. OfferingsManager.swift (RevenueCat on GitHub)
  10. OfferingStrings.kt (Android SDK log messages) (RevenueCat on GitHub)
  11. APIKeyValidator.kt (RevenueCat on GitHub)
  12. TN3186: Troubleshooting In-App Purchases availability in the sandbox (Apple Developer)
  13. Overview for configuring In-App Purchases (Apple Developer)
  14. App Review Guidelines (Apple Developer, 2026-10-16)
  15. Test your Google Play Billing Library integration (Android Developers, 2026-10-23)
SharePost on XLinkedIn

Comments

Share a question or note about this article.

Loading comments…