Recently active topics

Hey Everyone, I have a customer that not exist on my backend at all, does not exist on the dashboard at all (neither production or sandbox) but he is still able to login into my paid app… Can someone please tell me what on earth is going on? Any help would be super appreciated. Customer ID: 7f62a3e2-7f3b-4f9a-9d82-f472584ffbee

Hello - wanted to clarify something I saw discussed in documentation and other questions. It seems that there shouldn’t be a big concern exposing a customer’s user ID to the customer themselves. Is there an issue with other people being able to discover a customer’s ID? For example, we have IDs for our application users. These users may (in the future) interact with each other, for example user A might send a message to user B. Would it be a problem if the IDs that we use to enable identifying the target of the message are the same IDs we use to identify a user to RC? In other words, what would user A be able to do if they knew the customer ID for user B? Or: given our public API key (which is compiled into the app) and a customer’s ID, what information and operations are exposed? It would be great if there was a RC security whitepaper or something like that which went over all the security considerations for implementation somewhere in the doc hub...maybe i’m missing it?

I'm trying to setup retention offers in the Customer Center with this logic:If customer is canceling Active Product X, then offer Product Y Where each product is a different subscription in the App Store with different price points. However, when trying to save this configuration in the Customer Center editor I get the error “Store offer identifier is required for Product Y offer.” I’m not clear on why RC is requiring that I use a promotional offer when all I’m trying to do is offer the customer an entirely different product (subscription) as that is the offer itself. What am I missing here? Is what I’m trying to do bad and not a best practice? My rational is that we already offer Product Y as the back-up offer in our new user onboarding in the Exit Offer, when the user declines our primary product, and so I’d like to do the same here. FWIW, My Product Y, the fallback offer is an annual subscription price at $41.99 that is discounted relative to the default Product X. I understand that

Hello! I have enabled the integration from RC to Meta using the App events api. When in development and testing in sandbox mode, any test purchase shows up instantly in the events feed and later gets forwarded to metas event manager as expected. I have tested 2 real production purchases and it's been almost 24 hrs. RC correctly shows the purchases and customers, but no events in the meta integration as well as meta, both have not received these events. Is this normal or due to volume, or is something set up incorrectly? Thank you.

Hi,I’m experiencing an issue I can’t seem to fix.The text color on my paywall appears differently in the iOS simulator compared to what I see on the RevenueCat dashboard. Some text elements don’t have the same color as configured in the dashboard.I’ve tried switching the device appearance between light and dark mode, but it doesn’t change anything.Has anyone experienced this before or knows what could cause this discrepancy?Environment:Flutter: 3.38.7purchases_flutter: ^9.11.0purchases_ui_flutter: ^9.11.0iOS: 17.2Thanks in advance!  

Hi there. I have a carousel contained within a stack and want to set the Size/Height of the stack to “Fill”, but it’s just showing a “Fill disabled: parents height is set to fit” message. However the parent is the main Paywall component which has no option to change its size? 

Trying to use this endpoint to get the product details, but the trial_length field in the subscription model is not returned (null) even though the product does have a trial period.What’s going on? How do I get this information?

Hello RevenueCat Support Team,We are investigating an attribution issue related to AppsFlyer integration on Android and would appreciate your assistance.ContextIn some cases, purchase events (af_purchase) sent to AppsFlyer via S2S are attributed to an old appsflyer_id, which appears to belong to a previous installation of the app. According to AppsFlyer documentation, a new appsflyer_id should be generated on every fresh install.AppsFlyer support confirmed that these purchase events are received via S2S and advised us to ensure that the latest appsflyer_id is correctly extracted from the AppsFlyer SDK and used in the S2S request.Our implementation We obtain the AppsFlyer ID via:AppsFlyer.getAppsFlyerId() We pass it to RevenueCat after SDK initialization using:purchases.SetAppsflyerID(AppsFlyer.getAppsFlyerId()); RevenueCat then forwards purchase events to AppsFlyer via S2S.  Questions Does RevenueCat update the AppsFlyer ID used for S2S events, or is the first provided value persis

