SDKs

I want to fetch state from API in addition to webhook handling, for improved resilience.My subscriptions are credits based, when there’s initial/renewal event, I assign a number of credits to the user.Not sure how to proceed with the transfer webhook event:The user installs the app on device A: they get id 1. The user subscribes. My backend has id 1 → 10 credits.The user installs the app on device B: they get id 2.Let’s say that the backend for some reason doesn’t receive or process the transfer webhook, so it’s not aware that id 1 → id 2Now device B, with its id 2, triggers a refresh from RevenueCat api: I get that id 2 has a subscription.Since I don’t have the old id, all I can do here is to create a new record for id 2 with 10 credits, as if it was a new user. Which is incorrect, because it’s effectively duplicating the credits for the user, who can now use 10 credits on device A and 10 credits on device B.How can I associat

Hello RC Support:The issue described below is in the latest IOS SDK only. The android SDK does not have this issue. The crux of the issue is that presented_offering_id IS NOT matching the product_id and resulting incorrect understanding of which product the user actually purchased.I’ll explain this with an example.We have a few  product_id = Plus , Gold, Platinum. The corresponding presented_offering_id also matches this: i.e. presented_offering_id = Plus , Gold, Platinum.As an example, In IOS when a user purchases a Gold offering on the paywall, we see the following INCORRECT response in the webhook events that we receive. Actual plan purchased by the user: GoldProduct_Id received via webhook: goldpresented_offering_id received via webhook: platinum. In Android, it is functioning properly:Actual plan purchased by the user: GoldProduct_Id received via webhook: goldpresented_offeri

I am using the React Native SDK, and I am getting some PAYWALL_RESULT.ERROR back when users are shown the paywall.I have been searching for what this result means, but I haven’t been able to find many details about this specific error.All I can see is this line from the source code: “If an error happened during purchase/restoration.” I would like to know whether this indicates an error on RevenueCat’s side (such as the server sending 500s) or a store/user error (for example, problems processing the payment).Thanks! 

Platform: React NativeSDK Version: react-native-purchases 8.11.6, react-native-purchases-ui 8.11.6Issue: Bold font weight not applying on Android V2 Paywalls (works perfectly on iOS) Problem DescriptionI have successfully configured custom fonts ("Nunito Sans") for V2 Paywalls and they work perfectly on iOS, but on Android the bold weight is not being applied - all text appears as regular weight even when elements are configured as bold in the RevenueCat dashboard. What Works ✅- Custom font "Nunito Sans" loads correctly on Android (showing custom font instead of system font)- All font weights work perfectly on iOS- Regular font weight displays correctly on Android What Doesn't Work ❌- Bold font weight on Android (appears as regular weight)- Text configured as bold in dashboard renders as regular o

Dear RevenueCat Community,I am using the RevenueCat SDK in my Flutter application and have implemented App Tracking Transparency (ATT) permission on iOS. When the user grants permission, I call the method Purchases.collectDeviceIdentifiers() to obtain the device's IDFA. This value is correctly set and included in the events sent through the webhooks.In my Flutter app, users can purchase subscriptions using Stripe. For this, a web view is opened for the user to complete the payment. Once the purchase is completed and the user returns to the app, the app submit to this endpoint https://api.revenuecat.com/v1/receipts the subscription ids to upload the purchase to RevenueCat. This is how the user gains access to the app features after the purchase.To receive purchase events centra

Hi RevenueCat team,All of my agreements and tax information are already set up and working. I also have other apps where In-App Purchases are working fine. However, with this new app I’m stuck because of Apple’s requirement:“Your first subscription must be submitted with a new app version. Create your subscription, then select it from the app’s In-App Purchases and Subscriptions section on the version page before submitting the version to App Review.”Because of this, I cannot send my IAP for review, and Apple is rejecting the submission under 2.1 - Performance - App Completeness with the note:We found that your in-app purchase products exhibited one or more bugs which create a poor user experience. Specifically, after selecting both weekly and yearly subscriptions an error message is displayed.Review device details:• Device type: iPhone 13 mini• OS

 This code checks to see if a customer should be shown the  paywall.          let customerInfo = try await Purchases.shared.customerInfo(fetchPolicy: .fetchCurrent) let timeInterval = Date.now.timeIntervalSince(customerInfo.firstSeen) let ninetyDays: TimeInterval = 90 * 24 * 60 * 60 return timeInterval >= ninetyDaysThis check is returning false.On the RevenueCat dashboard for this user first seen was 27 June 2024. They never changed their App User ID. However they only seen the paywall today 17 September 2025. Which is much greater than the 90 days. What could be causing the delay in showing the paywall? I appreciate that the customerInfo could be cached but not for over a year.

