Get help with anything related to RevenueCat.
Recently active
Hi,We’re developing an app for iOS and Android with React Native. We want to use RevenueCat as payment provider. Our test with Android works fine. But on iOS an error occurred:Error 23 on iOSWe understand that something in our configuration is causing an issue. But we can’t get the error handling correctly on React Native. We looked at:https://www.revenuecat.com/docs/test-and-launch/errorshttps://www.revenuecat.com/docs/test-and-launch/debuggingBut both of these pages doesn’t show React Native examples.Can someone show us an example of error handling (or Debug Menu) on React Native?Thank you.
When I choose Template 7 and add packaging with the 'Custom Settings per Package' option, I fill in all the fields and press the 'Create' button, but it shows a warning: 'There are validation errors that need to be fixed before submitting.' A red highlight appears on the packaging section, but no specific error is shown.
We are considering using Revenuecat for cross-platform support, but our service, is designed so that the same user can have multiple accounts, and the system does not keep track of which users have which accounts. We are told that cross-platform support requires the use of a custom App User ID to track users across platforms, but if our app's user_id is set to a custom App User ID, they will be treated as different users, and we will not be able to track users if the platform changes. How can we achieve cross-platform support while preventing duplicate purchases of the same subscription plan when the same user currently has multiple accounts? Would we need to build a separate system to have users decide on a parent user_id and integrate them even if they have multiple accounts, so that Revenuecat sees a one-to-one relationship?
Can anyone point us to recommended best practices for regional availability? Our app is in English, so should we just release it to US & Canada, or better to have it available in all regions? What are the considerations there? Like should you only expand to other regions once you’re ready to offer i18n there, have consulted an accountant on any unique financial / tax practices, or does the Apple App Store handle most of that? Thanks!
if (Platform.isAndroid) { print('android haui'); kProductIds = { googleGoldSubscription, googlePlatinumSubscription }; Purchases.setup(googleApiKey);} else { kProductIds = { appleGoldSubscription, applePlatinumSubscription }; Purchases.setup(appleApiKey);}List<StoreProduct> storeProducts = await Purchases.getProducts( kProductIds.toList());if (storeProducts.isNotEmpty) { setState(() { for (var product in storeProducts) { subscriptionPrices[product.title] = SubscriptionInfo( price: product.price, currencyCode: product.currencyCode, ); } }); String jsonString = jsonEncode(subscriptionPrices.map((key, value) => MapEntry(key, value.toJson()))); await prefs.setString('subscriptionPrices', jsonString);} else { if (kDebugMode) { print('No products found.'); }}i have verified the api keys and the product identifiers they are matchingit works fine for ios but when i run it on android it return“No products found.”any idea why
Cannot generate integrate In-App Purchase Key - I followed all the steps up to the part of integrating the subscription.p8 into the app. After credential validation, a 'fail to fetch' error occurs when I try to save the change.Help?!
Hi guys, maybe I missed something - but I want to clarify this question, does Apple support - Revenue Cat or other services for mobile app(subscription) for Dubai/Ireland? From Apple support I got an answer: Apple Developer Program Support doesn't support third-party development tools. You can also refer to the link below regarding Apple Pay guidelines for the web. But I see on the website that there is support, and a bit confused whether it makes sense to connect this service or not?
When we created our plans, wrong offer (trial period) was added to 1 of the plans on google play store. Accidentally we used 7 months instead of 7 weeks. Trial length was changed to the correct one already.Is there any way to change trial length for existing users? Or maybe some other suggestion what can be done to not allow users to use app for free for 7 months?
My application doesn't need user to create account or login. When the user open the app, they need to subscribe to one of the plan to use the app. I am having trouble submitting the app for Google review since they need me to give them access to the app.Is there anyone familiar with this situation and does revenuecat has any function for this case?
We need to add some metadata (key-values) to user’s payments. As an example, we’d like to send workspaceId and other key-value parameters along with a payment that user is creating.I understand that there is a Subscriber attributes which offers capturing custom metadata on the user object, however what we need is to attach metadata to individual payments and not users.Anyway to acheive this functionality with RevenueCat APIs?
I am using RevenueCat for in-app purchases in my Ionic Capacitor React app. I have a question regarding the scenario when a user purchases or subscribes to a plan. If the payment enters a pending state, how can I check whether the payment was eventually successful or failed?And also how i am check if the user are not cancel their subscription after plan purchase.
Hi,I would like to implement a 24 hour “full access/no ads” acess to my App. It should be a one time purchase for the user and automatically expires after 24 hours. I see only the possibility to implement this with consumables.How I would realise it:I would create an own Entitlement for those consumables My app would check all transactions for this Entitlement and consider the entitlement as active if one of the purchases has been done max 24 hours agoCaveats I see:Revenue cat would consume the product directly after purchase. And then the entitlement stays active forever. Not a problem. But not really beautifulWhat do you think of this idea? Are there more caveats or problems you see? A better idea?
Hey everyone!I wanted to share an issue I’m experiencing with RevenueCat in my app, which is currently in closed testing. Yesterday, I made two purchases using a real credit card to check how things work in production mode. Up until now, I had only tested with Google Play’s test cards, and everything worked perfectly in sandbox mode.The issue is that while the payments were processed correctly (each purchase was under 1 USD), when I checked the "Overview" section in RevenueCat, it recorded a total of 30 USD, which doesn’t make sense. Both transactions are listed as if they were 14.99 USD each.This seems strange since everything worked as expected in sandbox mode, and the amounts were recorded correctly. Has anyone experienced something similar or have any idea why this might be happening?Any help or suggestions would be greatly appreciated!I’m attaching some screenshots to provide more evidence of what I’m describing.This is one of the transactions, and the amount is 0.53This is what t
Error 429 is:{ "code": 7638, "message": "There is another request in flight trying to perform the same action."}Error 529 is:{ "code": 7746, "message": "This fetch token is currently being ingested. Please retry the request again to ensure any changes since the initial request are ingested."}This can happen if we do multiple `POST /receipts` for the same user.Do they have a different meaning? Is there a nuance in how we should handle these?
Because of the account number, I now have to re-register a google play account.Therefore, it involves transferring the application of the old account to the new account.My app offers subscription items as well as one-time permanent buy-out items.I want to know what I need to do before and after migrating my application. I need to ensure that users who have purchased perpetual goods are not affected and subscriptions are not affected before and after migrating my application.
I have a question.I'm thinking of leaving the in-app purchase subscriptions for my iOS and Android apps to Revenuecat, storing the data received from Revenuecat's Webhooks on my own server, and using that data to control the provision and suspension of paid features in my app using my own app API. In that case, I have two questions.1. Webhooks are asynchronous, so what should I do if I need to take delays or non-delivery into account? I'd like to know if there is a Revenuecat function that can take that into account.2. Is this design correct in the first place? The purpose of introducing Revenuecat is to reduce the cost of implementing in-app purchase subscriptions in-house in accordance with the specifications of Apple and Google's platforms.