How do I add a Footer to my Paywall. When not using a template I don’t see the option as it’s not included by default and it’s none of the components. 

The Paywall doesn’t show the price (although all other UI are shown correctly) and pressing the purchase button doesn’t have any effect. It shows the price and the button works in Test Store.I have added myself to Google Play Internal Testing and have the correct product ID and base plan Id from Play Console. I have also linked the offer and entitlement correctly. The Google Play API key is also correct in the client code.

So we’ve been running an experiment for about a week now, and discovered a row called “other”. We’re guessing that it is counted as “other” when a user changes the product, say from Monthly subscription to Annual subscription in the device settings or app store. (*not* within the app or RevenueCat paywall) The question is, if our understanding is correct, how does this affect the actual offerings rows? For example, If a user changed from monthly subscription to annual subscription, then is monthly subscription counted -1 and annual subscription counted +1 in the Experiments report table? Or do the numbers not change once they’re counted? Thanks!

Hi team,Is there any way to access the beta paywall analytics?  kind regards,D

Per https://www.revenuecat.com/docs/tools/experiments-v1/creating-offerings-to-test, we created different subscription groups: https://i.imgur.com/9eIRy0Y.jpegWe’re only using “Asr All Acces” pricing, but we want to experiment with the “Asr All Access ($3/mo $30/yr)” and “Asr All Access ($4/mo $40/yr)” subscription group pricing. Apple rejected this 😐 Any suggestions on working around this? Is different subscription groups still the best way to experiment with pricing?See below for Apple’s reason: Guideline 2.1 - Performance - App CompletenessIssue DescriptionIn-app purchase products associated with the app version submitted for review, such as All Access (1 month) ($3), All Access (1 month) ($4), All Access (1 year) ($30), All Access (lifetime) ($50), All Access (1 year) ($40), and All access lifetime ($49.99), could not be found in the submitted binary.Next StepsIf you do not want to make these in-app purchase products available at this time, remove the unused in-app purchase produc

When I export my Figma file to RevenueCat the line spacing is much larger than it is in Figma. I’ve also tried building this natively in RevenueCat, but I don’t see any controls for linespacing. And if I just use two blocks next to each other with no space, the line spacing is still too large. Is there anyway to address this so the linespacing for the paywall in RevenueCat matches the design as created in Figma? 

One of the paywall templates has a toggle to enable a free trial (and is set to off on default). I want to use this but it is not clear how to set it up.My question is do I need to duplicate my products in App Store Connect and have one set with, and one set without a trial period? Or is there an easier way and can RC somehow handle the trial? 

RevenueCat Support Inquiry: Detecting Active Subscriptions on Shared Store account Before PurchaseContextWe have multiple users with separate accounts in our app using the same device and Store account. We're encountering an issue with subscription management when users share the same Store account.Current Setup- Platform: React Native- SDK: react-native-purchases- RevenueCat Setting: "Keep with original App User ID"- Use Case: Scenario where:  - Device has one Store account configured  - Multiple users have separate accounts in our app  - Each user needs their own subscription, but they share the device (and Store account)The ProblemScenario:1. User A logs into our app with credentials: userA@example.com2. We call Purchases.logIn('userA_12345')3. User A purchases Product X (e.g., Monthly Plan) using Store account: M4. User A logs out5. User B logs into our app with different credentials: userB@example.com6. We call Purchases.logIn('userB_67890')7. User B's customerInfo shows no active

How are we supposed to determine which roles are required for which endpoints? The descriptions for configuring roles via the dashboard are vague and do not match the apis whatsoever.

Which most of the apps are showing app icons correctly, but my https://verified.revenuecat.com/vahanpro, doesn’t show app icon at all. I have configured App store and Play Store creds correctly, like other apps, but still it wont come up.Even my verified link(above) doesn’t show App Store link, when App store app is live and working correctly.Please Help!Thanks in advance.

I am currently not receiving any push notifications on my iphone when a user is purchasing something in my app.I confirmed in the IPhone settings as well as within the RevenueCat app that RevenueCat is allowed to send notifications. Any idea why I wouldn’t be notified about a transaction?Thanks!

