Get help with anything related to RevenueCat.
Recently active
The documentation suggests Purchases.configure() is async because of the await in the Configuration docs. However, the React Native TypeScript definition says (args: PurchasesConfiguration) => void, so no promise. Which is it?I am using "react-native-purchases": "^7.1.0".
Our app has multiple types of events (trial, trial converted, trial cancelled, yearly subscription...)We added adjust integration and all the data being sent to adjust are matching all events except one: the trial converted one.we see almost double the numbers on adjust.how can we investigate this?
Our service is an iOS app using RevenueCatSDK. And the iOS app uses our WebApi backend with RevenueCatAPI.The service user can have multiple service Accounts, multiple AppleIDs and multiple Apple Devices. The service want to have following behavior:User has multiple service Accounts, AppleIDs and Apple Devices. service Accounts: (e.g. Account_A, Account_B) AppleIDs: (e.g. AppleID_A, AppleID_B) Apple Devices: (e.g. iPhone_A, iPhone_B) User can change combination of Account, AppleID and iPhone. Account has unique UserID and sets the UserID to AppUserID(RevenueCat). We don't use anonymous AppUserID. Role is managed by our WebApi If a user makes a subscription with the combination (iPhone_A, AppleID_A, Account_A), the user Role is changed and the Role is managed by the our WebApi. Whether the combination is (iPhone_A, AppleID_B, Account_A) or (iPhone_B, AppleID_A, Account_A), Account_A can use our service in a Role managed by our WebApi. Until subscription expiration, AppleID_A can re
It goes something like this:1 - Sign into RC with appID12 - Purchase subscription.3 - Sign out and back in again using appID24 - RC says no subscription active for appID2 and so we present offerings.5 - Purchase fails because (presumably) Play Store thinks we already have an active sub because appID1 bought one using the common PlayStore sign in.I’d like to prohibit sub sharing across different accounts.In order for appID2 to be able to purchase a subscription, another Play Store account needs to be used.What’s the general best practice for dealing with this scenario?Many thanks.
Hello,I intend to have both subscription and consumable products in my app. If you want an example of the kind of setup I want, check Slopes: the app offers subscription (monthly/yearly) + consumables (passes to unlock one day or one week). In Slopes, the user can redeem the pass whenever he wants, but it’s not what I plan: I plan to use the consumable as soon it’s purchased. So if a user purchase a one week pass consumable, I want to unlock the content from the purchase date.How would you setup the same thing using RevenueCat? Do I have to setup my own system to record the purchase date (= activation date in my case) then unlock the content based on this date? Or is it possible to access consumables purchase history in RevenueCat so I can check when a consumable had been purchased and unlock the content afterwards?Thanks,Axel
Hello,is there a way to get a customer (or subscription) by the customer attributes?Thanks in advanceMarius
I'm using the RC's remote paywall feature and my app is being rejected at App Store, because when there is no internet, the Paywall doesn't load (despite showing the no internet connection alert). Has anyone ever had this problem? I would really like to use remote paywall, but it looks like my app will only be approved if I use a hard-coded Paywall in Xcode
Hi all, I could not find this in the docs. I have 2 different paywalls and 2 different offerings. How do I call up a specific paywall within the app vs the other using UKIT or Swift/IOS? Thanks!
sorry and delete only edit posts
On iOS, my paywall works just fine. So that’s proof that my product settings and paywall settings are all setup correctly for App Store. On Android, I followed the documentation and checklist - three times over - to make sure each step is followed to the letter. I have verified my google ↔ RevenueCat server-side connection is setup correctly, by sending test messages successfully from google. My subscription products in Google Play are in active status - which I’ve “imported” into RevenueCat. I have a attached entitlements, and created one offering with packages in RC correctly (both Apple App Store and Google Play Store products in each package - and all that is working correctly in iOS). My app is in “alpha/closed” testing stage (and approved by google) - when I download the app on a real device, and run it, I still get the following error: "Error 23: There is an issue with your configuration. Check the underlying error for more details." In case you are wondering how Google a
Hi, looking for some confirmation on the abilities of RC for our product, and googling this question is quite hard. We want to take Stripe payments in our mobile app, for purchases / subscriptions related to physical goods (which shouldn’t go through Apple / Google’s IAP system). For this, we would love to use RC’s paywalls, experiments and tracking features.React Native SDK would be used. Is this possible, and are there any caveats to be aware of? Thanks community!
Been getting this error after adding the service account credential JSON, I’ve made sure that I followed the documentation: https://www.revenuecat.com/docs/creating-play-service-credentials but haven’t been able to resolve this.
Hello together,What would be your recommendation on managing the following product setup: Many non-consumable products (e.g. books) of thee price classes: low, medium, high?1) Enter each book with price in Google/ Apple and create package in RC from each of the entries?2) Enter each price class in Google / Apple and linkt that to a book specific package in RC?3) Enter each price class in Google / Apple and link that to a book specific offering in RC?4) Other?Is RC actually fit for this purpose? Alternatives?Kind regardsBP
Hi, I’m implementing one-time purchases using RevenueCat.I’ve set up a webhook to receive data when a user successfully completes a purchase. However, for security reasons, I don’t fully trust the data received via the webhook and want to verify the purchase using RevenueCat's REST API (v2).I’ve gone through the documentation but couldn’t find a clear endpoint to validate one-time purchases. Could you help me with the following questions?Which endpoint should I use to validate a one-time purchase? What parameters should I include in the request? For example, should I use id, transaction_id, or app_user_id from the webhook data? Can the /v2/projects/{project_id}/purchases/{purchase_id} endpoint be used for this purpose? If so, what value should be passed as {purchase_id}?
Hello, I have this error from RevenueCat: code: 23, message: There is an issue with your configuration. Check the underlying error for more details. There's a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect (or the StoreKit Configuration file if one is being used). More information: https://rev.cat/why-are-offerings-empty domain: RevenueCat.ErrorCode, userInfo: "readableErrorCode":"CONFIGURATION_ERROR","readable_error_code":"CONFIGURATION_ERROR","source_file":"RevenueCat/OfferingsManager.swift:237","source_function":"createErrorForEmptyResult(_:)","NSLocalizedDescription": There is an issue with your configuration. Check the underlying error for more details. There's a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect (or the StoreKit Configuration file if one is being used). More information: https://rev.cat/why-are-off
Hi there,I’m looking for some clarifications on how to ask the user for consent for the sending consumption data. I was reading this article on sending consumption info to reduce refunds: https://www.revenuecat.com/blog/company/handle-apple-refund-requests-automatically/ And then I saw the paragraph about asking the user for consent with a warning sign:⚠️ Important: Make sure you have customer consent to share consumption data by outlining this in your terms and conditions, as required by Apple. In the article (as quoted above) it says it’s enough to put it into the Terms and Conditions, but the linked Apple article is much more ambiguous about this. Like this part:So the user can opt-out and it should be “affirmative consent”. What’s your experience with this? Is a paragraph in the terms and conditions sufficient? Did Apple Review reject anything?
I've implemented a listener for subscription status changes in my Flutter app like this: void listenToCustomerInfoUpdates(Function(CustomerInfo) listener) { Purchases.addCustomerInfoUpdateListener((customerInfo) { // Called whenever subscription status changes listener(customerInfo); });}I want to confirm: If a user cancels their subscription through the system subscription settings (App Store), will this listener automatically detect the change?My implementation:I've set up the listener in my service layerUsing it with BLoC pattern to update UI stateThe listener is registered when the app initializesIs this the correct approach for handling real-time subscription status updates? Will it catch all subscription state changes including cancellations through the system settings?Thanks in advance for any clarification!
