Learn and Share

Dear dev team,I noticed that when I use one paywall for both web and android, the dark mode seems have some issue with render all background. Please see below:This is how it looks like in my browser: there are 2 big white sections besides the major section this is how I set it in paywall editor, I am not sure if I missed any settings 

Hi,                                                         We're stuck in an App Store review loop (Guideline 2.1 - Information Needed) and looking for advice from others who may have faced this.  The situation:  1. Apple reviewer logs in with our demo user and makes a Sandbox purchase  2. We provide a new demo user so they can test the paywall  3. When the reviewer logs in with the new demo user on the same device, the existing Sandbox subscription transfers over — because the reviewer's Sandbox Apple ID  hasn't changed  4. Every new demo user immediately has an active subscription  5. Apple keeps rejecting with the same "we need a user with expired subscription" template  Key insight:  The Sandbox subscription is tied to the reviewer's Apple ID, not to our demo user. No matter how many new demo users we provide, as long as the reviewer uses the  same device and Sandbox Apple ID — they will always have an active

Hi RevenueCat team,We’re using Virtual Currencies (beta) for an AI product, and we’ve hit an important gap that I think affects many AI businesses.For most AI subscription products, usage credits are modeled as a monthly allowance, even when the customer is on an annual plan.  Today, RevenueCat grants currency on purchase/renewal (billing cycle), which means annual subscribers get all credits up front.That creates two major problems:We can’t natively do a monthly drip grant for annual plans (e.g., +X credits each month). We can’t natively do monthly expiration/reset of that monthly allowance within an annual subscription.Because of this, we had to build and maintain external scripts/webhooks to:Grant monthly credits to annual subscribers Remove/expire prior month’s credits (non-rollover policy)This is fragile and

Hi everyone,I’m looking for a way to update the main Call-to-Action (CTA) button text dynamically depending on which package the user selects. I don’t find how to do it… without the toggleCase: If the Weekly package is selected (which has a free trial enabled), I want the button to display: "Try for free". If the Yearly package is selected, I want the button to display: "Continue". Has anyone implemented this kind of conditional UI before? Any tips would be greatly appreciated!Thanks in advance!

I am currently finalizing a paywall design using the RevenueCat Paywall Editor (Tabs component).I have a specific design requirement where the pricing text displayed below the main card needs to change dynamically when the user toggles between the 'Annual' and 'Standard' tabs. Currently, that text remains static regardless of which tab is selected.Could you clarify the correct layer hierarchy for this? Do I need to nest the text layers inside the specific Tab Content folders to ensure the variables (like {{ product.price_per_week }}) update according to the selected package, or is there a different method to link text visibility to the active tab state?

Hello, while inspecting my RevenueCat panel, I noticed something.I offer Ad-Free usage in my application. The user first started using the app in July 2023 and has been actively using it. They made their purchase today, exactly 2.5 years later.To convert such long-term users to paying sooner, I think adding a criterion in the experiment screen, such as "Show B paywall if X time has passed since first open," would solve my problem.For example: "Hey, we've been together for over a year. blah blah"I'm presenting this idea to you. Regards.

Currently, our app uses device ID as the RevenueCat App User ID.On Android, when a user:- resets the device, or- switches to a new phoneThe device ID changes, which causes the App User ID to change as well.Recently, we’ve received many user complaints about being unable to restore their purchases.What we observed:- After device reset or device change, the user is treated as a new App User ID in RevenueCat.- The previous purchase is still visible in RevenueCat under the old App User ID.Using the order ID, we can manually locate the old App User ID and transfer entitlements manually, which works.However, automatic restore does not always transfer entitlements, even though:- The purchase was made with the same Google account- We are calling restorePurchases() correctlyExpected behavior (our understanding)From RevenueCat documentation and theory:When calling restorePurchases(), RevenueCat should

Hi, Is this normal to not having data at the Customers > Sandbox page?Thanks! 

Anyone knows how to change the blue color of the buttons in the image please? As in the design they are buttons that are linked to another websites.

