SDKs

My problem is with iOSMy subscription is registered under the AppStoreConnect and says “Ready for Review”All my Agreements are signed and up to date.My Bundle ID is correctI was able to successfully import my products to RC.My Products,Offerings, Entitlements are created.My app is registered on RC. (appdd508ae716)I am using TestFlight.I am using Expo I can’t think of anything else, I don’t understand why I am still getting this error. I have not tested on Android yet.

 ERROR  Error loading offerings: [Error: 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). React Native + Expo - Testing Revenue Cat on iOS Having trouble getting offerings on my device, however I can get them  on my emulator, but they are in Sandbox mode and show the default of the image below. None of my products on App Store connect are priced at this value.Please help - thanks 

Hello! Our app is being rejected because since we added RevenueCat we are violating the data practices of the Google Families Policy on our Kids App.The rejection explation below:Your app violates the Families Policy Requirements policy. We’ve identified that your app or an SDK in your app transmits identifier(s) that do not comply with our Families Policy. These identifiers may include, but are not limited to Android Advertising ID (AAID).For example, the destinations of Android Advertising ID transmission

Hello,I’m using the latest Revenue Cat SDK (8.4.0) and i’m trying to do the following use case in Sandbox :Subscribe to a monthly subscription Immediately refund it from Revenue Cat dashboard Open the app and see that the premium content is no longer available for the userI’m callingPurchases.sharedInstance.getCustomerInfoWith(fetchPolicy = CacheFetchPolicy.NOT_STALE_CACHED_OR_CURRENT) { customerInfo -> checkStatus(customerInfo) }And always get this Logs : Retrieving customer info with policy: NOT_STALE_CACHED_OR_CURRENTℹ️ Checking if cache is stale AppInBackground trueℹ️ Vending CustomerInfo from cache. Something weird here, is that AppInBackground is always returning TRUE. This means that the cache will not be stale before the 25 hours delay and never within the 5 minutes delays for

How to display paywall in flutter app?

Hi, I’m new to RC and this forum. I’ve searched but couldn’t find anything definitive on this topic but if there is, please let me know…Is there a way in StoreKit 2 (and in extension, in the RevenueCat SDK) to get an unique identifier for the current iCloud ID or user? I'm a bit worried about this part in the SDK docs:If you don't provide an App User ID when instantiating the Purchases SDK, RevenueCat will generate a new random App User ID for you and cache it on the device. In the event that the user deletes and reinstalls the app, a new random App User ID will be generated.I guess my question is: do I have to force the current user to sign in with their Apple ID if I want to prevent the quoted behavior?Edit: Or did I overthink everything again — maybe I should ignore the iCloud ID for my iOS/macOS-only app, and just rely on the RC-provided anonymous App User ID and the 

Hello,I have a Flutter application using GetX for state management and a Laravel backend. My app includes a subscription feature, but it was rejected by iOS because I need to integrate in-app purchases. Can anyone help me integrate in-app purchases specifically for iOS? I successfully connected the application from the iOS side with Revenuecat, but I'm stuck and unsure how to proceed to complete the integration.

Hi,  Looking at the documentation for custom attributes, I cannot find any information about syncing attributes and offerings using the React Native SDK. Does this mean that it is not required to sync attributes and offerings after setting an attribute or that it is not possible to sync attributes and offerings manually? We are trying to create a targeting rule based on custom attributes set during the onboarding. Curious to learn what the best practice is here. Thanks in advanceAlexander

I can’t pass the App Store Reviews because of this error. I can't produce this case. But review team is keep sending me this. And I can’t pass the reviews for 3 days. On my side, everything works very well.  

I’m using Ionic with Capacitor.The RevenueCat documentation recommends using a cordova plugin, but Ionic has been in the process of migrating away from Capacitor for the past few years, and this is now the only Cordova plugin in my app.There’s already a capacitor plugin on github but I was wondering if there are any plans to release an official Capacitor plugin as well.

I use BugSnag to capture my errors and report them in a way that can be quanitfied.  This last week my top 2 errors all came from `Purchases` errors:Seen in the last 7 days:Errors Events getOfferings Error in Paywall • src/features/Paywall/index.tsx:165 There is an issue with your configuration. Check the underlying error for more details. 140 Purchase Error in Paywall • src/features/Paywall/index.tsx:197 No Package available to purchase. 34  Now, the typical response from RevenueCat is:Do you have logging enabled? YES ``` Purchases.setLogLevel(Purchases.LOG_LEVEL.DEBUG); await Purchases.configure({ apiKey: APIKEY }); ``` Can I replicate? NO  So

Hi!Main Flow:My backend listens to Revenue Cat webhook events. I listen to renewal to mark old subscription as in active and create a new active subscription with full in-app balance.Currently if user clicks on product he already purchased, Revenue cat react native client throws error with code Purchases.PURCHASES_ERROR_CODE.PRODUCT_ALREADY_PURCHASED_ERROR which is correct. But then I get webhook event on purchase. Question:Why this happens if Apple doesn’t let to re-subscribe to plan which hasn’t expired yet. From my understanding after client PRODUCT_ALREADY_PURCHASED_ERROR was thrown no webhook event should come to backend. 

