SDKs

We have the combined issues of 1) purchase requests hanging and 2) PurchaseErrorCode.operationAlreadyInProgress for our flutter app. Haven’t been able to reproduce on our side but have several users recently report this.Example of a recent Android report: https://finch.hellonext.co/b/Bugs/p/can-t-sign-up-for-trial-with-monthly-billing. We always display the error code that is returned (like in the bug report screenshot) but it sounds like some users can have requestToPurchaseProduct effectively hang without an error code returned. Is requestToPurchaseProduct always supposed to throw an error to timeout, or are we expected to handle timing out purchase requests ourselves?After the hanging, users who close the app and retry again end up getting stuck with PurchaseErrorCode.operationAlreadyInProgress. The error

the problem is I get the web hooks on EXPIRATION, PRODUCT_CHANGE and CANCELLATION but I don’t get it on INITIAL_PURCHASE or RENEWAL so we can't update our database what am I missing, I set every thing right, I also set revenueCat web hooks on App Store Connect for Sandbox and production and I even get customer history in overview with sandbox checked  

Hello all,I have setup real time developer notifications for my Android app, everything seems to be working fine and when I click the “Send test notification” in the developer console, the notification is successfully sent and no error is provided, however, all my Android purchases keep getting automatically cancelled 3 days after a successful purchase. My guess is that the purchase is cancelled because they’re not acknowledged by the SDK.I’ve followed the setup steps multiple times and the purchase flow and everything else works as expected, but it is really frustrating to see all my purchases returned because some misconfiguration on either mine or RC’s end that I haven’t been able to pinpoint.I also setup a new Pub/Sub subscription to the topic automatically created by the RevenueCat system and I successfully receive the base64 encoded notification with a payload similar to this one:{"version":"1.0","packageName":"com.my.a

I’m trying to set up our payment at my workplace and I encountered a problem I cannot find others are having.Everything works, in theory and practically which is weird, but I still get warning logs in console when clicking the purchase button in app.So as soon as I click the purchase button I get two warning/error in log:[Purchases] - WARN: 🍎‼️ There is a problem with the SKPaymentTransaction missing a transaction date - this is an issue with the App Store.[Purchases] - WARN: 🍎‼️ There is a problem with the SKPaymentTransaction missing a transaction identifier - this is an issue with the App Store.However, I still get the prompt to purchase and I fill in my sandbox account details and hit buy. Everything is successful. The customer and data shows up on RevenueCat list. However the billing shows up as an error in customer info in RevenueCat in the details of history for customer.I found 

When I tried to restore a lifetime access IAP on iOS with this code it did not detect a purchase. It seems to only work with subscriptions. Am I doing something wrong, or is there a different method to detect if a user has purchased a lifetime access IAP? Tried looking through docs but didn’t come across anything. Thanks for any help in advance.Purchases.shared.restorePurchases { (customerInfo, error) in    //Check customerInfo to see if entitlement is active    attemptingRestorePurchase = true // Bool that starts loading indicator    if customerInfo?.entitlements.all[Constants.entitlementID]?.isActive == true {        paidCustomer = true //Mark user as paid        attemptingRestorePurchase = false //stop loading indicator    } else {        if networkMonitor.isConnected { // Alert toggle - checks internet connection

Hello, I have some issues with the app review.I have tested it using an android and iOS simulators and I can fetch the entitlements without any issue, I can see the description, price etc and the subscription works.However after installing the app through the TestFlight application, when I fetch the entitlements, I only see the price.Any idea why could this happen?Thanks

Revenuecat team: Thank you for providing such a good service.ConditionSDK: react-native-purchases@^4.5.2:   version "4.5.3" Restore setting: Block RestoreSDK login timing: at App initializing and before purchaseRuns restorePurchase internally before makePurchase to check if product is already purchased by different Member. (Shows message to re-login by purchased member)UsecaseiPhone user (App ID = X）log in to app as Member: A=app_user_id. Then purchase Monthly subscription. User log out Member: A. User log in as Member: B. User Try to purchase Monthly subscription (internally runs restore for checking before purchase), “Receipt already in use” error occurs and prevent Member: B from purchasing.  This behavior is as we expected. But after above, When User try to purchase again as Member: B( internally runs restore for checking before purchase), this time

I have the following issue:My app requires being logged in, otherwise I don’t make use of the RevenueCat SDK, meaning that when I init() the Purchases I always provide the userID. When the user logs out, I also call the logOut() method in the SDK.If I make a purchase with account A, then log out, create a new account B and make a new purchase, on iOS at least I get a pop up saying the I am already subscribed and no matter if I press Manage or OK, the SDK will return that I have an active entitlement and make the account B premium.This is really bad, since with one account you could create multiple accounts that automatically will get the premium status.Am I doing something wrong? Is this just happening when I use the simulator with the StoreKit? I don’t want to have this behaviour in production.Thanks!  

Hi, I’ve configured Free Trial offer on both Monthly and Yearly Plans in Google Play Store.The free trial (14 days) shows up in payment sheet incase of Yearly plans, but not incase of Monthly plans.The configuration is exactly the same in both monthly and yearly subscriptions and when I fetch the product info I get the following object - {…,freeTrialPeriod:”P2W”,...} in Logcat. Following the eligibility criteria -   I fetch all entitlements and allPurchasedProductIdentifiers to make sure that user has not subscribed to the plan beforehand  So, I’m not sure why its not reflecting in pay sheet only in case of monthly plans.Any help regarding this topic will be appreciated. 

Goal: I’d set up a monthly/yearly subscription plan for App Store users, and now would like to increase the price for new users. However, I’d like to grandfather the old users’ price (i.e. their subscription prices ideally wouldn’t change).Setup: I originally created 2 new products in Apple/RevenueCat, created a new RevenueCat offering pointing to those products, and then made the new offering the default. Within my app, the new price is as expected! However, if a user goes to their payment settings, they can see ALL of the pricing. I have paying users across all 4 subscription products. Question: As I understand it, if I untick “Cleared for Sale” on the old products, old users’ subscriptions will stop. Is there a way to do this without disrupting the user? Thank you!

Want object structure and demo values for return object of Purchases.getOfferings(). It returns an object  of “current” and “all” keys. And don’t return demo values with which we can test in debug mode.

Hi,I am able to buy some consumable (on iOS Sim & Device) using my Sandbox account. I see : [Purchases] - INFO: 😻💰 Purchased product - 'xxxxxx' 15:33:28 DEBUG Purchase succeeded. Optional({  "bundleId" : "xxx",  "deviceVerification" : "w97BiaZOSrXxTrvrR6wTZuT44AL39rFO+V0gTIoE45eIjLCz6d4KmmemegmqFect",  "deviceVerificationNonce" : "39520f62-1cba-4ef9-a348-6523a7baeb17",  "inAppOwnershipType" : "PURCHASED",  "originalPurchaseDate" : 1655494381866.502,  "originalTransactionId" : "11",  "productId" : "xxxxxx",  "purchaseDate" : 1655494381866.502,  "quantity" : 1,  "signedDate" : 1655494381867.5581,  "transactionId" : "11",  "type" : "Consumable"

Imagine that my app crashes just after a successful payment. I want to know purchase to finish when my app restarts.I don’t see in the docs how to do it using RevenueCat. I was using this code: SwiftyStoreKit.completeTransactions(atomically: true) { purchases in for purchase in purchases { switch purchase.transaction.transactionState { case .purchased, .restored: if purchase.needsFinishTransaction { // Deliver content from server, then: SwiftyStoreKit.finishTransaction(purchase.transaction) } // Unlock content case .failed, .purchasing, .deferred: break // do nothing } }} Thanks

We’ve got an issue where the PurchaserInfo is empty when using same appUserID but different device/platform. We’re using the Legacy (Alias) mode because we want the user to share the entitlements across multiple devices.This scenario is: Android (paying Subscriber) -> iOS (new device)Is what we’re trying to do possible? Is there a reason why the PurchaserInfo would be empty on the iOS device.We checked to see if RC is throwing any errors when restore purchases is pressed, which it isn’t. Obviously, we don’t expect Restore Purchases to actually restore a purchase, but we do expect it to send the entitlements for the appUserID. Is our understanding correct?

I am using the flutter SDK to integrate IAP to my app and i am using the non renewable subscription model. I want to get a unique transaction ID issued by apple to send to my server to store it if the user wants to refund his purchase in the future.

There is another question out there marked as solved (see below) however I believe there is a need to re-open this as per recent changes to Google policy. Google is now requiring apps to allow for cancelling a subscription from within an app. An email was sent to app developers about a policy change: We’re updating our Subscriptions policy to state that users must be able to easily cancel their subscriptions from within the app. You’ll have at least 30 days from the date of this notification to update your app to comply with the following policy changes.As this is not currently possible via RevenuCat it means that apps are in danger of being in violation of Google policies and banned from the Play Store. We urgently need a way to cancel a subscription so that it does not renew but without refunding for purchases already made. 

Through the Google Play API you can revoke, refund, and cancel a subscription. Through the RevenueCat API you can revoke and refund, not cancel. Is there going to be added support for canceling a subscription?

We have native iOS app with revenue Cat, its work perfect. Now we rewrite our app with Flutter framework. In app written with flutter we use revenueCat too and it works perfect on Android(release) and iOS(test flight). Imagine user bought subscription in native iOS app, then we realese new version app written with flutter, user install it and want to restore subscription. Now question will the subscription been restored ?

I have been looking in the documentation but didn’t see anything related to flutter for redeeming a coded!I have implemented the auto-renewable subscription with 1 month free trial in my Flutter app and have tested using Sandbox on iOS and works fine. How can I redeem an offer code using Flutter?

Hello, I am implementing a paywall and I want to keep the products displayed as dynamic as possible. I want to display the title and description of the product on iOS, but it is returning an empty string for both properties:  I am using StoreKit with XCode to test properly on my iOS simulator using React Native: This is my App Store Connect configuration (it is in Ready to Submit state): It is working properly for Android (except it is not returning the description, maybe to due to the fact that there is no description p

Hello, We’re using the React Native SDK for an Android and iOS app. We have received some reports in social media from users complaining that they have been charged immediately after purchase despite the product having a 7 day free trial. We don’t have any user Ids to check in the RevenueCat dashboard yet but we’d like to understand better how free trial eligibility works in the React Native SDK. Does checkTrialOrIntroductoryPriceEligibility work on Android with the React Native SDK? I’ve seen another post from an Android native user that a different mechanism is necessary If the method returns INTRO_ELIGIBILITY_STATUS_UNKNOWN, is it safe to assume that the user is not eligible?   Are false positives (is not eligible, unknown is returned) or false negatives (is eligible, unknown is returned) more likely? If a user has already consumed a free trial and they attempt to purchase a free trial product, they will be

Hi,Before integration with RC, we had only non-consumable IAPs, now we want to release auto-renewable subscriptions with RC SDK.We added non-consumable IAPs to the entitlement with subscriptions. That seems to unlock a feature under that entitlement for customers with lifetime access.So what is the benefit of performing `syncPurchases()` for users with lifetime access since they get the access the entitlement already?

Hi there,is there a way to check if a user has currently subscribed to a specific package? The use case is that I want to have a monthly and a yearly subscription for pro access. If a user has subscribed to one of both, I want to mark it accordingly in the UI and disable the buy button.I can’t just check if the pro-access-entitlement is active because both the monthly and the annual subscription refer to the same entitlement. Any ideas?Best, Tobias

Hi there, I have a “Lifetime Pro” inapp product. After I refunded this through Google Play it is still fetched as a bought product by Revenuecat. How can I securely verify that my non-subscription product is not refunded?This function is essential for me as it would be too easy for users just to buy the lifetime product, directly refund it and enjoy the lifetime pro for free. Appreciate any help.

On occasion we get an error from the update subscriber attributes API. We are not sure what is causing the error since we are following the documentation. Here is the error response: {‘code’: 7259, ‘message’:‘Subscription not found for subscriber’}