SDKs

In my app once the user has successfully subscribed and has access to the app, I want to be able to display the current pricing that the user is on back to the user. This is fine if the user is not on an intro pricing plan, but I am having a hard time determining and then displaying this if the user is in an intro pricing period. I am able to find the correct intro pricing using the snippet below, but this does not help me figure out if the user is paying that price or the full price. packageInfo.product.introPrice?.priceString I am using React Native. Thanks

export const extFirestoreRevenueCatPurchasesHandler = onRequest( async (request, response) => { const {processUserCredits} = require("./functions/userCredits"); await processUserCredits(request); response.status(200).send('Webhook received'); });export interface RCEvent { api_version: string event: { aliases: string[] app_id: string app_user_id: string country_code: string currency: string entitlement_id: string entitlement_ids: string[] environment: string event_timestamp_ms: number expiration_at_ms: number id: string is_family_share: boolean offer_code?: string original_app_user_id: string original_transaction_id: string period_type: string presented_offering_id: string price: number price_in_purchased_currency: number

When i build my app on the new sdk i get a coiuple errors:Trying to purchase a plan: ERROR: 😿‼️ There is an issue with your configuration. Check the underlying error for more details. This StoreProduct represents an SK1 product, but SK2 was expected. 

I’m seeing this error pop up in production only, through Sentry logs. It is intermittent -- it looks like most users are able to subscribe successfully. And, I know that in some cases this may be a legitimate situation where someone clicks purchase and then cancels out of it.However, I see this happening a lot more than I would expect if it were just that situation. In addition, I have specific reports of users trying to make the purchase and seeing an error message in my app. When I triangulate that back to the Sentry issue occurring on that device at that time, it’s the “Purchase was cancelled” error.So my question is, if the user is saying they are attempting to purchase and not canceling it, but they are still getting this error back from RC, how can I further debug?For additional context here is the complete error I get back from RC. Again, this happens intermittently when users attempt to make a purchase, even if they state that they did not cancel it:

When I use the price string from the API, we see 12.99 like we have in the Apple app store. However, when I access the price itself in the Flutter client library, I see 12.989999771118164. I am not manipulating this price at all, I am printing it directly from Flutter lib. Do you think this is: 1) Apple weirdness 2) RevenueCat API bug OR 3) Flutter bug?

I have created a product in google play console, and I also created a revenuecat product with the same id, but the the following line of code returns an empty array.// Fetching all products by passing an array of their product_idconst products = await Purchases.getProducts(['product_id']);// Printing the list of products available.console.log(products); // Example response:[]Project info:Expo SDK version: 45 React native: 0.68.2 react-native-purchases: 4.6.1 Device tested: android

Now Apple requires privacy manifest for each third party SDK. We are using revenue cat 6.10.0 and there is no xcprivacy file inside this revenue cat for unity version. Where can I get xcprivacy for revenue cat to use it in unity3d project?

Hello, Team, hope you are doing well.I upgraded revenueCat module to latest one in my ionic/angular project.this is the module in package.json"@revenuecat/purchases-capacitor": "^7.3.1"it’s working on xCode without issue.but I can’t build android build on Android Studio.Execution failed for task ':revenuecat-purchases-capacitor:compileDebugKotlin'.> 'compileDebugJavaWithJavac' task (current target is 17) and 'compileDebugKotlin' task (current target is 19) jvm target compatibility should be set to the same Java version.  Consider using JVM toolchain: https://kotl.in/gradle/jvm/toolchain* Try:> Run with --stacktrace option to get the stack trace.> Run with --info or --debug option to get more log output.> Run with --scan to get full insights.This is the error log when building. if I use old package, the android build will work without error."@a

Hi,While testing my subscriptions on IOS with a sandbox account i found a strange behaviour of getCustomerInfo(), needing to call it twice in order to get the correct data.The way i’ve set my app is to call getCustomerInfo on appLaunch and on appResume, to check for updates. The scenario is the following:I purchase a subscription and get back info that the entitlement is active and my expirationDate is 5min from now (because of the sandbox account). Then i minimize the app and wait 6 mins, after which i can see the sub renewal transaction appearing in rc dashboard and in the customer details screen. I open the app, which triggers getCustomerInfo, but it’s returning the same data i got from when i first purchased the sub. Then when i minimize the app and open it again, triggering getCustomerInfo for the 2nd time, it return the correct updated data with the new expirationDate.Is this the expected behaviour? Is this because

