Get Help

Hi, Any update on changing the timestamps you’re sending to Customer.io via the direct integration from ISO to Epoch? I asked in this post before: Customer.io doesn’t run on ISO, they use Epoch. As it stands, this integration isn’t very useful (the most important piece of data that I need in Customerio is the user’s expiration date!).

https://api.revenuecat.com/v2/projects/${project.id}/charts/actives?realtime=false&start_date=${dateStr}&end_date=${dateStr}I want to get the result for a single specific app from the link above.How do I do that?

I have read many posts about this but still don't know what's going on. I can't figure out why I can show my subscriptions but not the non-consumable product. Starting from Google Play, these are my subscriptions (again, no problem with them):The no-consumable product:(no country restrictions, set price...) And now comes RC. This is my product catalog:

Hi,I’m using the RevenueCat Web Paywall Editor and would like to keep using it (no custom paywall in code).With Android 16, forcing portrait is no longer allowed → I now need proper landscape support.Current challenges: Paywall is optimized for portrait, but breaks in landscape (height constraints) Editor only provides FIT / FILL / FIXED — no responsive rules No way to: show/hide elements based on orientation adjust layout/spacing per orientation Tried switching images from FILL → FIT, but still not getting good results Questions: What are the best practices to design a paywall that works well in both portrait & landscape using the Web Editor? Is the expected approach: one responsive layout?

Hello,I am encountering the well-known readable_error_code: CONFIGURATION_ERROR (code: 23) while implementing subscriptions on iOS.I have already performed several checks to identify the cause of the issue, and so far all configurations appear to be correct: All contracts in App Store Connect have been properly signed. The product identifiers match exactly between App Store Connect and RevenueCat. All required metadata and configurations have been completed. The backend integration has been finalized and appears to be working as expected. We also performed tests on physical devices (iPad and iPhone) running iOS 26.2.1, and the error still occurs when attempting to fetch the products.The only potential issue I can identify is the subscription status. The products are currently liste

Hey, I’m in the process of selling my app to someone. It’s on iOS + Web. I use RevenueCat for both.  As far as I’m aware, when I transfer the app on App Store Connect, all the secrets/keys remain the same? How does it work on RevenueCat web billing? I can’t transfer my Stripe account as I’ve got other apps running through there, but I also don’t want any disruption to existing subscribers.  What would be the best way going about moving web purchases over to a new Stripe Account? Thanks!

My custom paywall was showing for a couple of days in TestFlight, but for some reason its reverted to the Apple default paywall...which is causing my app to be rejected. HELP!!

We're using RC Billing (Web Billing) with the RevenueCat JS SDK. During the purchase flow, we pass the customer's email via the `customerEmail` parameter in `Purchases.purchase()`.Due to a bug on our side, some subscribers had an incorrect email passed as `customerEmail` at checkout time. We've since fixed the bug, but for the affected subscribers, all lifecycle emails (subscription confirmation, renewal reminders, billing issue notices, etc.) are still being sent to the old incorrect email.What we've already tried:1. Updated the `$email` subscriber attribute in the RevenueCat dashboard — lifecycle emails still go to the old address.2. Updated the email on the corresponding Stripe Customer — lifecycle emails still go to the old address.It appears that RC Billing stores the checkout email internally, separate from both the `$email` subscriber attribute and the Stripe Customer email, and uses that internal email for lifecycle emails.

I have a scenario where I would like to have one Offering and Paywall general design, but be able to customize the text and header imagery depending on some user chosen option or paywall trigger.Examples:The user has chosen a preference (favorite type of sport). I would like to display an image related to that specific sport for him. The Paywall trigger is specific to a feature. User clicks a locked feature (ie. offline-mode, dark-mode, etc). I would like to display a specific image and text header for each of these.In this example, the header differs for those cases, but the rest of the Paywall visual and structure is the same. Offering/Package choices, Feature list, boutons in the footer, etc.All these options also share the same offering for example.In my understanding, right now, with the 1:1 Offering/Paywall model, it seems that I would need to have a dozen different Offerings and Paywalls for this. Meaning t