I am getting the following crashes on Android using revenueCat KMP SDK. And it has increased recently. What could be the issue?The attached two files are of the PaywallState and Purchase click button codes Exception java.lang.IllegalStateException: at com.revenuecat.purchases.kmp.di.AndroidProviderKt.requireActivity (AndroidProvider.kt:83) at com.revenuecat.purchases.kmp.Purchases.purchase (Purchases.android.kt:275) at com.revenuecat.purchases.kmp.Purchases.purchase$default (Purchases.android.kt:266) at utils.PaywallState.purchaseSelectedPackage (PaywallState.kt:29) at pro.ui.paywall.PaywallScreenKt.PaywallScreen$lambda$41$lambda$40$lambda$39$lambda$26$lambda$25 (PaywallScreen.kt:230) at androidx.compose.foundation.ClickableNode.onPointerEvent-H0pRuoY (Clickable.kt:1018) at androidx.compose.ui.input.pointer.Node.dispatchMainEventPass (HitPathTracker.kt:436) at androidx.compose.ui.input.poi

Hi everyone,I have a mobile app that originally relied on $RCAnonymousIDs to manage subscriptions. Now, we’ve introduced mandatory signup, so I’m now working on migrating from anonymous IDs to our own custom user IDs.What’s not clear to me is the best way to handle the transition: How can I merge an existing custom user ID with the old $RCAnonymousID values already in the system? Should this be done via the API, or does the SDK handle it automatically? In some cases, the custom user ID is already listed as an alias of an anonymous ID. How can I “promote” the custom ID so it becomes the original_app_user_id instead of the anonymous one? Has anyone here gone through a similar migration? Any guidance on the best practices would be really helpful.Thanks!

I noticed that we had inflated install numbers on RC vs. App Store. I trust Apple more with the installs, so I went on to find the root cause.We have a Flutter app and I call Purchases.logOut() when a user logs out. This sometimes happens automatically. I now read in the docs that logOut will clear the saved appUserID. This will generate a random user id and save it in the cache.Since RC seems to count appUserIDs as installs, each log-out will count as an additional install. Question: Should I even call Purchases.logout when our users log out? They are still on the same device, with the same Apple ID (most likely). Seems to me that this is wrong and inflates our install numbers.

Hello, I have a flutter app that is working fine on Android but can’t fetch offers from Appstore Connect.  I have verified all the details, from product id, bundle id, products are approves, agreements signed, bank account added, etc.  I can see where the issue lies in any config setting.  What else could be causing this problem?  I went through the “Why are offerings or products empty?” checklist.  I did see where it stated about a shared secret but that was for storekit 1 which is not what we are using.  I have done the certificate for storekit 2.  This is only on iOS.  Any help is greatly appreciated.  

Hello,I plan to use virtual currencies within my app.For me, spending or gaining is straight forward and I will use my backend for such calls.Evaluating the available tokens within the app raises more questions and I tried to understand the official doc here https://www.revenuecat.com/docs/offerings/virtual-currency but I still wonder about some aspects.Exact use case: I need to know within my view models if the user has tokens or not.What should I use: Purchases.shared.cachedVirtualCurrencies or Purchases.shared.virtualCurrencies()?I understand the fact that I need to call the Purchases.shared.invalidateVirtualCurrenciesCache() each time there is a backend transaction, but then what?Is calling Purchases.shared.invalidateVirtualCurrenciesCache()

