Skip to main content
Question

app not fetching offerings on android

  • September 19, 2025
  • 8 replies
  • 186 views

Forum|alt.badge.img

hello. im building the app mostly in flutterflow and im hitting the wall . offers are not showing no matter what i do . it was setup about 10 days ago so they should show .

What’s implemented

  • FlutterFlow → RevenueCat integration enabled.

    • Android Public SDK key (goog_…) set.

    • iOS Public SDK key (appl_…) set (for later).

    • “Load data after App Launch” enabled.

  • RevenueCat project config.

    • Offering default published.

    • Package $rc_monthly attached to Android product premium_monthly:monthly and iOS product.

    • Entitlement premium mapped to that package.

    • Hosted paywall published (but we’re using purchasePackage).

  • Google Play Console.

    • App id: com.klikin.app (matches RC app + build).

    • Subscription premium_monthly with base plan monthly is Active/Published.

    • Countries: ~173 (includes Switzerland).

    • Payments profile: Active.

    • Test track: Closed/Internal; app installed via testing link (not search).

    • Tester (my Google account): added and accepted.

    • Service account JSON uploaded to RevenueCat → Valid credentials shown.

    • Same service account invited as a user in Play Console with Monetization / Financial permissions.

  • Firebase.

    • Webhook (RC → HTTPS function) deployed; requests received (saw hits).

    • Membership trial / gift Cloud Functions present (not blocking purchase flow).

App-side code / flows

  • Warmup on Home Page Load: rcWarmup (touches getCustomerInfo; waits/retries for getOfferings.current).

  • RC Login: rcLogin(uid) runs if reLastUid != currentUser.uid; then sets reLastUid.

  • Purchase button: rcPurchaseByPackage(offeringId="default", packageId="$rc_monthly", entitlementId="premium")

    • Finds package by RC id, fallback by store id (premium_monthly:monthly).

    • Calls Purchases.purchasePackage(target).

    • Verifies entitlement → returns bool.

  • Diagnostics added:

    • Purchases.setLogLevel(LogLevel.debug) enabled.

    • Versions of actions with retries + optional SnackBars / returned error strings.

    • Earlier test wrote RC customer attributes (diag) to inspect on dashboard.

What we observe (device & RC)

  • RC Dashboard → Customers: my device user appears; “New customers” increments; no active entitlements.

  • Earlier probe snackbar:Failed to reach RC handling” / “RevenueCat not ready yet. Try again”.

  • Current behavior: tapping Start membership:

    • The button shows longer “loading”, but no Google Play purchase sheet appears.

    • When actions didn’t include SnackBars, nothing visible (only prints).

    • When warmup has SnackBars, it sometimes reports getOfferings() didn’t yield a current offering.

  • Built-in FF action (“Open RC Paywall”) also did not open earlier—same symptom.

  • Cancel/Manage subscription button does open the Play subscriptions page (device has working Play services).

IDs verified (consistent everywhere)

  • Package name: com.klikin.app.

  • Offering id: default.

  • RC package id: $rc_monthly.

  • Play product id (with base plan): premium_monthly:monthly.

  • Entitlement id: premium.

  • RC SDK keys: Public keys match the RC project apps.

Things we’ve already ruled out

  • Wrong keys / wrong app id (RC shows customer hits; keys match).

  • Missing service account permissions (RC shows Valid credentials; service account granted Monetization/Financial in Play).

  • Tester not enrolled / wrong install path (installed via testing link; “You’re a tester” banner).

  • Outdated Play Store / cache (cleared Play Store & Play Services caches, rebooted, reinstalled).

  • Regional availability (product active in target country; tester in CH; countries include CH).

  • Firebase issues (webhook receives requests; RC → Firebase path works; not related to sheet opening).

The actual symptom to investigate

  • Purchases.getOfferings() intermittently throws / returns no current offering on the device, so purchasePackage is never called and the Play purchase sheet never appears—despite RC showing the device/customer and the offering configured/published.

What would help from support

    • Server logs for this appUserId / package name showing why getOfferings() returns no current offering (e.g., Play returned 0 valid products for this account/build/country).

    • Any PurchasesErrorCode or backend errors tied to my calls around the timestamps of attempts.

  • or any other idea you might have 

    so thats in short i have been on it for 4 days now and its simply not working no matter what i try
This post has been closed for comments

8 replies

guilherme
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • September 29, 2025

Hey ​@borivoj-radulovic-290304 ,

I'm very sorry about the delay on this reply. We've been auditing our ticketing system and found that your ticket was never resolved due to an issue in our system that deprioritized it.

We've fixed the issue so it shouldn't happen again!

From your report, it looks like the setup is accurate - I was also able to check your RevenueCat dashboard and all seems as expected.

Would it be possible to share your FlutterFlow config as screenshots? For the different actions and overall settings? 


Forum|alt.badge.img

hello, i did end up opening a ticket as well and it seems that everything on your side works correctly , person helping me managed to fetch the offers internally . as of flutterflow i only have fetch offer and or purchase for testing purposes so it is as simple as that and should work which means revenuecat and flutterflow are not the culprit. i didnt have time yet to fiddle with googles side as i was finishing other things but as soon as i do i will update this feed with what i found out. at least this narrows it down on where the communication gets broken so thank you for your answer and as soon as i can ill update here.


guilherme
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • September 29, 2025

Hey ​@borivoj-radulovic-290304  - thanks for confirming those!

To centralise comms then, could I ask to add the future update/details on the ongoing ticket? Once we understand what is happening we can post the solution here, but it would avoid having to jump between the 2 contact points.

Feel free to tag this thread on the ticket too, for added context.

Thanks,


Forum|alt.badge.img

@guilherme everything will be here the ticket was closed after confirming that its not on revenuecat side. as soon as i have more info ill post it here as i see many people on different forums having same or similar problems and it might help. hopefully in next few days ill be able to tackle this issue again so i dont leave what im doing now in the middle.


Forum|alt.badge.img

@guilherme a small update , figured out that in play store in payment methods there is no “test card” for anyone for some reason . i contacted google as license testing email list is properly set and and active i even tried with new email and new phone and still no test card anywhere. ill update here as i figure out more things as of now culprit is definitely google  


guilherme
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • October 9, 2025

Hey ​@borivoj-radulovic-290304 thanks for that update - do let us know how it goes!

 


Forum|alt.badge.img

@guilherme  hello its been some time but here is the update . as of now problem is still there . i narrowed it down to the device is not being treated as a license tester, so Google Play never shows the sandbox test card and the Billing client returns no products . google support is not very helpful . i have been trying to make them verify on the backend that the tester accounts are actually flagged as license testers alas they still haven't and just run in circles without ever giving me the straight answer. i will make sure to give updates as i get them 


guilherme
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • October 23, 2025

Absolutely! Let me know once you know more - adding our documentation on this too, in case it’s helpful: https://www.revenuecat.com/docs/test-and-launch/sandbox/google-play-store#create-a-test-user-and-configure-licensing-testing