Get Help

I’m trying to generate an In-App Purchase Key on App Store Connect as that’s a mandatory step in the set up process for iOS apps. However, App store connect won’t let me, and also won’t tell me what’s wrong. When I try to generate a key, I get a “error, please try again later” error and then immediately redirected to the home page. In the chrome devtools console, I see a 403 forbidden error. Wtf?

I upload the P8 key file from App Store Connect to the revenuecat with my Key ID and Issuer ID. Everything is correct but it still says that “Credentials are not configured yet” what should I do more to get my credentials validated ?

In the Customer Info (https://www.revenuecat.com/docs/api-v1#tag/customer_info_model) `subscriber` field, there is a dictionary of identifiers to subscriptions. It looks like the identifier is the product identifier from the respective stores. What happens if the same identifier is present on the App Store and Google Play?   

During the Apple review process, the reviewer encountered an "Error 23" message indicating a configuration issue. This has happened twice now, even though I haven’t made any changes to my RevenueCat setup or code since my last successful reviews. In the previous reviews, the reviewer was able to complete the subscription process successfully but rejected the app for an unrelated reason. Now, when I test the subscription flow, everything still works perfectly on my end, so I’m unsure why it’s failing for them.Do you have any insights on what might be causing this issue or how I can resolve it? Could it be related to Apple's sandbox environment, or is there something specific I need to check or adjust in my RevenueCat configuration(even though it worked in the past and is still working)? Would uploading a new build and resubmitting help? I’ve seen others try this approach, but I’d appreciate your advice.Thanks for your help!

Hello,I’ve been looking on already posted questions but didn’t found the answer about that.I’ve been sending some promo codes for my Android and Apple application, the Apple promo code redeemed are marked as TRIAL in my console, but the Google Play ones are marked as a regular purchase with the real price while in the Google Play Console it’s marked with a 0.00€ revenue. My issue here is that I suppose that it’s counted in the MMR (and thus i’ll pay 1% on the revenues if i reach the 2500$ threshold) while it doesn’t make me earn money, so in fact i’m losing money by giving promo code 😫 ? Or maybe the real MMR is recomputed after with the real transactions amount ? I don’t know. Thanks for the clarification :)

Is there a way to add a video to the existing fullscreen paywall in place of the image?