Hello RevenueCat community 👋Kindly ask for your support or any ideas.I have a paywall with:• a toggle that switches between a yearly plan with 3-day free trial and a weekly plan without trial, and• package cards that the user can tap directly (yearly / weekly).When the user changes the toggle, the selected package and CTA text update correctly:• Yearly + trial → CTA: “Start free trial”• Weekly (no trial) → CTA: “Continue purchase”But if the user ignores the toggle and taps a package card directly, the toggle position and CTA text don’t update — they stay in the previous state, which breaks the business logic.How would you recommend structuring the logic / configuration so that the toggle and CTA always reflect the currently selected package, even when the user taps the package directly?I’m attachin

I’m using Stripe Server-to-Server notifications with RevenueCat, and I want to confirm whether it’s possible to automatically set RevenueCat customer attributes from the Stripe metadata included in events such as checkout.session.completed, invoice.paid, or customer.subscription.updated.Is there a built-in way for RevenueCat to read Stripe metadata and store it as customer attributes (for example, email, app_user_id, or custom fields)?Or are we required to manually call the RevenueCat POST /customers/{app_user_id}/attributes API to update customer attributes after receiving Stripe webhooks?Any recommendations or best practices for keeping Stripe metadata synced with RevenueCat customer attributes?

 I’m currently using Stripe Server Notifications in RevenueCat, and I’ve found that I cannot directly update customer attributes from this flow. Because of this limitation, I implemented the following approach and would like to get feedback on whether it’s safe, reliable, and recommended.The approach I’m using: I create a RevenueCat customer using the user’s sessionId as the app_user_id  After creating the customer, I update their attributes—for example, adding the user’s email. In RevenueCat, I configured it so that metadata is pulled from the app_user_id assigned to the customer. During checkout, Stripe Server Notifications correctly map the transaction to the RevenueCat customer using this app_user_id. My question:Given that Stripe Server Notifications do not allow

Please support Harmony 😁

I’m an expo / React native dev. I’ve been stuck testing on a physical device because my simulator could never get past:Error fetching offerings. There’s a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect.On TestFlight, physical device testing, and production, everything worked smoothly. It was just the simulator. Something I wish the docs stated that ChatGPT helped with was:In your scheme, make sure your Debug scheme, under options, set the StoreKit configuration to your StoreKit config file. Even if you assume you did, make sure it’s still there since expo, when updating versions, may delete your `ios` folder. This was the thing that helped: assuming everything else worked, running `npx expo prebuild` then opening my xcworkspace file in iOS in XCode itself then running it from Xcode actually made it work. Then, you can go back to running `npm run ios` afte

Hi RevenueCat Team! 👋I'd love to request a highly needed feature that would significantly improve the user experience for apps with custom language selection functionality.## The ProblemCurrently, RevenueCat paywalls automatically determine their display language based on the device's system locale settings. While this works great for most cases, it creates a major UX issue for apps that allow users to change the app language independently from their device settings.*Current limitations:*- Paywalls always use device locale, ignoring in-app language preferences- No way to programmatically specify which localization to display- Users see paywalls in different languages than their chosen app language- Particularly problematic for language learning apps, international apps, and apps targeting multilingual users## Proposed SolutionAdd an optional locale or language parameter to paywall presentation methods across all platf

My app has a monthly subscription and a one-time IAP for access.Currently, if the user has a monthly subscription and chooses the one-time purchase later on, the monthly subscription does not cancel automatically and it will continue to bill the user the monthly sub until they cancel it. I was looking for a way to add a description to the native iOS confirmation sheet but that doesn’t look possible. I can add language in the paywall as well but that might look a bit messy but this seems to be the best option so far. I dont believe users can make IAP from settings or anywhere outside of the app itself right? How have folks communicated something like this to users?

Restoring purchases is a mechanism by which your user can restore their in-app purchases, re-activating any content that had previously been purchased from the same store account (Apple’s App Store or Google Play).By not including a method to restore purchases, users could lose access to existing purchases to which they are entitled. This isn’t ideal, so it is strongly recommended that you include some way for users to trigger the restoreTransactions method, even if you require all customers to create accounts.What happens when a user restores purchases?When a user restores purchases, the Purchases SDK syncs the user’s device receipt with the RevenueCat backend. The device receipt contains unique information about the user’s transactions so that RevenueCat is able to pair the transactions to an app user ID a