iOS purchases made using a promo code aren’t being recognised in my app. Initially I take a user to the URL below from my app. Once they come back Purchases.syncPurchases() is called. I also have a button in the same page that calls Purchases.restorePurchases(), but pressing that seems to have no effect as well. I do have a listener for any changes in the customer information using this Purchases.addCustomerInfoUpdateListener((info) {}), it starts when the app is opened. Once a promo code has been used successfully and the user comes back to the app and the syncPurchses method is called there is still no update in customer info. My app is in production (available on app store) and I already have in-app-purchses/subscriptions working and fully integrated. What is going wrong here?  https://apps.

Hi all,I have an iOS app created by PWABuilder that Apple have rejected for not having in app purchases. Therefore I’m implementing RevenueCat. However I’m struggling to see where I would add and present the paywall within the code built by PWABuilder. I have 0 experience with Xcode and Swfit unfortunately.Does anyone have any experience of this at all please?https://www.revenuecat.com/docs/tools/paywalls/displaying-paywalls Thanks.

D/[Purchases] - DEBUG( 6814): Request already scheduled with jitter delay, adding existing callbacks to unjittered request with key: BackgroundAwareCallbackCacheKey(cacheKey=[/subscribers/%24RCAnonymousID%3A05155e0681644ad69dc66564531ea514/offerings], appInBackground=false)D/[Purchases] - DEBUG( 6814): Getting storefront from cache was null.D/EGL_emulation( 6814): app_time_stats: avg=9341.14ms min=3.54ms max=130723.25ms count=14D/[Purchases] - DEBUG( 6814): API request started: GET /subscribers/%24RCAnonymousID%3A05155e0681644ad69dc66564531ea514/offeringsD/[Purchases] - DEBUG( 6814): API request completed with status: GET /subscribers/%24RCAnonymousID%3A05155e0681644ad69dc66564531ea514/offerings 304D/[Purchases] - DEBUG( 6814): ℹ️ Requesting products from the store with identifiers: premium, elpa_1299_foreverW/BillingClient( 6814): getSkuDetails() failed for queryProductDetailsAsync. Response code: 2E/[Purchases] - ERROR( 6814): 🤖‼️ B