Something is wrong with the checkTrialOrIntroductoryPriceEligibility function. I'm not sure if I'm doing it right; to be sure, I wanted to share my problem here first.In my iOS app, I use this snippet to check whether there is an eligible introductory price:if (Platform.OS === 'ios') { // Purchases.checkTrialOrIntroductoryPriceEligibility is only available for iOS const introEligibilityStatuses = await Purchases.checkTrialOrIntroductoryPriceEligibility([ pkg.product.identifier, ]); return ( introEligibilityStatuses[pkg.product.identifier].status === Purchases.INTRO_ELIGIBILITY_STATUS.INTRO_ELIGIBILITY_STATUS_ELIGIBLE ); }  In one account, everything works fine—I haven't bought anything with that account yet.But the second account (with expired introductory subscription) returns wrong

Hi, I’ve been using Paywall with Flutter, and it’s been great so far, but it doesn’t handle subscription upgrades/downgrades for Google Play, which is a major issue.Without this essential feature, Paywall becomes almost unusable for managing multiple subscriptions on the Play Store.Are there any solutions to make RevenueCat Paywall work for upgrades/downgrades with Google subscriptions in Flutter?

I’ve uploaded a new version of my app with sdk version 9.5.0 and I’m seeing this error in production, did anyone encounter this?here is the stack trace: com.revenuecat.purchases.CoroutinesExtensionsCommonKt$awaitGetProducts$2$2.invoke (CoroutinesExtensionsCommon.kt:146) com.revenuecat.purchases.CoroutinesExtensionsCommonKt$awaitGetProducts$2$2.invoke (CoroutinesExtensionsCommon.kt:141) com.revenuecat.purchases.ListenerConversionsCommonKt$getStoreProductsCallback$1.onError (ListenerConversionsCommon.kt:36) com.revenuecat.purchases.PurchasesOrchestrator$getProducts$1.onError (PurchasesOrchestrator.kt:517) com.revenuecat.purchases.PurchasesOrchestrator$getProductsOfTypes$1$2$1.invoke (PurchasesOrchestrator.kt:1128) com.revenuecat.purchases.PurchasesOrchestrator$getProductsOfTypes$1$2$1.invoke (PurchasesOrchestrator.kt:1126) com.revenuecat.purchases.PurchasesOrchestrator.dispatch$lambda$63 (PurchasesOrchestrator.kt:1158)

I currently use API v8, there are lifetime products in my app that were incorrectly configured as “consumable” in the RevenueCat dashboard (I fixed that to be “non-consumable” but many users have already purchased these before). I understand that in API v9 (which uses Play Billing Library 8), I can’t restore consumed products. Does that mean that if I upgrade then these products will be non-restorable?In other words, does fixing the products from “consumable” to be “non-consumable” solve the issue for all purchases, or does it apply only to new purchases after the fix?

I have created a Paywall with some icons as you can see in the screenshot attached. But when I try to open the paywall in my app, or even in the RevenueCat app, the icons do not appear.  iOS 26RevenueCat SDK 5.39.0  

Hi.. I’ve got an old ObjC project that uses RevCat.  I don’t rely on the system localization but allow the user to choose the language to override it.. so I want to also override the paywall localization. I found another post that says this is possible in ios: Purchases.shared.overridePreferredUILocale("es")My app is ObjC and generally I can call any func with objC but this one doesn't seem to be found.. trying:[[RCPurchases sharedPurchases] overridePreferredUILocale:@”es”];But that’s not found.. is there a way? Or would I need to switch over and have some swift in my project (I haven’t really done that, I know it’s possible.. just trying to find the easiest solution at the moment) Thanks!D

Hi,In my app, users can manually select their preferred language, since many of them don’t change their phone’s system language to match their native one.Because of this, the app language is controlled through my own state management system rather than relying on the device’s localization settings.The problem is that I can’t find a way to localize the paywall to match this internal language setting.Am I missing something here, or does this mean I can’t localize the paywall at all?This feature is essential for us, and it could determine whether we continue with RevenueCat or need to explore alternatives.Please help!

Error loading subscriptions: PlatformException(23, There is an issue with your configuration. Check the underlying error for more details. 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, {code: 23, readableErrorCode:CONFIGURATION_ERROR, message: There is an issue with your configuration. Check the underlying error for more details. 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, readable_error_code:CONFIGURATION_ERROR, underlying ErrorMessage:

I’m integrating Customer Center into my app (with purchases-kmp) and the Customer Center Composable always shows a blank screen. Any ideas on what could be wrong? https://drive.google.com/file/d/1YT3z5aytElJVvgDZvJHN_VwCV-aRu7X8/view?usp=sharing

We have multiple paywalls configured in RevenueCat and would like to implement dynamic paywall decisioning based on the user’s attributes or behavior.What is the recommended approach to determine and show the correct paywall for each user?Is there a way to manage or customize which paywall is presented at runtime using RevenueCat’s SDK or dashboard?

Getting a bunch of these in my logs12.1.0 - [FirebaseAnalytics][I-ACS023141] Purchase is a duplicate and will not be reported. Product ID: test3Is this from RevenueCat? I’m not sending this data to analytics. Thanks!

I tested successfully purchasing a subscription : I downloaded the app from Play Store, and purchase  it, everything is fine.Is it possible to do the same test when deploying from Android Studio or installing manually the apk ? When I try, I get an error “This version of the application is not configured for billing through Google Play”.Both tests are done on an emulator. Thank you

Hello RevenueCat community,We would like to open a discussion around the initialization behavior of the Amazon Appstore SDK when used with RevenueCat, particularly on Fire TV devices and low-spec kindle tablets. EnvironmentReact Native Purchases: react-native-purchases: 8.11.10 RevenueCat Amazon Store: purchases-store-amazon:8.22.0 Amazon Appstore SDK: com.amazon.device:amazon-appstore-sdk:3.0.5Devices tested:Fire TV Stick (Fire OS 5.2.9.5) Kindle Fire 7, 7th generation (Fire OS 5.7.1.0) Issue observed When configuring RevenueCat withPurchases.configure({ apiKey: REVENUE_CAT_API_KEY_AMAZON, useAmazon: true })we sometimes experience very long initialization times (up to 30–60 seconds). This affects the ability to fetch offerings at app startup.