Get Help

Hi,Im having a hard time getting my app through ios review.Specifically failing it because my rc pay wall shows Error 23 and I get this message in the log…Your products are configured in RevenueCat but aren't approved in App Store Connect yet. This prevents users from making purchases in production. Please ensure all products are approved and available for sale in App Store Connect But I think Im seeing error 23, because apple are not approving my Monetization section.Specifically the app store localization keeps being reject. Is the good hypothesis? That in order to stop error code 23, I need to apple approve the localizations?Im just going round in circles with them

Hello, I’m using react native (react-native-purchases and react-native-purchases-ui both at 9.7.0) for my iOS-only app. I’m displaying a paywall to my users via const result = await RevenueCatUI.presentPaywall({ offering });The paywall renders correctly. I have a restore button that restore the purchase correctly, but it does not dismiss the paywall. The user is often left confused as to whether the restore worked or not. How can I get the paywall to dismiss automatically after a restore? There’s no `dismiss()` method on `RevenueCatUI` either, and I would like to not use `<RevenueCatUI.Paywall />` component as that has several scroll issues when used in a bottom sheet to mimic similar behavior of `RevenueCatUI.presentPaywall()`

Our paywall on iOS works perfectly fine right now. It fetches the products/offerings and displays the paywall UI.However on Android we are only showing the offerings and not the paywall UI. Was curious if anyone knows the solution/problem?We are running RC:react-native-purchases - 9.7.0react-native-purchases-ui - 9.7.0expo: ^54.0.19We are displaying the paywall via: <RevenueCatUI.Paywall>

Hi all, I have a question about RevenueCat-Mixpanel integration. Through this integration, we’re able to get purchase-related events such as rc_initial_purchase in our Mixpanel dashboard. However, all of our sandbox data are also included in these events, making our Mixpanel charts inaccurate for analysis.So I’m wondering if there’s a way to exclude these sandbox events when being sent to 3rd party tools like Mixpanel.Thanks!

Hi all, we’ve integrated Mixpanel, and are sending events such as initial purchase.We also have implemented our own Mixpanel events for each purchase, which means there are two (supposed-to-be) identical events being sent to our Mixpanel when a user makes their purchase, like below:purchase_subscription (our own Mixpanel event, sent via Mixpanel SDK) rc_initial_purchase (event from RevenueCat integration) The problem is, the number of two events never match. Sometimes the number of events from RevenueCat integration is higher, and sometimes not. I do understand that there may be some (slight) discrepancies, but the gap sometimes is as large as 20%. (viewed daily) What could be the cause? We’ve been trying to find if there’s any pattern in the discrepancies, but couldn’t find any.  Thanks in advance! P.S. If this info could help: We’ve counted the numbe

Hey! I just created my app and set up my ‘in-app purchase’ .p8 file and key, but immediately got this error. Any clues on what to do?   

Hello,I have a working subscription system with revenuecat for a jazz education app. I wanted to be able sell individual lessons. I heard from many customer that they would want individual lesson purchases that is unlocked for life. I have 42 lessons in the app now and I plan to add more. It will be around 150-180 lessons total. So, What is the best practice here? Do I need to create 150 SKUs ?I have 6 categories and that number will be 10 categories soon.Every lesson in each category will have the same price. However, I will need to track who bought which lesson? So could I somehow have 10 categorical prices to simplify things down and still track 150 lessons with it? Thanks..

We can honour entitlements that were purchased on other platforms by calling login(appUserId).What if someone purchases a package on ios, then logs out of the app, then creates a new appUserId.Wouldn’t this create a scenario where multiple appUserId’s have an entitlement from a single purchase?

Im extremely stuck on submitting my app to the app store.I tried to submit my app to the app store - but it got rejected based on the paywall screen erroring.Im using a custom screen. I have a few questions.Do I have to submit the app and the subscriptions together?Surely this leads to a catch 22 - where the paywall screen will not ever serve the subscriptions since they are still in review…Ive been waiting for my subscriptions to get reviewed now for like 4 days - I’m wondering if i need to submit the whole APP again for review - to get them to review the whole app again and therefore review the subscriptions (?).If I use my prod revenue cat key - i get a similar error appearing…@app/mobile:dev:  WARN  [RevenueCat] ⚠️ RevenueCat SDK is config

Using variables such as {{ product.relative_discount }} or {{ product.price_per_period }} seems to work in the paywall editor, however it does not work in development builds. I have attached two screenshots, one of the editor and one of my running dev build. As you can see, the percentage is missing from the dev build, as well as the price period. What am I doing wrong?  