Launching a brand new app (iOS) with 1 in-app purchase seems complicated.The issue is:I cannot set a default offering if the in-app purchase is still “Waiting for Review”. Then the paywall will display RevenueCatUI.PaywallError3. Solution: Get your in-app purchase approved. My in-app purchase won’t be approved by Apple if the Paywall is not properly displayed. Also, Apple won’t approve the purchase if the App cannot be approved. Solution: Get your paywall fixed.  Here is what I got:@objc public var current: Offering? { guard let currentOfferingID = currentOfferingID else { return nil } return all[currentOfferingID]?.copyWith(targeting: self.targeting)}Will always return `nil` because there is no current offering marked as default (see point 2) in my dashboard. That means that if you use `Pa

HiI'm building a desktop application for macOS using Tauri .I need to integrate RevenueCat for in-app subscriptions with Apple App Store.I've been looking into the process, and it seems to involve bridging Rust with native macOS (Swift/Objective-C) RevenueCat SDKs via FFI, which I'm not familiar with.My main challenge is that I don't have experience with Rust's FFI, Swift, or Objective-C.Has anyone successfully integrated RevenueCat into a Tauri macOS application? If so, could you please share: Your recommended approach: Did you find a way to do this primarily from the Rust side (perhaps using an existing Rust crate or a simpler FFI pattern)? Or did you have to write a Swift/Objective-C wrapper? Any existing examples or boilerplate code: A minimal working example would be incredibly helpful. Alternative strategies: Are there any other ways

I too encountered the issue with getOfferings not working on Android. It was baffling because the revenuecat configuration (offering > product > entitlement)  was correct, and standalone api calls worked ok. All iOS tests worked fine, yet in Android I got errors. "There is an issue with your configuration. Check the underlying error for more details."and upon digging deeper into that message:“None of the products registered in the revenuecat dashboard can be found in the google play store” For me, the issue was that I was using the WRONG API KEY when initiating revenuecat in a given function. I was trying to be “too agnostic”.  // I was feeding the iOS api key when initiating revcat, thinking it was a global API key. await Purchases.configure({ apiKey: revenueCatApiKey }); // Then of course the rest of code worked fine on iOS....const offerings = await Purchases.getOfferi

Hello. I have read all the existing posts on this issue, but am still stuck.My Flutter app has been successfully processing purchases via RevCat for over a year, but following publishing the latest version of the app, iOS users are getting Error #23 when trying to purchase: “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”I have changed nothing in the app in the latest version relevant to this issue except increased the iOS deployment target version to 18.0.I have checked all the suggestions mentioned in this form posts (signed agreements, financial setup, correct API keys, etc.), all looks fine and has not changed.purchases_flutter version is 8.7.1The code that produces this error is: offerings = await Purchases.getOfferings();Please help me diagnose and solve

Basically it works like this: When a user downloads the app, he immediately is given 7 days of premium access, for free without opt-in into a subscription or anything, just by default. Then after 7 days, you show him the paywall where the user can choose a a monthly or yearly offer, if he doesn't choose a subscription, he loses the premium access. You communicate all of this clearly upfront (the user also sees a banner in the app saying "5 days left"), so the users knows that he is in the "trial" period. Of course the advantage is that basically all users "enter" the trial phase, but the trial to paid conversion will obviously be lower. But in total the paid users should be more hopefully, if product-market fit is great.Anyone tried this out yet? You have data on how your download to paid conversion rate improved? By how much? Can someone recommend this strategy and back it up with data? That would help a lot! Thank you very much!!

I was getting this error when trying to fetch products: SERVICE_UNAVAILABLE: Error fetching products. An internal error occurred. Nothing happened when trying to initiate a purchase. After checking everything in the code and console, the fix was simple:🔑 The device was logged out of Google Play. Once I logged back into a Google account in the Play Store app, everything worked. Just sharing in case it helps someone else save time