In the documentation for checking subscription status, it is said that for checking if a user has paid, we need to use the entitlement object like this:if (Object.entries(customerInfo.entitlements.active).length) { //user has access to some entitlement}However, this doesn’t work when a user has used a promo-code on Android. Instead we use:if (Object.entries(customerInfo.activeSubscriptions).length) {//user has access to some entitlement}Is that a correct way to check?

Hello,I’m having some difficulties with implementing Capacitor and Vue 3 for Android.Firstly, I want to figure out how to handle locked areas in my app upon boot. As I understand it, the app will send a request to the RevenueCat API to check the subscription status of each user IDs, which will return either a “subscribed” or “unsubscribed” response.I think the best approach would be to save this status in persistent storage and then develop the necessary logic to lock or unlock functions in my app.Could you please confirm if my understanding is correct?Additionally, regarding the Vue.js part: should I include this logic in the App.vue file?Thank you! if (Platform.is.android) {try {const revenuecat = await import('@revenuecat/purchases-capacitor');const Purchases = revenuecat.Purchases;const LOG_LEVEL = revenuecat.LOG_LEVEL;

When do you plan to add flutter web support? There is a huge demand for it and it seems that you already have the tools to support it?

I recently received several iOS errors with error code 20 (PAYMENT_PENDING_ERROR). I read the documentation here, but am still unsure what’s causing this error and how to resolve it. The users don’t have parental controls on their devices.The RevenueCat docs mention “a user might choose to purchase your in-app product at a physical store using cash” - is this an option the user would have turned on somewhere in their device settings?Or is there a different reason this error could be occurring?  

Hi all!We’re running an A/B-test with a monthly subscription and two pricings both pricings and have the same setup in the AppStore and RevCat but the second package has PACKAGE_TYPE  CUSTOM or UNKNOWN whereas the first has MONTHLY as expected. What could be wrong with the setup?currentOffering.availablePackages.map((pkg) => {let priceTag = pkg.product.priceString;switch(pkg.packageType) { case Purchases.PACKAGE_TYPE.LIFETIME: priceTag += ' einmalig'; break; case Purchases.PACKAGE_TYPE.ANNUAL: priceTag += ' pro Jahr'; break; case Purchases.PACKAGE_TYPE.SIX_MONTH: priceTag += ' alle 6 Monate'; break; case Purchases.PACKAGE_TYPE.THREE_MONTH: priceTag += ' alle 3 Monate'; break; case Purchases.PACKAGE_TYPE.TWO_MONTH: priceTag += ' alle 2 Monate'; break; case Purchases.PACKAGE_TYPE.MONTHLY: priceTag += ' pro Monat'; break; case Purcha

Hello,We are currently using the React-Native SDK. The getCustomerInfo() method provides a PurchasesEntitlementInfo object that contains both the originalPurchaseDate and latestPurchaseDate.originalPurchaseDate: The first date this entitlement was purchased, in ISO8601 format. latestPurchaseDate: The latest purchase or renewal date for the entitlement, in ISO8601 format.Does the originalPurchaseDate refer to the start date of the current subscription cycle? Or does it represent the very first date the subscription was ever started?For example, if Customer A initially began a 1-month premium subscription on 2024-03-01, canceled in 2024-06, skipped payments in 2024-07 and 2024-08, and then resumed the same 1-month premium subscription on 2024-09-01, what would be considered the originalPurchaseDate?In this case:If the origi

Hi all, I’m testing the possibility of extending a subscription.For Apple I managed to get it work by using the https://api.storekit.itunes.apple.com/inApps/v1/subscriptions/extend/ endpoint. This also produced a webhook event. For google I used the https://api.revenuecat.com/v1/subscribers/{app_user_id}/subscriptions/{product_identifier}/defer endpoint. Now, the subscription correctly got extended by the amount specified; using the https://api.revenuecat.com/v1/subscribers/{app_user_id} endpoint to fetch subscriber data I can see the updated expires_date, but I did not received

I am using Unity version 2021.3.29f1 and I am making subscription purchases with IAP version 4.12.2. IAP version supports android payment library version 6.2.1. So I am using RevenueCat sdk 6.10.0. When I try to get a build after sdk installation, I get an error as “com.android.build.gradle.internal.tasks.Workers$ActionFacade”. When I uninstall the SDK, the problem is solved. What should I do?

Hello,I’ve read all the other community posts for this issue and can’t seem to get to the bottom of it. I’ve also been through the Why are offerings or products empty? post.I’m running a Capacitor app with NextJS using @revenuecat/purchases-capacitor 9.0.4. I have configured Purchases with an apiKey and confirmed with Purchases.isConfigured() and Purchases.getCustomerInfo() - both coming back as expected.When calling Purchases.getProducts({ productIdentifiers: [‘my-product-id] }) I’m just getting back an empty array, no errors.My Service Account Credentials JSON is verified and I even imported the subscription product from Google Play, so I know the connection is working ok. When viewing the product within the RevenueCat dashboard I see “Store status: Ok”. The subscription is both active and backwards compatible withi

Im using React Native and have setup my Paywall to include an introductory offer if eligibleFor example - {{ sub_offer_duration }} Free then {{ price_per_period }} Unfortunately my Paywall does not show the introductory offer, even though I am eligible.This is true on TestFlight & SandBox. New users and existing. When I start the Apple Payment Dialogue, Apple actually shows me the introductory offer - So this seems to be a problem with RevenueCat. Does anyone have a solution for this?

Hi Everyone,In the case that a user has a payment problem or their payment is past due, I would like to help them navigate to a place where they can manage their payment info (in case they need to update their credit card number or something similar). The managementURL property just sends the user to a general area for managing subscriptions, but there is no way to manage payment details from there.Is there any way to send the user some place where they can view and update their payment details?TIA!-Mike D.

'm developing a subscription-based app on Flutter for Google Android and have run into a challenge with the platform's limitations on subscription management. Specifically, Google Play does not allow developers to programmatically cancel or modify subscriptions on behalf of users. Users must manage their subscriptions directly through the Google Play interface, which complicates the process of upgrading to a new subscription tier within the app.Challenge: Google Android’s policy requires users to manually cancel or modify their subscriptions, which can disrupt the user experience and reduce conversion rates for subscription upgrades.Proposed Solution: To address this, I am considering a hybrid approach using RevenueCat's customizable paywall feature. The idea is to still use the RevenueCat paywall for managing subscriptions but to augment this with additional UX elements that guide users through the necessary steps to manually cancel t

Probably related to Using React Native PaywallFooterView. There is a general lack of flexibility to control what happens behind this component.I attached a picture of my paywall running on an iPhone 6s simulator running iOS 15. There is no way to control the font scaling for this view, rendering it completely unusable for users who have bigger font sizes. As you can see, my custom paywall design is hidden behind this huge footer.I read that you are currently working on improving paywall design, but still wanted to report this use case so it’s taken into account.