General Questions

I made and remade this service account credentials JSON multiple times and it still won’t work. I even created a new google cloud project and made a new service account there. Did the whole process outlined in the docs to create the service account with pub/sub admin etc and it fails to work.  I keep getting an error that the “credentials need attention”. It doesn’t seem to have any problem accessing my subscription products in the google play console. However, in each product it also says beside “Store Status” - “Could not check” and “Connection issue - Make sure the service account credentials JSON is configured properly.” Has anybody else had issue like this and managed to resolve them?  Thanks,  Jay

I originally went with glassfy 2 years ago because their docs and setup for capacitor were simpler to understand.  Unfortunately, they’ve now gone defunct, so I need to migrate to RC.  have two apps that I need to migrate. One app is very seasonal, so glassfy may not exist any more when the users finally open their app. The other, I had issues with android not sending the subscription into to glassfy anyway, and their support refused to respond. My main question:can I simply call syncPurchases once for all users the first time they run the updated app version that has RC integrated?If I can simply call syncPurchases once on update, and each user who does this will automatically be given their subscription access, that would be great.  Can anyone confirm this would work?  Or do I need to do something more complicated?

I’m new to RevenueCat and am looking into how I can migrate my existing app’s non-consumable in-app purchases to RevenueCat.I know this type of question has been asked several times, but none of the answers really answered my questionSo far, I’ve looked at using syncPurchases() but as stated in the documentation:Google Play Store does not provide an option to mark IAPs as consumable or non-consumable. RevenueCat's SDK will consume all Android IAPs upon purchase.To replicate the behavior of a non-consumable IAP for Android users, you must ensure your user will not offered the IAP after the initial purchase. Failure to do so will enable the user to re-purchase the IAP. ...and sure enough, in initial testing, as soon as I call syncPurchases() all of the user’s in-app products are consumed and the Google Play Billing client no longer sees the purchases.Regarding the first paragraph, when using the Google Play Billing API, we have the option to consume, or not consume the in-app purchase. A

 I get the error in the title when I run the followingawait Purchases.purchaseProduct(product.identifier);I have verified that the Product Id is the same as the one in App Store Connect.Bank account and taxes are already set up.What is the problem and how do I fix it?

I am making a test purchase for a monthly subscription. It happens correctly the first time and for the correct user. I am using the always accept visa card from google testers. There is exactly one renewal happening which is fine and the second time I get CANCELLATION with BILLING_ERROR on the sandbox. 

I have few apps and I would like possibility to share subscriptions between them. So if a user is subscribed in one app they would have possibility to use pro features in other apps as well. Is it possible now with RevenueCat?

Been getting this error after adding the service account credential JSON, I’ve made sure that I followed the documentation: https://www.revenuecat.com/docs/creating-play-service-credentials but haven’t been able to resolve this.

After having subscriptions working correctly in my apps on ios and android, since yesterday I have started receiving an error when connecting to the android play store and it is not possible to make a subscription on android. Anyone know what might be happening?