I am trying to use RevenueCat for selling consumable products on my ReactNative mobile app. To start with, I configured a product in my revenuecat account, connected it with a in app product on Google Play. In revenuecat, I can see the two are connected properly. I do not have any offerings or entitlements, because these consumable products are open for all users.However, in my code, when I queryPurchases.getProducts(["productId"]) get an empty array. Struggling for two days, not able to guess what could be the issue? Can you please help?

Hello there. We developed an app that's for both platforms, iOS and Android, the app allows users to purchase a subscription. The iOS version is working fine, but I'm trying to implement same functionality on Android, using either purchaseStoreProduct or purchaseSubscriptionOption. The first one gives me message that the item to purchase is not found and the second got stuck forever and gives no error.Can you help me please? I'm using the 7.2.8 version of the lib.

I am trying to use RevenueCat for selling consumable products on my ReactNative mobile app. To start with, I configured a product in my revenuecat account, connected it with a in app product on Google Play. In revenuecat, I can see the two are connected properly. I do not have any offerings or entitlements, because these consumable products are open for all users.However, in my code, when I queryPurchases.getProducts(["productId"]) get an empty array. Struggling for two days, not able to guess what could be the issue? Can you please help?

As discussed in the post linked below which seems to have comments closed, the migration guide points to the Firebase docs for tracking StoreKit 2 transactions in Firebase.However, it’s not clear from the sample code provided by Google/Firebase how this would integrate with RevenueCat exactly.Does it matter if `await transaction.finish()` is called after `Analytics.logTransaction(transaction)`?Guidance appreciated. Thank you.func purchaseSomeProduct(_ product: Product) { // Purchase a Product. This is mostly standard boilerplate StoreKit 2 // code, except for the Analytics.logTransaction() call. let result = try await product.purchase() switch result { case .success(let verification): let transaction = try checkVerified(verification) // Call this Firebase API to log the in-app purchase event. // NOTE: How do we hook in to this specific poin

Hi,When can I expect a RevenueCat Unity SDK update to include latest RevenueCat Android SDK changes?.Thanks

When a user logs in, it pulls their app user ID then performs the login() function on that ID.I have a real active subscription with my live app on the app store with my App User ID.When I run my app in TestFlight and login with the same App User Id, my entitlement is granted and it loads my CustomerInfo from my Live account. I thought this was an isolated environment?

“This method will send all the purchases to the RevenueCat backend. Call this when using your own implementation for subscriptions anytime a sync is needed, like after a successful purchase.”Source: https://sdk.revenuecat.com/android/5.0.0/purchases/com.revenuecat.purchases/-purchases/sync-purchases.htmlIf I understand correctly syncPurchases:1. upload the local device’s receipt to RevenueCat2. Transaction might under another app user id, so if needed transfer going to happen.3. The user access all entitlement based on the device’s receiptIs it correct? If yes, I don’t understand why need to call “like after a successful purchase.”.I assume purchaseProduct make a full sync with RevenueCat backend after the purchase, because the app should send the curren

Hello, I’m having the following error on iOS platform in my Unity game. PurchasesHybridCommon/CommonFunctionality.swift:21: Fatal error: Purchases has not been configured. Please configure the SDK before calling this method.Not all my users face this error and I cannot reproduce it on my devices. I just can see them on Crashlytics.This is how I configure Purchases:  

We are occasionally seeing cases where a user is able to start a subscription but their email is not associated with the user in the RC dashboard.  Our code pretty straightforwardly should not allow this. The below snippet is the only place where we call `Purchases.configure()` and we immediately set the email attribute.fun initializeRevenueCat(user: User) { if (user.email.isEmpty()) { return } val config = PurchasesConfiguration.Builder(...).build() Purchases.configure(config).also { it.setEmail(user.email) }}Is this a bug in the RC Android SDK or are we missing something in usage?

Hello!Our app was rejected due to the same issue discussed here: It appears that the solution given in that thread was basically to not use the sandbox - but the App Store reviewer uses the sandbox to test and validate our app?We were able to get things working by restoring purchases prior to trying to view the introductory offer. However, as you can imagine, it is difficult to communicate this issue to the App Store reviewer.I have some follow-up questions on this:Is this an App Store Sandbox issue or is there an issue with the RevenueCat SDK? Has a bug report been filed with Apple that we can reference when responding to the reviewer? Is there some sort of additional functionality we should implement in our app to make sure we don’t exp

Flutter, iOSI’m able to subscribe through paywall, able to fetch offerings and products. But when deployed to testflight it doesn’t work. I get error that error with configuration and can’t fetch products. The subscription in applestore connect hasn’t been approved and is in the state “Waiting for Review”, if I submit a build it gets reviewed and rejected stating that they got an error when opening the paywall, the error is the same as above. Can anyone help me out?

 Hi,Im using purchases_flutter: ^6.30.1 in my flutter app to handle downgrade and upgrade for subscriptions.im getting issue in android while downgrading  await Purchases.purchasePackage call does not resolve when GoogleProrationMode.deferred is used.Expected behavior: The await Purchases.purchasePackage call should resolve, allowing subsequent code to execute Actual behavior: The await Purchases.purchasePackage call does not resolve any help regard this ?

Android is requiring all Appstore submissions target API Level 34 from 8/30 onwards. This involves moving from @capacitor/core 5.x to 6.x. The https://github.com/RevenueCat/purchases-capacitor SDK is currently set to require @capacitor/core 5.x. Will there be an update to target 6.x?