I have been using revenue cat for over 6 months now and I just started my first price point experiment yesterday. I went to open the paywall today and my app froze. It also froze in my development build and I was able to find the following log. DEBUG [RevenueCat] ℹ️ API request failed: GET '/v1/subscribers/user_1234/health_report' (500): There was an unknown backend error. Internal server error.Request-ID: <DEPRECATED>; Amzn-Trace-ID: <DEPRECATED> ERROR [RevenueCat] 😿‼️ There was an unknown backend error. Internal server error.Code: construct.js 2 | var setPrototypeOf = require("./setPrototypeOf.js"); 3 | function _construct(t, e, r) {> 4 | if (isNativeReflectConstruct()) return Reflect.construct.apply(null, arguments); | ^ 5 | var o = [null]; 6 | o.push.apply(o, e); 7 | var p = new (t.

Hi everyone, We’ve been stuck on this issue for a while and would really appreciate some guidance. We are integrating RevenueCat in a React Native / Expo app and using our own custom paywall UI (we are not using RevenueCat Paywalls). Our app is already in App Store Connect → Ready to Submit, and our subscriptions are configured, but the SDK is still returning empty offerings. Setup Products in App Store Connect babysoothe_monthly (auto-renewable) babysoothe_yearly (auto-renewable)  Both products currently show:Status: Ready to SubmitThey also have: localization pricing screenshot for review subscription group configured  

Credentials need attention Valid key format The key is not valid or is not compatible with the Bundle ID of your app.  

Looking into the RC Privacy Policy, I found the following snippet:If you are using our products or services as a developer, the following information regarding your end users may be received and processed by us: “End User Technical Information”: This refers to technical information related to an end user’s mobile device or computer, such as: device type, operating system,  “End User Transaction Information”: This refers to transaction information related to an end user’s activities with respect to your app or other digital product, and may include: Last seen time that the end user used your app or digital product; Apple receipt file; and Google purchase token, “Optional End User Information”: This refers to information that we may receive if you select or enable this option in our products, which

We just launched an app with IOS and REvenue Cat. We are doing subscriptions. No in app, just subscriptions. we are getting prodcut details via api, so i am sure that matches up.  the business agreements, etc are all active the subscriptions are active.  the app is ready for distribution.  We have checked API and seems to match up.  Product ID matches. Any other bright ideas out there? I feel like we have tried everything. 

I beleive I have everything configured properly but testflight shows this when paywall is prompted to show

I've been experimenting with the Charts API v2 to build an automated weekly operator brief, and I found something interesting.When you pull revenue and MRR chart data for the same time window, they can tell completely different stories. In one project I analyzed, revenue was up ~14.7% while MRR was down ~3.0% in the same comparison window. If you only checked one chart, you'd either celebrate or worry — but the real signal is in the contradiction between them.The pattern: annual prepayments can inflate revenue while the monthly recurring base quietly declines. I call this a "sugar rush" — the topline looks healthy but the recurring foundation isn't compounding.I built a small open-source tool that automates this comparison across multiple chart endpoints (revenue, MRR, churn, trial conversion, new customers, trials) and flags when metrics move in contradicting directions:

Hi RevenueCat team 👋Love the Paywall Builder — it covers a lot of ground without needing a developer. I wanted to submit a feature request for two animation/visual effect capabilities that I think would have a meaningful impact on conversion:**1. Pulse animation on the CTA button**A subtle, looping pulse effect on the primary purchase button (e.g. a gentle scale or glow pulse) is a well-established pattern for drawing attention to the key action on a paywall. Right now there's no way to add motion to the button component without going fully custom.**2. Shimmer / glow effect on  badges**A glimmer or shimmer animation on a badge is a lightweight way to signal which plan to pick and nudge users toward the higher-value option. Again, this isn't currently achievable within the builder.Both effects are small but proven conversion levers — especially on paywalls where users may be hesitating between plans.

I am noticing a difference in key performance metrics when comparing the RevenueCat Web Dashboard (Overview) to the RC’s iOS app’s dashboard. Which one is correct?

The new customer metrics don't match reality.Hello,we recently switched to RevenueCat. After the switch, we started seeing different data.  As a mobile app, we usually pay close attention to both the number of downloads and the number of users, meaning the users who are active within the app.  However, there is a discrepancy between the new customer metric in RevenueCat and the new customer metrics in our own main dashboard.When I read the explanations, phrases like “active” made me think, “It must be counting them as new users because it can't track those who registered earlier.”Could this be the case?Can a user who registered before switching to RevenueCat be recognized as a new user when they log in for the first time after switching to RevenueCat?Or what could the issue be?

I deleted a development project. it did not seem to work so I deleted it again. after an hour I noticed that I deleted a PRODUCTION Project. some huge bug that I discovered and I cant seem to find a solution to restore it. I need support ASAP I cant wait 2 days for a ticket answer I get a bunch of downloads and this will result in revenue loss and 100% bad ratings since its a hard paywall app!

Hello everyone,I am a non-technical founder and I have a question regarding the integration between RevenueCat and AppsFlyer.In my RevenueCat dashboard, when I check a specific Customer profile, I noticed that the AppsFlyer ID is already populated in the attributes. Since I am not the developer, I am not sure how this ID was collected, but it is there.My questions are: With this AppsFlyer ID available in RevenueCat, is it possible to look up this exact user on the AppsFlyer dashboard to see their original traffic source (e.g., which specific ad campaign or media source they came from)? Where exactly in the AppsFlyer interface (which report or view) should I paste this ID to find the user's attribution data? I've checked the "Activity View" but couldn't find a direct search bar for IDs. Does the presence of this ID in RevenueCat mean the SDK integration is already worki

Environment:SDK: react-native-purchases ^9.8.0 Platform: iOS (Expo SDK 54, React Native 0.81.5) Testing on: TestFlight (physical iPhone + iPad) Bundle ID: com.withim.app API key prefix: appl_Products:com.withim.app.grace_monthly1 (Auto-Renewable, 1 month, 7-day free trial) com.withim.app.grace_annual1 (Auto-Renewable, 1 year, 7-day free trial) com.withim.app.grace_lifetime1 (Non-Consumable) All 3 products are "Waiting for Review" in App Store Connect RevenueCat offerings configured: $rc_monthly, $rc_annual, $rc_lifetimeProblem: When calling purchasePackage(), it immediately throws error code 16 (UNKNOWN_BACKEND_ERROR) with no readableErrorCode or underly

I have added localization through RevenueCat which has updated the text content. I would like to change the main image for each language to help improve conversions by country. Is it possible to “localize” the image in addition to the text copy? I’ve been seeing more requests for this (> 9 months ago)Thanks!

Hi RevenueCat team, I’d like to request a new built-in event (similar to Superwall’s new “Trial Qualified”). The goal is to send a signal to MMPs when, after a short qualification window (e.g., 30 minutes post trial start), a user has either a subscription or an active trial, indicating higher intent/quality than a raw trial start (which often gets cancelled within minutes).Proposed definition:Event name: Qualified Initial Conversion or Qualified Conversion Trigger: 30 minutes after Initial Purchase or Trial Started, if the trial is still active and the user hasn’t opted out/cancelled. Suppression: Do not fire if the user cancels or refunds before the 30-minute mark.   Why this is useful:Many MMPs and growth teams use early qualification events to improve campaign optimization signals, reduce noise from very short-lived trials, and better predict conver

All subscription prices are correctly configured in App Store Connect for all countries and regions. We are currently testing on devices configured for India, where the device region, App Store region, and Apple ID are all set to India.However, during testing in TestFlight, we are seeing inconsistent currency behavior: In our custom paywall UI / RevenueCat paywall, the prices returned from RevenueCat offerings appear in USD ($). When the Apple in-app purchase sheet opens, the price is displayed correctly in INR (₹). Current flow: Paywall (RevenueCat offerings): $ USD Apple Purchase Sheet: ₹ INR (correct) This creates a confusing experience because users initially see USD on the paywall, but the actual purchase sheet shows INR.