I am testing a "No-Login" app (Anonymous IDs only) using RevenueCat in the Apple Sandbox environment. My project also uses Firebase and AppsFlyer. I am trying to simulate two completely different users, but RevenueCat is automatically aliasing them into a single Customer Profile.The Workflow I Followed:User A: Installed the app → Generated $RCAnonymousID_1 → Purchased Weekly Plan using Sandbox Account A.Cleanup: Uninstalled the app from the device.Switch: Signed out of Sandbox Account A in developer Settings and signed into Sandbox Account B.User B: Freshly installed the app → Generated $RCAnonymousID_2 → Purchased Monthly Plan using Sandbox Account B. The Issue: Instead of creating a second Customer Profile for $RCAnonymousID_2, RevenueCat added $RCAnonymousID_2 as an alias to the first profile.Integrations in Use: Firebase: I use the Firebase integration. (Are Firebase Instance IDs or UIDs being used by RevenueCat to link these sessions?) AppsFlyer: I have the AppsFlyer integration

Discovering the sdk is challenging when it’s not clear if test case is failing because of developer errors or because some functionality is not supported in the Test Store.I’ve found this information is really scattered on a case by case basis. IS there anywhere where we can see what functionality should or shouldn’t work in the Test Store?This page exists - https://www.revenuecat.com/docs/test-and-launch/sandboxHowever it lacks important details - for example, that introductory offers cant be tested in the Test Store. 

Hi! I am using an app that has 2 parts: a web part and a mobile part (for Android and iOS). Both are generated using the same codebase with Quasar, which in turn uses Capacitor to generate the mobile apps.To allow users subscribe on the mobile part, I use the Capacitor SDK. I want users to be able to see their customer information (current plan, renewal dates...) in the app, be it the mobile or web version.Obtaining this information on the mobile version is easy using the Capacitor SDK. However, I’m not sure about the recommended way to obtain this info on the web part. My first idea was to use the Web SDK. However, there is no way to get a “web” API key, aside from setting up the RC Billing with Stripe, which I don’t intend to use. So I plan to use the Android key.Here are my questions:Is it OK to use public API key for Android store, as in theory the customer info is shared amongst every platform? Is it the idiomatic way to use the web SDK as I plan to or is there some caveat that I

I have an app that uses one-off lifetime purchases instead of subscriptions. The overview dashboard seems to be set up with subscription data in mind. Is there any way I can make it show one-off purchases and other data related to that?

Hello,I’m testing RevenueCat exit paywalls using the Expo + React Native setup and running into an issue where the exit offer paywall never appears after closing the initial paywall.Environment: react-native: 0.81.5 expo: ~54.0.30 react-native-purchases: ^9.7.5 react-native-purchases-ui: ^9.7.5 Setup details: Using the RevenueCat Paywalls UI Calling presentPaywall() from react-native-purchases-ui Testing in dev environment Using default offering Both: Default paywall Exit offer paywall are created and published Expected behavior: presentPaywall() shows the default paywall User closes it Exit offer paywall should automatically appear Actual behavior: Default paywall shows correctly User closes it Nothing happens — exit offer is never displayed No errors are logged, and the close action completes silently.How I’m presenting the paywall:import { presentPaywall } from "react-native-purchases-ui";await presentPaywall();Questions: Is there any additional confi

Hi,is it possible to defer the enrollment to an experiment to a later point of time?I’m using the React-Native SDK. We set up our first experiment a couple of days ago and had a look at the numbers so far. RC experiment stats tell us there were 860 (A: 430 / B: 430) customers so far getting enrolled to our experiment. Our analytics tool however tracks the paywall visit. There only ~300 users made it till the paywall. After a short chat with AI I found out that RC enrolls the user to an experiment variant once the `getOfferings()` has been called. We do call this function, but only in the component which displays the paywall. In RevenueCat on our customers I can see that the customers get enrolled immediately at the same point of time once they were ”first seen using the app”. We initialise the SDK with `Purchases.configure()` directly after the app starts. Between the initialisation and the `getOfferings()` call we only fetch the customer info using `Purchases.getCustomerInfo()` to che