SDKs

Hi everyone,I’m testing subscriptions in my iOS app through TestFlight, but opening the subscription screen produces this error: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).Setup• Expo / React Native with react-native-purchases.• EAS production build distributed through TestFlight.• The build uses the public iOS RevenueCat SDK key (appl_…), not the Test Store key. The same key was configured in the EAS production environment before building.• RevenueCat Test Store is enabled only in development builds.• The app is currently in App Review.What I’ve checked• The Paid Applications Agreement is active, and tax/banking information is complete (Purchases worked for another app of mine in the past).• The bundle ID matches between the app, App Store Connect, and RevenueCat.• Apple product IDs match exactly between App Store Connect and Reve

Hi everyone,I am using the RevenueCat Flutter SDK (purchases_flutter) on Android (Google Play Store) in my game. I am encountering an intermittent issue where purchases are occasionally attributed to a newly generated $RCAnonymousID at the moment of purchase, even though Purchases.logIn("2585") is executed during app initialization.Important Context: In my game architecture, users cannot access or open the shop page unless they are fully signed in. Therefore, an anonymous purchase flow should theoretically be impossible under normal user operation.Additionally, right before a user selects a product to pay, I explicitly call Purchases.setEmail(). However, when this bug occurs and the purchase is unexpectedly assigned to an anonymous ID, subscriber_attributes in the webhook payload remains completely empty (no $email present).This issue happens rarely; in most cases, the Flutter SDK works as expected and attaches purchases to the logged-in app_user_id.Timeline of Events (from Dashboard L

Hi RevenueCat team and community, I am building my mobile application using FlutterFlow (No-Code platform), so I do not manually manage native Android configuration files or code in a standard IDE. When trying to generate a release Android App Bundle (AAB), my build fails during the R8 minification task because of `purchases_flutter` and Google Play Billing API classes. I have attached a complete diagnostic report to this post (Flutter Build Diagnostic Report.pdf) which contains the exact error logs, but here is the core issue:ERROR: R8: Missing class com.android.billingclient.api.QueryPurchaseHistoryParams$Builder (referenced from: ... com.revenuecat.purchases.google.BillingClientParamBuildersKt.buildQueryPurchaseHistoryParams(...)) Execution failed for task ':app:minifyReleaseWithR8'.Since I am working within FlutterFlow, could you please advise on how I can resolve this? Specifically: 1. Do I need to add custom ProGuard keep rules in FlutterFlow for RevenueCat / Google Play Billing?

We are experiencing inconsistent currency display during testing in TestFlight. All subscription prices are already correctly configured in App Store Connect for all countries and regions. Custom Paywall UI / RevenueCat Paywall: Prices retrieved from RevenueCat offerings are displayed in USD ($). Apple In-App Purchase Sheet: Prices are correctly displayed in INR (₹). I came across a similar post discussing this issue that was published around seven months ago. I would like to confirm whether there have been any updates or changes since then, and whether this behavior is still expected or if there is now a recommended solution.

It would be useful to expose the existing Customer Center Contact Support UI as a standalone flow, for example:RevenueCatUI.presentContactSupport()We already use the Contact Support functionality configured through Customer Center, including RevenueCat's support form and embedded metadata.However, our app has its own Support entry point, and we would like to open the RevenueCat Contact Support form directly without first presenting the entire Customer Center.Ideally, this would use the same Contact Support configuration, metadata, and ticket flow as the existing Customer Center implementation, just exposed as a standalone UI flow.Since RevenueCatUI already uses an internal support ticket flow, it seems that most of the underlying functionality is already in place. Because of that, exposing the existing Contact Support UI as a standalone entry point may be relatively small in scope, while making it much easier to integrate into custom app settings and support screens.

Google released new version of Next Gen AdMob SDK. Does RevenueCat support that?

Hi,I added a one-time lifetime purchase to my app using RevenueCat. Technically, this is a non-consumable in-app purchase. The app is not currently available on the app stores; I am testing it through internal testing (Play Store) and TestFlight (App Store), and I plan to release it once everything is complete.Users who purchase lifetime access will receive certain benefits, such as an ad-free experience.However, I am experiencing the following issue on iOS:The user installs the app. The user purchases lifetime access. The user deletes the app. The user reinstalls it through TestFlight. The user taps the Restore Purchases button on the purchase screen.After tapping the button, it enters a loading state, but nothing happens afterward. There is no response or confirmation.However, if the user taps the purchase button again, iOS displays the following message:“You’ve already purchased this. It has been restored for free.”I am not sure whether the same issue occurs on Android because the p

RevenueCat is showing wrong paywalls in my app at seemingly random. Fresh install, etc does not help. When testing with the RevenueCat app itself this happens as well.I have only 1 paywall. Only light mode. I do not have any running experiments. iOS only app.

I’m using a custom font with 3 weights (450, 500 & 550). I’m using these in my paywalls, and they display properly in the Paywall Editor and in my iOS and Android app. On the web, (@revenuecat/purchases-js 1.39.1) it’s not as great. The 500 font doesn’t really show up different than the 450. Font-weight is good if I inspect it but visually it’s not right.Wondering if it could be related to that specific font, or it’s a web SDK issue?Thank you.

I’m currently writing an API endpoint for use by an Android app, to interface with the “Restore a Google Play purchase by order ID” REST API endpoint. This is due to well-known “consumed purchase” misconfiguration issue. It’s hard to test it due to the nature of the issue, and therefore I have a few questions.If the restoration succeeds (i.e. the response code is 200), can I immediately query the customer info (using the app SDK) and expect the entitlement that wasn’t present before to now be immediately present, or does it take time? I will disable caching for the request. If the customer entered an invalid order_id (the GPA… value) what response code should I expect from the API? I’m seeing 404, is that correct? What safeguards are there for customers restoring to multiple devices, for example if their order_id became public? Once an order is restored can it be restored to other users? How much protection should I build into my API? Are there any other potential vectors for abuse I s

We use the RevenueCat Purchases SDK for Kotlin, version 9.28.1, on our Android app.In our use case, we want to set or update the user’s e-mail attribute on their RevenueCat profile as part of their logging in to our app. The e-mail is a piece of data that does help during customer support, so we want it to be stored reliably on RevenueCat.We are aware that user attributes are not immediately synced to the RC backend for calls like setEmail(), and that attribute syncing actually happens implicitly as part of other, more significant, events (or with an explicit syncAttributesAndOfferingsIfNeeded() call.) With this in mind, we do these two calls, one right after the other:Purchases.sharedInstance.setEmail(...)Purchases.sharedInstance.logIn(...)We have browsed the SDK source code and it does look like logIn() is one of the calls for which attribute synchronization happens under the covers on the Kotlin SDK (even though that is not mentioned in the documentation), which might mean that we d

Hi everyone,I'm running into the known Billing Library 8 limitation around consumed one-time products, and want to confirm the recommended path forward, plus flag one detail that seems inconsistent.Setup:Flutter app, no login system (anonymous app_user_ids) purchases_flutter 10.11.0 / purchases-android (via hybrid common) Product sfl_pro is a non-consumable one-time product (not a subscription), correctly configured as non-consumable in the RevenueCat dashboard Transfer Purchases setting is enabled correctly Testing via Open Testing track with a licensed tester account (sandbox/test purchases, not production charges)Issue:User purchases sfl_pro on Device A → works, entitlement active. On Device B (same Google account, same license tester, confirmed identical "preferred billing account" identifier in logcat), restorePurchases() returns successfully but with an empty result: activeEntitlements: [], nonSubscriptionTransactions: [],However, if the user tries to purchase sfl_pro again f

This question has been asked before more than half a year ago here:Using offers on new Google Play one-time products | RevenueCat CommunityiOS & Android - In app purchase discount codes | RevenueCat CommunityI want to use the discount function for my one-time product in Google Play. It would be great if RevenueCat would be able to display the discounted price, maybe alongside the regular price so that we can dynamically build texts like--4,99€-- (strikethrough) only 0,99€ How is the current situation and progress on this topic?Thanks for any clarification.

Hi,Google Play has recently published the new guidelines for app optimization with R8 and is actively pushing for it (https://developer.android.com/topic/performance/app-optimization/enable-app-optimization).I want to comply ASAP, but I am also super paranoid about breaking anything related to the payments.I just updated to:```"@revenuecat/purchases-capacitor": "13.4.2","@revenuecat/purchases-capacitor-ui": "13.4.2",``` And I found that the dependency comes with the proguard rule:`-keep class com.revenuecat.** { *; }`I am happy with all that, all I want is to make sure that once I enable this:```minifyEnabled = trueshrinkResources = true```nothing breaks.So I would appreciate the “official” confirmation on this.Thank you!

Hello people,  I just want to understand a bit more on how the revcat Test Store works. First, I tested with a local dev build and it works perfectly fine. But when I got and create a preview build (NOT production, release) build, I get the warning that im using a test key and the app will now close. Is this normal behavior or is there a way to fix this? I dont have the option to use the real app store key on a preview build because I have different build environments along with different bundle identifiers. This would imply that I have to create a new app in app store connect simply to test the native purchase flow. 

Hi RevenueCat team,for my subscription-based app, I recently noticed a bulk of first-time downloads in App Store Connect labeled as “Institutional Purchase”. The app itself is free, with premium functionality unlocked through an auto-renewable subscription managed by RevenueCat.This got me looking into Apple's new WWDC26 organizational subscription volume purchasing.When an organization purchases and assigns a subscription to a user, StoreKit reports a transaction with `Transaction.OwnershipType.assigned`. Will RevenueCat recognize this transaction and expose the corresponding entitlement as active through `CustomerInfo.entitlements.active`, just like an individually purchased subscription?More importantly, will this work server-side/backwards-compatibly with already released RevenueCat SDK versions, or will apps need to ship an SDK update before organization-assigned subscriptions can be recognized? Similarly, when Apple reports `assignmentRevoked`, will RevenueCat automatically deact

If your Paywalls v2 paywall is served through a workflow, the dashboard's play_store_product_change_mode setting gets silently dropped. WorkflowScreenMapper rebuilds the paywall's component data from the workflow payload and hardcodes productChangeConfig to null, so ProductChangeCalculator never runs and the purchase goes out with no oldProductId.End result: an existing subscriber who taps a different tier doesn't get upgraded — they end up with two concurrent Google Play subscriptions, both billed, with no error or warning anywhere. onPurchaseCompleted fires like nothing went wrong.Filed with full repro steps, logs, and the disassembly behind the root cause here:👉 https://github.com/RevenueCat/purchases-android/issues/4002Posting here too because we couldn't find any dashboard or API way to opt an offering out of the workflow path, and setPurchaseLogic is rejected under the default purchasesAreCompletedBy = REVENUECAT (SDK logs a warning and ignores it). If anyone has found a support

Our users' devices report A LOT of these warnings after we updated to the latest KMP SDK:[Purchases] - WARN: Could not resolve remote config blob(s) for 4 of 4 requested item(s) in topic 'ui_config': [app, localizations, variable_config, custom_variables]. Returning null. These are new in our latest Android release, and we're getting 1000s of them reported on Sentry. We haven't changed anything in our RevenueCat config/account, just updated the SDK.Current SDK versions (in which the warning occurs): com.revenuecat.purchases:purchases:10.16.0 com.revenuecat.purchases:purchases-kmp-core:3.4.0 com.revenuecat.purchases:purchases-kmp-core-android:3.4.0 com.revenuecat.purchases:purchases-kmp-mappings-android:3.4.0 com.revenuecat.purchases:purchases-kmp-models-android:3.4.0 Previous release contained these SDK versions (warning doesn't occur): com.revenuecat.purchases:purchases:10.14.1 com.revenuecat.purchases:purchases-kmp-core:3.3.1 com.revenuecat.purchases:purchases-kmp-core-an

On iOS, my Paywalls V2 paywall downloads its custom fonts from fonts.pawwalls.com on every launch, even though the exact same font files are bundled in the app and registered through UIAppFonts. The subsequent registration then fails, and the download stalls the paywall's first render by roughly a second.This looks closely related to this thread: https://community.revenuecat.com/sdks-51/font-are-downloaded-although-they-are-available-7359 — where staff identified "a bug on our end with the font name formatting" and the resolution was to re-upload the font file after the fix shipped. I'm on a much newer SDK than that reporter, and I have re-uploaded the fonts, but the behavior is unchanged.My main question is at the bottom: what is the supported way to have a V2 paywall use an app-bundled font without an uploaded file, so no download is attempted at all?**Environment**- react-native-purchases 10.4.2, react-native-purchases-ui 10.4.2- PurchasesHybridCommon / PurchasesHybridCommonUI 18.19

The support for the native side has been released recently. However, it doesn’t seem like the same support is in place for React Native SDK. Is there any timeline for that?

Recently, we upgraded both our libraries (purchases and purchases-ui) to version 9.0.0 because Google Play required apps to use Play Billing Library (PBL) version 8 or later.Before that we had no issues with our app, purchases worked fine in locall and production enviroment.A few days ago a user issued an email to us that he tried to make a purchase of our one time package(‘consumable’). In revenue cat we saw that he was charged but the item in our app was still locked (indicating the payment wasnt successfull). I tried to trace where was the issue, but i couldnt find out. Today for the first time i replicated the issue and i made the same one time purchase in my local enivorment (sanbox), it registered the payment in revenue cat but i saw these error logs: There was a problem with the App Store. Problem communicating with the Store when trying to validate the receipt.The strange part is this issue happens at random times. After this unsuccessful payemnt i made, i tried a second time a

Components-based paywall: conditional intro-offer row is missing in the firstrender, even though eligibility is already cached## Setup- purchases-ios 5.70.0, SwiftUI, iOS 18- Components-based paywall built in the editor, presented with  RevenueCatUI.PaywallView(offering:displayCloseButton:)- In the editor, a text row ("7 days free trial") is hidden by default and  shown only when the customer is eligible for the introductory offer, by paywall logic.- Product identifiers below are redacted.## ProblemThe paywall opens with that row missing and shows it one render pass later.There is no transition or animation involved — the row simply is not there inthe first frame and is there in the next.The plan card grows upward, so nothing below it moves and the purchase buttonstays in place. It is purely cosmetic. Still, what appears late is the offeritself, which is the one line we would want visible from the very first frame.## What I triedResolving eligibility before rendering, so the answer is