Get help with anything related to RevenueCat.
Recently active
I am integrating RevenueCat into both my iOS and Android applications, and I've encountered an issue with how purchases are assigned to customer IDs across different logins: On iOS: When I log in with Account A, set the customer ID to A (with revenuecat’s login), and make a purchase (not subscription), the purchase is correctly associated with customer ID A in the RevenueCat dashboard. However, when I log out and log in with Account B (in my app), set the customer ID to B (with revenuecat’s login), and make another purchase, the new purchase still gets associated with customer ID A instead of B. On Android: After logging out of Account A and logging in with Account B, the new purchase correctly associates with customer ID B as expected. I've already set the “Restore Purchases Behavior” in RevenueCat to “Leave purchases on the original App User ID”.Expected Behavior: My expectation is that purchases made by customer A should only be associated with customer ID A, and purchases by cust
Hello, It’s unclear from your documentation what the recommended approach is when a company has two subscription levels (e.g. Basic and Pro). The Entitlements documentation clearly shows two separate subscription levels of “gold” and “platinum” in the images (below), but then the Offerings documentation only really explains what to do if you have a single subscription level (and then you choose the Monthly, Annual, etc identifiers). The recommendations on the forums seems to go from “use separate offerings” to “use a custom identifier”. Based on the example image you have on the entitlements documentation below, I’m assuming you’d recommend keeping both tiers in a single offering, but using customer identifiers instead of the default ones (e.g. gold_monthly, gold_annual, platinum_life, etc).I’d strongly encourage you to add this 2-tier setup to your Offerings documentation, since it’s a very common scenario, and it was really unclear to me what the best approach was. Thank you!
I keep getting rejected in the app store for the same thing - a black screen on load. I’m unable to reproduce the error on my end no matter what I do, whether in the simulator or on a real device, new install or whatever. All the review team give me is a screenshot of a black screen and tell me that’s what they get on launch. I can’t fix it because I can’t reproduce it, all I can do is add a time out on the revenue cat loading so it still gets past that point.I get barely any information out of them as you can image, so I have no further specifics and normally they approve it after the second or third time anyway because it probably manages to load or something. But every time I add a new update half the time they reject it again for this same black screen issue..There’s literally zero problems with the app, the subscriptions or how they are set up - everything works perfectly. Why do they have a problem with revenuecat loading in their review environment?
We have subscriptions setup in our app however our client wants to see which users from our database are subscribed. Is there a way to pass in an email so that we can query the revenuecat API to get a list of subscribed users and email, or to see on the customers dashboard the emails of those who are subscribed? Any advice will be appreciated. :)
Hello RevenueCat Support,I’m currently running an experiment where new users are enrolled into a test offering, which provides a specific offer (e.g., Offering B). However, I’ve encountered an issue with returning users who reinstall the app:When a user who previously used the app and uninstalled it re-downloads, they are treated as a new user and enrolled into the test offering as expected. Upon purchasing within this test offering, their purchase history associates with their old user ID, causing them to revert to the default offering rather than retaining the test offering they were enrolled in.Could you advise on the best approach to avoid this issue so that users in this situation continue to receive the test offering (e.g., Offering B) even after restoring their previous purchases? I’d like to ensure experiment consistency and prevent unexpected default offering switches for returning users.Thank you for your guidance!
Hi everyone, I’m having a problem with RevenueCat on my application, it’s giving me this error: And on my Application it works in the Xcode environment how can I solve this problem thank you! :
Hi,In my Flutter app I am using ‘purchases_flutter’ (6.2.0) for IAP and everything is working fine with Google or Apple stores. However Amazon IAP is not working - getting following error when call ‘offerings = await Purchases.getOfferings();’:‘Timeout error trying to get Amazon user data’It seems that error returned from server side, any chance to clarify what can cause this error? I reviewed all configuration on both, RevenueCat and Amazon, everything seems according to docs.
I've set a 30-day trial for the annual plan and a 7-day trial for the monthly plan in Apple Store Connect. However, the paywall is not displaying the correct trial periods. it shows 7 days for annual and 14 days for monthly, How can I resolve this issue?
Hello,Whenever I submit a build, the Google Play Store (and possibly the App Store) automatically runs a series of tests they’ve created. If I submit multiple builds in a day, the number of test interactions can exceed the number of actual users who downloaded the app that day. I don’t have a login page, everybody can use my app anonymously.Is there any way to exclude these test users from the RevenueCat dashboard? They significantly skew the free trial start statistics.
Hello, I have detected what appears to be fraudulent activity. In October, one of our apps (older, unmaintained) reported unusually high revenue (~4x). I found the anomaly in Mixpanel: 49 in-app purchases where made from Tokyo between October 4 - 13th. Each of these users literally opened the app, started a 7-day free trial, and never returned. In every single case. Strangely, most of these trial converted, resulting ~4x the normal revenue. My app did not experience any boost in ratings or rank (49 downloads wouldn’t really move the needle here). But it did see a steep rise in revenue. As far as I’m aware, this “IAP attack” hasn’t occurred in any other app we operate, nor is there any impact on private API/backend resources. QuestionWhat kind of attack is this? Should we report it to Apple or might that backfire into a suspension? Would greatly appreciate any insight on this.
Hi,trying to make use of RevenueCat but I won’t get it to work on Android but only iOS.I am getting when trying to purchase a product on a simulator and on my Android device with:try { await Purchases.purchaseProduct('test_4weeks_4_extend'); } catch (e) { print(e); }D/[Purchases] - DEBUG(11123): ℹ️ Requesting products from the store with identifiers: test_4weeks_4_extendD/[Purchases] - DEBUG(11123): ℹ️ Products request finished for test_4weeks_4_extendI/flutter (11123): PlatformException(5, The product is not available for purchase., {code: 5, message: The product is not available for purchase., readableErrorCode: ProductNotAvailableForPurchaseError, readable_error_code: ProductNotAvailableForPurchaseError, underlyingErrorMessage: Couldn't find product.}, null)I have followed the complete setup and created the keys and they are successfully on the platform and also connection to Google is working for Developer Connection.The identifiers are matching the same on P
Hello! I am architecting the backend for a mobile application and despite reading through a lot of documentation posts, I feel I’m going in circles trying to grasp some subtle points and would love to get some answers before committing a lot of development. So I understand the basics of user IDs and anonymous user ids. Our app will ONLY allow users to login (and get an explicit User ID recorded in our database) AFTER a purchase.No problem: users get an anonymous ID, they sign in and we assign them a new, unique App User ID, which we record, and use login() to associate with their RC account. The question happens when the same user logs into a fresh device (or reinstalls). They get a new anonymous ID upon starting up, but then what happens when they “Restore purchases”?My hope is that we would be able to get access to the previously assigned App User ID. However, the documentation for Restoring Purchases mentions:If an anonymous ID restores and the owner of the receipt is an identified
I was thinking about uploading my React-Native Android App to Huawei AppGallery.I use IAP using RevenueCart with iOS and Google and was wondering, whether Huawei support is already available / planned / not possible.Thanks in advance!
Hi folks,I have few concerns regarding upgrade/downgrade subscription in android. Before coming onto the questions i want to tell the subscription scenario we are using in our app.BasicPackage:Monthly YearlyAdvanvePackage:Monthly YearlyQuestions:What upgrade/downgrade refers to means is it refer to duration i.e monthly, yearly etc or ammount of package? We have to handle all the posssible scenarios for upgrading and downgrading seperately based on current subscription and manually by passing oldProductID?? The doc says we have to pass oldProductId what was it meant? basePlanId(yearly_advance_Package) or subscriptionId(advancePackage) for productIdentifier(advancePackage:yearly_advance_Package) while i think productIdentifier only use for revenue cat. If IOS subscribed user login into to Android what should i do?? instead of allowing them to manage in our app isn’t it better to route it to managementUrl?? Because if he buys then there will be two subscription for same user and vice ver