Within a local Xcode testing environment we sometimes run in to the following error (which is received from RevenueCat):Error Domain=RCBackendErrorDomain Code=7638 "There is another request in flight trying to perform the same action."This is the error that we receive back when we try and make a purchase (within the following code block): func purchase(package: Package, completion: @escaping (InAppPurchaseResult) -> Void) { purchasePackage(package) { _, purchaserInfo, error, userCanceled in if userCanceled { completion(.userCancelled) } else if let error = error { completion(.failure(error)) print(error) print(error.localizedDescription) } else if purchaserInfo?.entitlements.all["unlocked"]?.isActive == true { completion(.success) } else {

Hi All,I have more than 15k active user and only handful of people having this issue. The customer created the account but we are unable to see his transaction history, upon further inspection we found out that the user is already paying for the subscription, it’s just RC don’t recognize it.After following the below doc, I realize that we might have to add restore Purchase functionality to overcome this issue. After testing in sandbox we got a weird issue which says :-“😿‼️ There is already another active subscriber using the same receipt.” which is coming from the API with endpoint “/v1/receipts”. NOTE:- Both the sandbox and app account are new so there is no way that the sandbox had an previous purchase history. Now I am a bi

Hi, I thought the only values you see for the period_type field are: TRIAL, NORMAL, PROMOTIONAL. However, see attached. I see a PREPAID value? In the attached picture, the product is a recurring subscription (as opposed to a prepaid/non-recurring product). So the period_type value doesn’t seem to match.Is this a bug in RC? If not, what does this period_type mean? iOS subs continue to use the NORMAL period_type, so am I expected to field different period types, depending on the store? Thanks, Toby

When I try to sync purchases on one of my devices, I get the following error:Error syncing purchases StoreTransaction(orderId=null, productIds=[plus_upgrade], type=INAPP, purchaseTime=1641997886514, purchaseToken=<redacted>, purchaseState=UNSPECIFIED_STATE, isAutoRenewing=null, signature=<redacted>, originalJson={"productId":"plus_upgrade","purchaseToken":"<redacted>","purchaseTime":1641997886514,"quantity":1,"developerPayload":null}, presentedOfferingIdentifier=null, storeUserID=null, purchaseType=GOOGLE_RESTORED_PURCHASE, marketplace=null, subscriptionOptionId=null, replacementMode=null). Error: PurchasesError(code=UnknownBackendError, underlyingErrorMessage=Backend Code: 7651 - The payment for this non-subscription product is not complete., message='There was an unknown backend error.')On the Play Console, I see that this in-app purchase has been refunded and it has a proper order ID.Any idea?

Hey RevenueCat Community, we are currently migrating from Glassfy and are also using the Paywalls feature. What I am missing here from Glassfy is the customisability in Paywalls and not being dependent on Templates as much. As you can see in the Screenshot, there are more values to adjust, variable Button count, Image Carousel, Paddings, Sizes, Margins etc. What I am proposing are similar features in the RevenueCat Paywalls feature. For example:Styling like in CSS: Sizes, Paddings, Margins, Borders (Radiuses)Flexible positioning and amount of ElementsWe are aware that it is aways Possible to natively create a Paywall, but here the huge use-case is that its a no-code solution, so customers can easily adapt and implement Paywalls themselves.What do you think of it and what are

Hi, I’ve been using Paywall with React Native, 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 React Native?

I am using Flutter, fyi.How do I check that the user is logged into their google account (and Play Services) on their device, so that I don’t get an error when I show the paywall?

Hi all,I’m testing the Scheduled Data Export integration but I don’t understand one thing. So there’s this option to only include new and updated transaction records, but how do I know which records are new and which are updated? And for the latter, how do I know which record it replaces? Last question, is there a way to get user events history from api? 

offering] DEBUG: ℹ️ Skipping products request for these products because they were already cached: ["pinqin_10_skill_coins"][purchases] INFO: 💰 Purchasing Product 'pinqin_10_skill_coins'[error] ERROR: 😿‼️ The operation is already in progress for this product.[purchases] ERROR: 💰 Product purchase for 'pinqin_10_skill_coins' failed with error: Error Domain=RevenueCat.ErrorCode Code=15 "The operation is already in progress for this product." UserInfo={NSLocalizedDescription=The operation is already in progress for this product., readable_error_code=OPERATION_ALREADY_IN_PROGRESS_FOR_PRODUCT_ERROR, source_function=addPurchaseCompletedCallback(productIdentifier:completion:), source_file=RevenueCat/PurchasesOrchestrator.swift:986}along with this whenever I am restarting the project , it works fine without this error.

Hi RevenueCat Support,I'm encountering an issue with my app, which was recently released on the App Store. When making a conversion via a sandbox account, the entitlements are not activating, and the CustomerInfo object consistently shows no active entitlements. Here’s an excerpt from the debug log:[DEBUG] Transaction: Optional(<StoreTransaction: identifier="2000000720835399" product="XXXMONTHLY" date="2024-09-20 20:48:21 +0000" quantity=1 >) [DEBUG] PurchaserInfo: Optional(<CustomerInfo: originalApplicationVersion=1.0, latestExpirationDate=Optional(2024-09-20 20:53:21 +0000), activeEntitlements=[:], activeSubscriptions=[:], nonSubscriptions=[], requestDate=2024-09-20 20:53:49 +0000, firstSeen=2024-09-20 20:51:57 +0000, originalAppUserId=EF36029C-E740-4B3C-B14C-1E179B37FD8D,

I’m quite new to RevenueCat, and I’m currently working on a Flutter app targeting all OS.Since the purchases_flutter package is not available for Windows or Linux (please do something about it!), I assume that I need to use Stripe, connected to my RevenueCat account, to display a web page with a Stripe paywall (I use a Payment Link to keep it simple), and then call the RevenueCat REST API to:list my offerings purchase a product through Stripe check if a user has purchased my one-time payment product or not recover a one-time payment purchaseSo I have 2 questions:Is it the right way to do? Why do I need a secret API Key (that, I assume, I need to store on a server), while I only need a public API Key for the Android, iOS and macOS version of my app?Thanks for your help.

Is there a way to send customer data when you use presentPaywall?  All of my customers are anonymous.App User ID$RCAnonymousID:dad1b19971024dfcbb968e83ac87e288I’m using the react node package,import RevenueCatUI from 'react-native-purchases-ui';await RevenueCatUI.presentPaywall({displayCloseButton: false,});

Hello,I’m using Revenuecat SDK in flutter (purchases_flutter 6.30.2).I have an app on Google Console with a free phase of 10 days.When I call Purchases.getOfferings(), I'm getting it, but the duration is expressed as below:period shows P1W3D = 10 days (ISO 8601), which is ok.periodNumberOfUnits = 7 days, which is wrong.Is there a problem in my interpretation or the data returned is inconsistent ? I found the same problem in freePhase.billingPeriod:Thanks for your supportChris

It was working fine a few weeks ago, but now it just crashes every time I try to configure RevenueCat. Issue goes away when I don’t configure it.What do I do?

Is there a way to set custom package name & details on paywalls? Currently, you can only set the same info across all packages. I have different packages that offer different levels of access (which need some description and can’t be purely forced into the name). I see the Siamese (tier) option allows this but the other paywall templates do not. Thanks.

Hello, I'm starting to test the platform and I came across a problem using the Purchases.setAttributes method in Flutter!When I create a customer with the ID: "teste_123", and put some information in the Purchases.setAttributes method, everything works normally. I can see this attribute information both in the webhook and in the platform.However, if I cancel this subscription and make a new one with the same customer, the information is no longer set in the attributes.My code looked like this:  

Hello, I know this has been asked before. Please forgive me for needing clarification. I am currently using `react-native-purchases` version `7.28.1`.  I understand that simply installing this package fulfills the requirement. My application in production uses 7.28.1. Why did I still get a notification that my current release is not fulfilling this requirement? If I submit a new release, do I need to add:  `implementation "com.android.billingclient:billing:7.0.0"` to build.gradle ? Do I need to add `implementation 'com.revenuecat.purchases:purchases:7.0.0'` to build.gradle? Do I need to add `   <meta-data             android:name="com.google.android.play.billingclient.version"             android:value="7.0.0" />` to AndroidManifest.main ?I intend to keep react-native-purchases to 7.28.1 instead of upgrading to 8.2 due to the fact that after the upgrade, I realize Purchases.getCustomerI

I’ve set up a default paywall for my React Native app which updates and displays correctly on my main device (iPhone 15 Pro). However it was rejected from the App Store because when they open it, it shows a much earlier version of the paywall without all the features or formatting included. This is also the case on my Android test device. If the updated paywall is showing on one device, why wouldn’t it work on the others?I should mention that the updated paywall is still not showing correctly on all devices more than 12 hours after creating it (changes update instantly on my main device, though).

I have two subscription set up in play store (Standard and Premium) and i have two base plans in each of these subscriptions ( Monthly and Premium ) . When i upgrade within the same subscription (ex: standard monthly to standard yearly) i use the Proration mode : IMMEDIATE_AND_CHARGE_FULL_PRICE and when i upgrading to a different tier (ex: Standard monthly to Premium monthly/yearly) I use the Proration mode : IMMEDIATE_AND_CHARGE_PRORATED_PRICE. Everything works fine.  The issue I have is that play store allows the user to have more than one subscription. It allows the user to have Standard and Premium subscription at the same time. The way i knew about this is that i signed into an account, bought a Standard Monthly subscription, then deleted the account and created a new account and on the paywall i clicked to buy the Premium Monthly subscription and it bought the premium monthly subscription also and I checked the google play store and the play store account is payi