I created this app with Expo and made a couple of offerings with Revenuecat. Now I want to test it. The packages appear,I hit subscribe, The popup appears, I write password and hit subscribe, It says done (without the tick appearing, just a circle) and the whole popup disappears, but after 3 seconds, the purchase popup (Sandbox) reappears again and again. No matter how many times I hit subscribe, it says done and re-appears. There is no record of subscription in my Revenuecat account (yes the sandbox checkbox ticked), and I have registered a sandbox user (valid email with a password) on App Store users. I’m very new to Sandbox testing and I use iOS simulator (17). Does anyone know what to do form here? Checked the Internet and not much was found. By the way, the code does not seem to go through anything after the purchase, it does not show the `console.log` after the function: Here’s the purchase function:  const subscribe = async(item) => { try { const {purchaserInfo} = aw

Hello, I have this error from RevenueCat: code: 23, 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 domain: RevenueCat.ErrorCode, userInfo: "readableErrorCode":"CONFIGURATION_ERROR","readable_error_code":"CONFIGURATION_ERROR","source_file":"RevenueCat/OfferingsManager.swift:237","source_function":"createErrorForEmptyResult(_:)","NSLocalizedDescription": 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-off

Something strange has been happening over this last week. Each user who starts a free trial has it automatically cancelled due to a billing error. Event data reported by RC contains "cancel_reason": "BILLING_ERROR".The app currently looks for billing issues (via billingIssueDetectedAt  in RCEntitlementInfo) and guides the user to update their App Store billing. Beyond this, to prevent revenue loss, I’ve switched to a discounted offering without a free trial while I figure out what’s going on.For context, it’s an iOS app using Purchases v3.11.1 (although this is probably not an SDK issue).Any ideas as to what’s happening here?

We are using Paddle for web subscriptions and aren’t sure how to link userIDs and sync status with RevenueCat. Is there a way we can post userIDs and subscription status to RevenueCat so that when the user logs in on iOS we know if they are subscribed or not. The reason I want to do it this way is because otherwise we’ll have to create a new layer on our backend that tracks subscription status for all users and we will need to check that instead of the RevenueCat SDK which kind of defeats the purpose.  Otherwise, we could first check if they are RevenueCat subscribed then check our backend too - which would work I think. But isn’t there some web sdk for subscriptions?

I was thinking about uploading my React-Native Android App to Huawei AppGallery.I use IAP using RevenueCart with iOS and Google and was wondering, whether Huawei support is already available / planned / not possible.Thanks in advance!

I can’t fetch data from StoreKit testing framwork  for test in app purchase on myappbelow this error messageflutter: fetchOffers error PlatformException(23, 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, readableErrorCode: CONFIGURATION_ERROR, code: 23, message: 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, underlyingErrorMessage: }, null) This is my step 1.I create StoreKit Configuration file on Xcode 2.Create subscriptionSubscription3.I config schema import StoreKit ConfigurationImport file config4.I export cerification

none of the products registered in the revenueCat dashboard could be fetched from the play store 

I am getting the V2 Paywalls setup.  I have it working on my Simulator just fine.  Now I am testing an actual device & my Paywall gets stuck.the `applicationId` is the same on both. I was originally calling `await Purchases.getOfferings();` so I could show my custom loading instead of the loading paywall UI.  But that was getting stuck also.There are NO errors in my logs.   I  do have `MISSING_METADATA` warnings, but isn’t that OK because it’s a “DEV” bundle and will never actually be submited for approval.  Plus, it renders on the simulator.  That being said, I have added screenshots so they’re now “Ready to Submit”. Is there something different about my physical iPhone compared to simulator? Android is OK on both simulator & device

hi, i use flutter with the latest packages versions. I get the following message: but i have configured a paywall:  what could be wrong? i already run flutter clean and reinstalled the app.   

{all: {}}The issue is occurring in iOS as well as Android.The product identifiers are same in the appstore as well as revenuecat. All agreements have been signed. There is a working version of RNIAP which we are replacing with revenuecat.I am not using any sandbox, directly testing on my device.How do I go about resolving this issue?

I am looking to be able to show unlocked features in a web based version of my app. If I make it so users can subscribe in either the iPhone or Android store but still access un-locked content on the web or desktop versions?  

I am pretty new to Revenuecat. Sorry if this problem is answered a hundred times, but I could not find a solution. Here is my problem:I do have an iOS app and have a paywall view. The user can either subscribe for a monthly or annual payment (I managed to set this up in App Store Connect and Revenuecat and this all works fine), or he can select a free trial for 14 days.I know, that I can set up a free trial in app store connect, but as far as I understand, this automatically will start a chargeable subscription, if he does not cancel before the end of the trial period. So in fact the free trial is part of subscription and the user has to choose a subscription method at the paywall. This seems not very appealing to me.I rather would like to say: “Click here and have a look”. When the user clicks ‘here’ then(!) the free trial period starts (without selecting a subscription method). During the free trial I can present a counter: ‘X days left’. After 14 days the user cannot access the cont

Hello, Any ideas as to why the app will be receiving active entitlements even months after the subscription has expired? Currently I have an app in production, and while going through some of the “Expired” accounts, I noticed that a few of them are still active with the application. I have checked, and double checked, tested the logic of the app and it seems as if it should block the person from using the app and being directed to a subscription page. However, the only reasonable explanation as to why the users are still having access to the app would be if RevenueCat’s SDK is sending back an active entitlement.  I have a method, that each time the app becomes active is called, this method is in charge of verifying that the user has an active subscription each time the app becomes active. Within “checkForActiveSubscription()” I call the “purchaserInfo” to get the latest information from the purchaser as per the instructions on how to check for active subscription on the documents. Side

Hi, I am new to programming and RevenueCat.  My IOS app has a subscription purchase option and the user was able to make a purchase, which I think shows up in Revenue Cat but I am not 100% sure as I don’t know how to directly relate the RevenueCat app ID to the user.  Fortunately, at the present time I do not have a large number of users so I believe I have identified the user correctly. However, when the user logs and the app queries  Purchases.shared.purchaserInfo, the entitlements comes back as nil.   I have searched the documentation and can’t understand what I have done wrong and am at a loss of where to start troubleshooting.  Any help would be appreciated. Thanks

Hi.I have used the Revenuecat extension for firebase for a while, but have not found the use of it as I cant see custom claims in the idTokenResult.I want to use custom claims to only allow users with subscription to upload files and then use this custom claims on firestore rules instead of only checking permission inside the application.I have configured the extension in revenuecat and enabled custom claims in the extension:Should custom claims be set in Firebase Auth with the user's active entitlements? DescriptionENABLEDBut when i fetch the entitlements in application, i only get theese:user?.getIdTokenResult(true).then((value) => print(value));{   "firebase":{      "identities":{         "email":[            "x"         ]      },      "sign_in_provider":"password"   },   "user_id":"x",   "aud":"x-app",   "exp":"x",   "iat":"x",   "iss":"x",   "sub":"x",   "email":"x",   "email_verified":true,   "auth_time":"x"}Any suggestions, or cant revenuecat set custom claims that i can use

Hi I am seeing this message in my App Store Connect, The SHA-1 intermediate certificate used for signing App Store receipts expires on January 24, 2025. If your app performs on-device receipt validation, make sure it supports the SHA-256 algorithm; alternatively, use the AppTransaction and Transaction APIs to verify App Store transactions. Learn More I checked the docs but couldn't find anything regarding that.Is there something we should do?I am using Flutter in my client with version: 8.2.2.

I use Paywall(Beta) . I want to translate into 20 languages, but I'm stuck with the character limit. How can we fix this?localized_strings: must be less than 4000 characters