Skip to main content
Question

NOELIGIBLEOFFER (statusCode 4) for all products — everything configured correctly, 6 days old

  • May 11, 2026
  • 3 replies
  • 27 views

Forum|alt.badge.img

Hi,

I'm getting NOELIGIBLEOFFER (statusCode 4) for all 4 subscription products on Android. 
SDK version 10.1.2, Capacitor plugin.

Logs show:
- RC API returns 200 for offerings ✅
- Products requested: elitemonthly, eliteyearly, promonthly, proyearly
- All return: Product Type subs, Reason NOELIGIBLEOFFER, statusCode 4
- Error: "None of the products registered in the RevenueCat dashboard 
  could be fetched from the Play Store"

What I've confirmed is correctly set up:
- Products created May 5 (6 days ago, not a propagation issue)
- Base plans are Active
- Prices set for CA and US
- Internal Testing track has a published APK
- Test accounts added as Internal Testers AND in License Testing
- Device restarted, Play Store cache cleared
- No recent changes to base plans

Package name: com.mi4labs.carnivorex

Any idea what I'm missing?

3 replies

Tarek
RevenueCat Staff
Forum|alt.badge.img+5
  • RevenueCat Staff
  • May 13, 2026

Hey ​@maria-ivanova-83634d ,

 

I checked your configuration against our sample app, and your offering is returned as empty. A few reasons might explain it:

 

1. Google Play Console agreements / banking not completed
You must have all merchant agreements signed and banking details filled in Google Play Console. If this hasn't been done, Play Store will refuse to serve products. This is a common gotcha.

2. App not published on a closed track
Google Play requires the app to be published on at least a closed testing track before in-app products can be fetched, even in development/testing. If it's only in draft or internal testing, products won't load either.

3. Licensed testers not configured
If the user testing this is not added as a licensed tester in Play Console → Settings → License testing, they may not be able to fetch products. The Google account on the device must match one of the licensed testers.

4. Regional availability
Please make sure the app and products are available in the region from which you're testing.
 

5. Physical Device Testing
We strongly recommend testing on a physical device rather than the Android emulator.
 

6. Package Name Validation
Please verify that the package name in the RevenueCat dashboard matches the package name in Google Play Console and your Android project exactly.
 

7. API Key Platform Check
Please, also make sure to configure the RevenueCat SDK with the correct platform-specific API key. The Google / Android key should begin with goog_.

 

Feel free to check our full troubleshooting guide for empty offerings here.

 

Let me know if that makes sense, and if there's anything I can clarify further!

 

Best regards,


Forum|alt.badge.img

Hi Tarek, 

 

That helped, thank you so much!


Tarek
RevenueCat Staff
Forum|alt.badge.img+5
  • RevenueCat Staff
  • May 15, 2026

Hi ​@maria-ivanova-83634d!

 

You're most welcome!

 

Best,