Get help with your SDK implementation.
Recently active
I migrated my app to RC, however my previous users are having the sync problem.Previously, I was not using a back-end for the subscriptions, so I was using the client-side receipt validation on iOS (React Native IAP package).I am trying to sync my previous users, but a little bit confused about the steps;if (isSubscribedInOldSystem && !isSubscribedInRevenueCat) {Purchases.syncPurchases();} 1 - What should I provide to the syncPurchases() function?2 - If I need to provide the receipt, should I provide full receipt? or just the receipt body? I mean, I was using this validation method;const receiptBody = { 'receipt-data': receipt, // Should I provide this to RC? password: 'PASSWORD', }; await IAP.validateReceiptIos(receiptBody, false) .then(response => { try { const renewalHistory = response.latest_receipt_info; const expirationDate = renewalHistory[0].expires_date_ms; const isExpired = Date.now() > expirationDate;
Hello,I’m using Qt (version 6), with cmake builder to create an app on IOS and Android.The code is in C++ for major part of logic, QML for UI, Objective-C and Java for platform-specific logic. The previous version of my app, use Qt5 and QtPurchasing to manage in-app purchase and I have only one non-consumable product to unlock premium features.I have updated my app to Qt6, and make in-app purchase works with qt example with native code.But now, I want to manage auto-renewable subscriptions and I have difficulty with native code to manage it.So I look for RevenueCat but I don’t achieve to install the SDK in my project. I started with IOS integration.I have look the GitHub purchase-ios and try to make direct integration.I have successfully include Purchase.h in my Objective-C file but purchase-ios is not build so linker not found RCPurchase symbol. I have try Swift package but I encounter problems with a Xcode bug which block swift package dependency adding, and failed during loading of
Hi RevenueCat, I’m glad that RevenueCat exists to help bridge the gap for in-app payment/subscription on the different platforms. For my app, I’m currently using Flutter SDK to get in-app auto-renewable subscription setup for both Android and iOS. I have read through the setup docs and have already done the setup, and I’m testing this locally in iOS simulator on iOS 15/14.5.I’m aware that iOS 13 and below, is not compatible with testing in iOS simulator but with 14 and above, it should be compatible. I’m using the latest flutter SDK (purchases_flutter: ^3.8.0)These are the following things done:App Store Connect:In-app purchase package creation App-specific shared secretXcode:Adding In-app purchase feature Package setup StoreKit configurationRevenueCat:Bundle ID setup Package creation to be the same as App Store connect Uploaded StoreKit public certI am able to retrieve the packages that are setup in the Flutter app correctly. However, when the code is called for Purchases.purchasePack
Hi, so we are using ionic capacitor framework. Everything works fine on IOS but we have problem with Android. So when we start the build we are running into this errors. Tried different gradle versions 4.2.2 and 7.0.3 - 7.0.4 "@angular/common": "~12.1.1", "@angular/compiler": "~12.1.1", "@angular/core": "~12.1.1", "@angular/fire": "^6.0.5", "@angular/forms": "~12.1.1", "@angular/platform-browser": "~12.1.1", "@angular/platform-browser-dynamic": "~12.1.1", "@angular/router": "~12.1.1", "@angular/service-worker": "~12.1.1", "@bugsnag/js": "^7.13.2", "@bugsnag/plugin-angular": "^7.13.2", "@capacitor-community/fcm": "^2.0.2", "@capacitor-community/firebase-analytics": "^1.0.0", "@capacitor-community/native-market": "^0.1.4", "@capacitor/android": "3.1.2", "@capacitor/app": "1.0.2", "@capacitor/browser": "^1.0.2", "@capacitor/core": "^3.1.2", "@capacitor/device": "^1.0.3", "@capacitor/haptics": "1.0.2", "@capacitor/ios": "^3.2.
Hello, I am working on updating all my Frameworks including Purchases, specifically trying to get rid of all my PODs and moving them as Swift Packages Dependency. Also, for this I decided to start doing it on the latest version of Xcode in beta and the upcoming iOS 15. I recently noticed that while testing, two things are happening that were not happening before. Products are being displayed on the simulator. The Sign in With Apple ID window is appearing.While testing on the simulator for iOS 14, I was never able to download the products from Revenue Cat, therefore I was only able to test on an my device. But I noticed that it now brings the products and is able to display them on the simulator. However I have not tried to do a purchase from there as I assumed is not going to work as expected. ( This, is actually a good thing because it allows me to test on simulator how my paywall is going to look and react to changes )However, on the second point for some reason, the “Sign in with
Hey there,Fetching the offers works as expected, but purchasing them results in an app crash.The crash only happens on android, ios works fine.I am on react-native-purchases v4.5.0.Testing on a Real Android deviceI am coming from the react-native-iap (5.2.14) package, I uninstalled the react-native-iap package already, but I am not sure if it might is related to that lib, something i forgot to clean up?I checked that the Purchases instance isConfigured:const configured = await Purchases.isConfigured();I tried both methods, purchaseProduct and purchasePackage, both crashed.LOGS:revenueCat Logs:💰 Retrieved skuDetailsList: SkuDetails: {"productId":"com.docomondo.yearly","type":"subs","title":"docomondo Premium (docomondo - dein smarter Dateimanager)","name":"docomondo Premium","price":"CHF 42.00","price_amount_micros":42000000,"price_currency_code":"CHF","description":"Benefit from all available Features!","subscriptionPeriod":"P1Y","freeTrialPeriod":"P4W2D","skuDetailsToken":"AEu..."}💰
Google Play won't allow me to add the subscription items to my product due to "Billing Permissions" in the bundle. The error message is:“To add in-app products, you need to add the BILLING permission to your APK” Team says this in our project and found that it is present in revenue cat sdk.
i dont know how to fix this error,am getting like this in terminal D/[Purchases] - DEBUG( 6672): ℹ️ Found 0 unsynced attributes for App User ID: $RCAnonymousID:ea91c2a133b14d9e8a8f4837df463bb3D/EGL_emulation( 6672): app_time_stats: avg=4.59ms min=1.73ms max=25.40ms count=54D/[Purchases] - DEBUG( 6672): ℹ️ API request started: POST /receiptsD/[Purchases] - DEBUG( 6672): ℹ️ API request completed with status: POST /receipts 503E/[Purchases] - ERROR( 6672): 🤖‼️ There was a credentials issue. Check the underlying error for more details.I/flutter ( 6672): ---------I/flutter ( 6672): PurchasesErrorCode.invalidCredentialsError
We have had 3 instances where a user has been charged twice for a Consumable Product. We have noticed that this happens when the user receives an error (example of error response below) from the API method in React Native await Purchases.purchaseProduct(productId, null, Purchases.PURCHASE_TYPE.INAPP). Below is a snippet of how we use the API method in a try/catch block. try { setIapLoading(true) await Purchases.setAttributes(userAttributes) log.info('Set user attributed', userAttributes) await Purchases.purchaseProduct(productId, null, Purchases.PURCHASE_TYPE.INAPP) log.info('Purchase successful') navigation.navigate(ROUTE_SIGN_UP) } catch (e: any) { if (e.code !== '1') { log.error('IAP Error for Product: ' + productId, JSON.stringify(e)) setIsOpen(true) } } Error Response:{"code":"2","message":"There was a problem with the App Store.","domain":"RCPurchasesErrorDomain","userInfo":{"readable_error_code":"STORE_PROBLEM","readableErrorCode":"STORE_PROBL
Hello,We would like to report an issue we are facing with the RevenueCat framework.We are implementing the delegate to receive subscription status changes, as it’s recommended in the documentation: https://docs.revenuecat.com/docs/purchaserinfo#listening-for-purchaser-info-updatesQuite often, this delegate is called with invalid subscription information. For example, here is one callback from today, December 13th -- the app wasn’t launched since friday, and instead of fetching the new subscription status (which should be “expired”), it returned an active subscription from December 10th:delegate update info: <PurchaserInfo originalApplicationVersion: 1.0, latestExpirationDate: 2021-12-10 16:04:57 +0000 activeEntitlements: { PremiumAccess = { billingIssueDetectedAt = null; expiresDate = “2021-12-10 16:04:57 +0000"; isActive = Yes; isSandbox = Yes; latestPurchaseDate = “2021-12-10 16:01:57 +0000”; originalPurchaseDate = “2021-12-06 16:39
I just installed RevenueCat via CocoaPods, but after I build/run my app (iOS/macOS), I got 60 warnings for each target. PODS: - Purchases (3.13.1) - PurchasesCoreSwift (3.13.1)TARGETS: - macOS (11.0) - iOS (15.0)Xcode: - Version 13.0macOS: - macOS Big Sur (Version 11.5.2)
Hi, RevenueCat is working well for almost all of my users. There is a user where the subscription is not being updated in the RevenueCat system despite the user frequently opening the app. An example user is l6eLj1tGiTZfNUVA who started their subscription 2021-11-05 10:11 AM. The Google Play console shows they been rebilling every month since 2021-11-03 and was last billed on 2022-01-03 however this isn’t shown in RevenueCat so I have to manually check with GPLAY and extend his subscription each time. I checked and this user last opened the app at the start of 2022 so is missing the December billing event, they are also using the most recent version of the app which includes the RevenueCat Cordova plugin. Any help would be appreciated 🙏
Legacy Public API Key is not visible in project settings section under API Keys I created four projects and Legacy Public API Key is visible in only one of my projectand is not visible in the remaining three.i attached the pic below the location for Legacy Public API Key Please help me!!
We are using Flutter and have an Android user who paid for a monthly subscription Dec 9th and canceled, but their subscription should be active until Jan 9th. They were trying to restore their purchase several times but it seems like restoring just hangs after waiting up to 2 minutes. The success/failure toasts that normally appear don’t seem to be triggering for them. Other Android users have been able to restore their purchase successfully.Are there any known issues for when users have canceled but are in an active subscription state? Pasted our restore purchase code & attached a screenshot of our user’s Google Play subscription screen. Future<bool> restorePurchase(BuildContext context) async { final PurchasesErrorCode? code = await requestToRestorePurchases(); if (code == null) { triggerToast(context: context, text: 'Purchase restored!'); triggerHeavyHaptic(); return true; } else { triggerToast( context: context, text: 'Could not restore existing subs
We are building an iOS subscription based app where a user can:Access feature X with no active subscription Access features X & Y with active free trial Access features X, Y & Z with active subscriptionThe features are content based so it might be that the user goes through all content of feature X and Y earlier than the free trial ends and in order to access the following “Z” the user would have to either wait for the trial to convert to a subscription or force end the free trial and subscribe. Question is if there is a way and how to achieve this “force end trial and subscribe” logic. Thank you
Hi,I’m developing on iOS and using StoreKit testing right now. I’m getting my offerings + packages from the RC API no problem now.However, the `packagetType` is `PackageType.custom`. I don’t understand where the package type is set or whether it should be automatic. The docs here list values for the type such as `ANNUAL`:https://docs.revenuecat.com/docs/displaying-products...but there’s nowhere to configure these in RC that I can find. So… presumably it is meant to be working this out from the App Store products… but isn’t because I’m using StoreKit?Either way, this seems very confusing.
After installing the framework by using Carthage with XCFrameworks, some developers have run into an issue when debugging. The issue is that when using `po` to print objects, an error saying `Couldn’t IRGen expression` gets returned. The underlying issue has to do with the way that LLDB stores and looks up debug symbols, which get tied to the machine that originally built the framework. More information on the issue can be found in the following articles: https://steipete.com/posts/couldnt-irgen-expression/ https://darjeelingsteve.com/articles/Resolving-LLDB-%22Couldn't-IRGen-Expression%22-Errors-When-Building-XCFrameworks-Using-Carthage.htmlThankfully, this can easily be worked around:One solution is to pass --no-use-binaries to Carthage (making the overall command carthage update purchases-ios --use-xcframeworks --no-use-binaries, so that the machine that builds the framework is the same one that’s used to debug, thus solving the issue. However, this might not be useful to everyone,
Hello,We’re using Carthage to consume Purchase.xcframework. It’s possible to download the pre-built xcframework within the release as described here. However, your prebuilt xcframework doesn’t contain dSYMs inside. I downloaded xcframework.zip from GitHub and discovered all the dSYMs outside .xcframework itself, in the separate folder. The RevenueCat official iOS SDK Installation guide suggests to run the carthage update with `--no-use-binaries` option which triggers a local build of xcframework. BTW this also might cause a problem such in my case where I don’t have swiftlint installed and getting this error on build:```Adding homebrew bin folder to PATH (/usr/local/bin)error: SwiftLint not installed in /usr/local/bin, download from https://github.com/realm/SwiftLintCommand PhaseScriptExecution emitted errors but did not return a nonzero exit code to indicate failure``` Question:Why not to contain dSYMs inside release pre-built `.xcframework`? Thus, we can run just `carthage update --n
Hi,I need to know if when I use Purchases.syncPurchases();and there is some to sync, a webhook is triggered?e.g. I have some users that used old App, that didn’t use RevenueCat or my own API, but the user update the App and now he can’t access the app because I’m using RevenueCat and controlling the status by server side, but Google or Apple knows that the user is a subscriber.in this case, if I use the sync method and when Revenue update a trigger will fired? Or I need to use the Rest API to know?obs. I’m using Flutter for the Apps.
When my app ran, everything was fine. But with SwiftUI Preview, Revenue Cat can’t run. As it relied on the instance of `AppDelegate`, there is no `AppDelegate` in SwiftUI Preview.```Purchases.configure(withAPIKey: "api key")```Is there a way to set `Purchases.configure(withAPIKey: "api key")` in SwiftUI Preview? Currently I had to comment code so the preview could work.
Hello, Apple updated app store prices in Turkey on December 8.For example: The option of 8.99 Turkish Lira (Tier 1) increased to 16.99(Tier 1) Turkish Lira.I see updated prices in the App Store Connect Panel. There's no problem here. BUT IN MY APP, THE PRICES ARE OLD. coin_100 - SkuDetails: {"productId":"coin_100","type":"inapp","title":"100 x Coin (x)","name":"100 x Coin","price":"₺8,99","price_amount_micros":8990000,"price_currency_code":"TRY","description":"100 x Coin is defined in the account",
Just wanted to give a shout out to the Revenue Cat team. @ 3:19 p.m. today Apple Review made first in-app purchase of my auto-renewing subscription and @ 3:24 p.m. I received email welcoming me to the App Store from Apple.I actually expected a lot more testing of the In-App purchase portion of the app because I know I spent a lot of time testing it and making last minute changes. But who am I to complain.Of course I got some rejections along the way for Rating, and Safety Guidelines but the In-App purchases flow went flawlessly thanks to the great staff Revenue Cat has assembled.I think back to my previous company where I did receipt validation locally (couldn’t afford a server backend staff) and thought it was crazy that every developer had to do this decryption validation of receipt. Even crazier was the verbose language you had to put on your paywall in a vertically challenged render space. I believe we got rejected six days in a row just for the wording on the paywall and the l
My test environments: Running XCode(Sandbox) and TestFlight. PRICES THAT LOOK WRONG I Have 9 consumable products. Prices I choose in Prices that the app store connect => appear in panel my app__________________ ____________________________________16.99 TRY(TİER 1) => But my on the application screen 8.99 TRY 34.99 TRY(TİER 2) => But my on the application screen 18.99 TRY 49.99 TRY(TİER 3) => But my on the application screen 27.99 TRY 119.99 TRY(TİER 7) => But my on the application screen 64.99 TRY 279.99 TRY(TİER 17) => But my on the application screen 159.99 TRY 829.99 TRY(TİER 49) => But my on the application screen 459.99 TRY Note: 1- Purchase works successfully. It's just the wrong price.2-) There is no problem with Google Play Store prices.3-) My app is not in publish mode,
My API get a list of my products (from my server) and display it on app. I'm using revenuecat only to do the subscription.The problem is that, for each country with his own currency, I need to display the right price, it means, my server doesn't know what is the users country to provide the correct price from Apple.There is a way on Revenuecat for me send the SKU and get the price based on the user's country?
In the sandbox environment, when I call Purchases.purchaseProduct or Purchases.purchasePackage (my product is auto-renewable), the payment sheet pops up for confirmation as expected. After I entered my credentials and pressed confirm, the payment sheet shows up again. I have to reenter my credential to confirm the purchase. This happens if the user does not have any subscriptions initially. Another big issue related to this is when the subscription expires, I cannot make a purchase to the same subscription because the payment sheet doesn’t show up at all, and the SDK console says it will not process because the purchase/transaction is a duplicate. TIA!
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.