Hey everyone,At our company, we currently ingest RevenueCat data through a webhook setup that sends events into our internal pipeline. We’re now considering whether to keep this approach or switch to pulling data directly into S3 (for example, via the API or an ETL process).I’d love to hear what RevenueCat recommends here — and what other teams have found works best — especially regarding: Data reliability and completeness over time. Ease of scaling and maintaining the integration. What’s the setup you’d suggest or have seen work best for production environments?Thanks in advance for any insights! 

We have a free App on the stores of Apple and Google and sell via IAP subscriptions to use our service using the RevenueCat paywall. This works well for B2C customers and should remain.But B2B customers want to buy license packages of e.g. 50 licenses and assign those to users within their organization. Therefore we need the ability to sell subscription licenses in bulk.The amount of licenses must be flexible to suit customers of different size.Ideally this can be done through our existing WooCommerce shop where customers would select the license amount from a dropdown. These bundles should then also be unlocked/processed via the paywall in RevenueCat to avoid changing our App and to maintain the B2C offer. I did all the work on the WooCommerce side to sell licenses and was able to pull web orders using n8n and make.com. But I struggle to create entitlements in RC using the REST API. According to latest ruling, this process should be allowe

I get this error when trying to create my second targeting rule: 

Hello,I have created a paywall in revenuecat’s designer. I have an issue with scroll and carousels: having a carousel in a scrolling screen prevent user from scrolling vertically (impossible on iOS, extremly hard on Android). I thinks it’s a gesture detection issue, trying to scroll vertically make an horizontal scroll on the carousel instead.If you have any tips ! 

Hello, I'm currently trying to set up my app with Rev Cat and set up the subscription. I'm currently not able to see the subscription when I move over to the official API key from the official app store.  I attached screenshots, and the code that I'm using. In the screenshot, it's showing that developer action is needed because I submitted it, and it didn't show correctly. Which is why when I got my developer's profile to the project, on the comments it said it's fine, and that it still should be visible.  // expo-app/components/Paywall.tsx{loading ? (    // ... loading spinner ...) : !currentOffering || currentOffering.length === 0 ? (    // This is what you see if RevenueCat returns nothing    <View style={{ padding: 20, alignItems: 'center' }}>        <Text style={styles.loadingText}>No subscriptions available.</Text>        <TouchableOpacity onPress={onClose} style={{ marginTop

I choosed the Exit Offer on my main Paywall but it doesn’t appear after click “X” button(Navigate Back action). My packages versions are "react-native-purchases": "^9.6.10","react-native-purchases-ui": "^9.6.12". 

I've asked a question here but it never got answered (probably because the original post got answered and I asked after) so here's a new post to try to get my answer on this topic.  If we want to only override "promo" placement with an experiment, we still have to re-define every other placements in the experiment? Or if we just keep the "All Other Case" to "No Offering" it will fallback on the targeting? Not so long ago we used to have this, which was creating a fallback on targeting-defined placements. Re-defining all of them (not only the tested placements) seems very error-prone and cumbersome.  

RevenueCat’s existing integrations send real-time subscription events out to supported platforms like OneSignal or Customer.io automatically via their integration UI, without needing your own webhook backend. A native Sendbird integration would let you: Sync subscription lifecycle events directly into Sendbird Trigger messaging flows without your own glue code Push events into chat/notification workflows in Sendbird Since it’s not currently listed, it’s not yet supported - so please consider this as a feature request.

Can we change the close button color in Flutter  await RevenueCatUI.presentPaywall(displayCloseButton: true); 

Is it possible to log in users anonymously?Currently we are facing an issue. We user Firebase in our apps and in order to send notifications we need to store push tokens in our database. So, we sign in users anonymously to Firebase, and then we can store this info under their user ID.The problem arises when we then call Revenuecat’s login function. We do this so that if a user contact’s us we can match them between Firebase ID abd Revenuecat.However, the problem arises in that now Revenuecat treats the user as signed in. So, same user trying to access the app on two devices will not be able to do so, as the purchase is constantly transferred from one user to the other.Hence a question - is there a way to provide anonymous alias? So that we can search users by their firebase id, but tell Revenuecat “this one is not signed in, so apply anonymous behavior to purchases transfers”.Alternatively, this could be sorted by allowing us to search customer by

I’ve seen these two threads:  and  And the blog post announcing the availability of paywall support for (non-flutter) web sdk here: https://www.revenuecat.com/blog/company/paywalls-on-the-web/ It would be very helpful to know if you have specific plans to add paywalls for web to the flutter SDK, and if so what the timeline might look like, so I can figure out whether I need to roll my own ahead of time or wait for a supported version.

My paywall has a big gap in the text when displayed on a max device. Is it possible to set the header image to enlarge to take up this space? Screenshots of iPhone 17 vs 17 max below: