Build a customized mobile subscription business with RevenueCat. We do the heavy lifting of normalizing subscribers from any source and maintain a single source of truth for subscription status, so you can get back to building your app.
RevenueCat is a powerful, secure, reliable, and free to use in-app purchase server with global support. All you need to get started is an API key.
ERROR: {"error":{"code":2,"message":"There was a problem with the App Store.","readable_error_code":"STORE_PROBLEM","underlyingErrorMessage":"Problem communicating with the Store when trying to validate the receipt.","readableErrorCode":"STORE_PROBLEM"},"userCancelled":false} ``` const response = await this.purchases.purchaseProduct(this.PRODUCT_ID); ``` typescript
Posted by Felipe 2 days ago
I created a consumable IAP (iOS) and tested the following scenario (https://developer.apple.com/documentation/storekit/in-app_purchase/testing_in-app_purchase_transactions): > Test an Interrupted Transaction > Set a breakpoint in your transaction queue observer’s paymentQueue(_:updatedTransactions:) method so you can control whether it delivers the product. Then make a purchase as usual in the test environment, and use the breakpoint to temporarily ignore the transaction, for example, by returning from the method immediately using the thread return command in the LLDB debugger. > Terminate and relaunch your app. StoreKit calls the paymentQueue(_:updatedTransactions:) method again shortly after launch. This time, let your app respond normally. Verify that your app correctly delivers the product and completes the transaction. I am using the purchases_flutter plugin (1.1.0) and from the documentation i can find no way to get the interrupted transaction. Moreover if i try to buy the same consumable again i get the following message from StoreKit: “This In-App Purchase has already been bought. It will be restored for free.” Is there any way to recover from this situation? Thanks.
Posted by Frederik 3 days ago
Hey everyone, Our latest update was rejected with the message: "We have started the review of your app, but we are not able to continue because we need an expired demo account to fully assess the subscription feature." We provided them with login info to an account that had previously had a subscription but no longer does. When resubmitting with this, we got rejected again for the same reason. Our subscriptions have been running fine for the last year, and the update contained no changes to anything subscription related. Any idea what more we can provide them or what we should do?
Posted by Michael 4 days ago
My app was just rejected again and I thought you might want to see the message from Apple: When validating receipts on your server, your server needs to be able to handle a production-signed app getting its receipts from Apple’s test environment. The recommended approach is for your production server to always validate receipts against the production App Store first. If validation fails with the error code "Sandbox receipt used in production," you should validate against the test environment instead. They also attached a screen shot so I know they were testing a subscription purchase and purchasePackage() return some error.
Posted by Michael Chartier 7 days ago
Hello, We currently have an iOS app out and were getting ready to launch a Mac Catalyst version of the app. In preparation for that we made a MacOS App in AppStoreConnect and gave RevenueCat the Mac App Store shared secret of that app. But since Apple released Universal purchases, we just want to use that so we deleted the Mac Catalyst version from AppStoreConnect (we haven't launched the Catalyst version yet) and gave our new Catalyst app the same bundle ID as the iOS version (to work with universal purchase). However, our "macOS Configuration" settings in RevenueCat still has the old Mac App Store shared secret key and there seems to be no way to delete this. What are the next steps in removing this key?
Posted by Fran 8 days ago
Hello, Our app uses does not included a login which means we have to use RevenueCat's Anonymous App User ID. We give a promotional free trial for new users, but since we use Anonymous App User IDs, the users can just delete the app and re-download it to get an another free trial. We think we can substitute Apple's Device Check (https://developer.apple.com/documentation/devicecheck) to know when a user already downloaded the app in the past with RevenueCat's subscriber attributes where we can just save the user's device id as an attribute. The only concern we have is mixing this with RevenueCat's Anonymous App User ID since it restarts whenever a user re-downloads the app. Is there a way around this with subscriber attributes or anything else?
Posted by Fran 8 days ago
Hi my application was not released yet and I was making purchase with sandbox user, the purchase was successful until show the dialog however it's ended "There was a problem with App store". This is the log: 2020-03-27 21:00:02.933854+0700 Runner[283:6154] [Purchases] - DEBUG: Vending offerings from cache 2020-03-27 21:00:02.934171+0700 Runner[283:6154] [Purchases] - DEBUG: makePurchase 2020-03-27 21:00:02.934924+0700 Runner[283:6154] [Purchases] - DEBUG: makePurchase - rocket_plan - Offering: Rocket Sales 2020-03-27 21:00:02.936578+0700 Runner[283:6154] Purchase Started !! 2020-03-27 21:00:02.940258+0700 Runner[283:6154] [Purchases] - DEBUG: PaymentQueue updatedTransaction: rocket_plan (null) ((null)) (null) - 0 2020-03-27 21:00:11.081338+0700 Runner[283:6422] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C10.1:2][0x118f416c0] get output frames failed, state 8196 2020-03-27 21:00:11.090565+0700 Runner[283:6422] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C10.1:2][0x118f416c0] get output frames failed, state 8196 2020-03-27 21:00:11.097460+0700 Runner[283:6422] TIC Read Status [10:0x0]: 1:57 2020-03-27 21:00:11.098430+0700 Runner[283:6422] TIC Read Status [10:0x0]: 1:57 2020-03-27 21:00:15.153365+0700 Runner[283:6946] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C11.1:2][0x105ebc3a0] get output frames failed, state 8196 2020-03-27 21:00:15.153828+0700 Runner[283:6946] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C11.1:2][0x105ebc3a0] get output frames failed, state 8196 2020-03-27 21:00:15.155711+0700 Runner[283:6946] TIC Read Status [11:0x0]: 1:57 2020-03-27 21:00:15.155885+0700 Runner[283:6946] TIC Read Status [11:0x0]: 1:57 2020-03-27 21:00:21.869236+0700 Runner[283:6154] [Purchases] - DEBUG: applicationDidBecomeActive 2020-03-27 21:00:34.021713+0700 Runner[283:6422] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C12.1:2][0x105fc9bc0] get output frames failed, state 8196 2020-03-27 21:00:34.022150+0700 Runner[283:6422] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C12.1:2][0x105fc9bc0] get output frames failed, state 8196 2020-03-27 21:00:34.029236+0700 Runner[283:6422] TIC Read Status [12:0x0]: 1:57 2020-03-27 21:00:34.029354+0700 Runner[283:6422] TIC Read Status [12:0x0]: 1:57 2020-03-27 21:00:36.757952+0700 Runner[283:6154] [Purchases] - DEBUG: applicationDidBecomeActive 2020-03-27 21:00:38.441530+0700 Runner[283:6154] Purchase Successful !! . 2020-03-27 21:00:38.446675+0700 Runner[283:6154] [Purchases] - DEBUG: PaymentQueue updatedTransaction: rocket_plan 1000000644273179 ((null)) 1000000643822621 - 1 2020-03-27 21:00:38.448914+0700 Runner[283:6154] [Purchases] - DEBUG: Loaded receipt from file:///private/var/mobile/Containers/Data/Application/5554A108-BAAC-4BDD-A2B4-62376A2E1B11/StoreKit/sandboxReceipt 2020-03-27 21:00:38.469747+0700 Runner[283:6154] [Purchases] - DEBUG: POST /v1/receipts 2020-03-27 21:00:40.174393+0700 Runner[283:7006] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C14.1:2][0x116370a60] get output frames failed, state 8196 2020-03-27 21:00:40.174988+0700 Runner[283:7006] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C14.1:2][0x116370a60] get output frames failed, state 8196 2020-03-27 21:00:40.176859+0700 Runner[283:7006] TIC Read Status [14:0x0]: 1:57 2020-03-27 21:00:40.177278+0700 Runner[283:7006] TIC Read Status [14:0x0]: 1:57 2020-03-27 21:00:41.009084+0700 Runner[283:7312] [Purchases] - DEBUG: POST /v1/receipts 503 2020-03-27 21:00:41.014570+0700 Runner[283:7312] [Purchases] - ERROR: There was a problem with the App Store. 2020-03-27 21:00:52.941614+0700 Runner[283:6154] [Purchases] - DEBUG: applicationDidBecomeActive
Posted by Steve 10 days ago
For iOS Is it necessary to call Purchases API from the main thread? I changed my code to use the main thread and it works as expected. But when I do not use the main thread I discovered the call to purchaserInfo() does NOT execute the closure. Here is the gist of the code: CKContainer.default().fetchUserRecordID { recordID, error in Purchases.configure(withAPIKey: "key", appUserID: recordID.recordName) Purchases.shared.delegate = self Purchases.shared.purchaserInfo { (purchaserInfo, error) in // process the data here in the closure }} First I get the CloudKit user record because I want to use that user record as the appUserID for Purchases. Then I call configure() and then purchaserInfo(). The closure is completely skipped. Purchases 3.1.2 on iOS 13.4
Posted by Mike Chartier 10 days ago
I am trying to upgrade Purchases for subscription attributes. When I add pod 'Purchases', '3.1.1', I get the following error. If I leave out the version number I get purchases 3.0 and don't have access to attributes. CocoaPods could not find compatible versions for pod "Purchases": In Podfile: Purchases (= 3.1.1) None of your spec sources contain a spec satisfying the dependency: `Purchases (= 3.1.1)`. You have either: * out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`. * mistyped the name or version. * not added the source repo that hosts the Podspec to your Podfile.
Posted by David 10 days ago
offerings() must use the network connection to download data from revenue cat servers right? If the network connection is down or there is some server problem, how long will it take before the completion handler is called with an error? The reason I ask is that my app was rejected because it would not display the prices for subscriptions. The only way I can see this happening is if the completion handler was not called for a long time.
Posted by Mike Chartier 11 days ago
after a long period of time running without any problem it failed to retrieve the activeProduct (SKProduct) Using sdk version 2.1.0 Failed to connect to app store message on debug messages [Purchases] - DEBUG: SKRequest failed: Não pôde conectar com a iTunes Store
Posted by Jackson s 11 days ago
Hi I am using Flutter and already successfully setup the account, and can fetch the list of packages. However, when I am loading for first time and trying to make purchase I get this error: "There was a problem with the Play Store. | Google Play Error: The project id used to call the Google Play Developer API has not been linked in the Google Play Developer Console." I have followed the setup completely including this step: https://docs.revenuecat.com/docs/creating-play-service-credentials Is there any missing step and what is the solution? Thank you This is the log: D/[Purchases] - DEBUG(24741): Debug logging enabled. D/[Purchases] - DEBUG(24741): SDK Version - 3.0.4 D/[Purchases] - DEBUG(24741): Initial App User ID - null D/[Purchases] - DEBUG(24741): Identifying App User ID: $RCAnonymousID:54b92a6c8e2b4eaf95123a1202f4a6a2 D/[Purchases] - DEBUG(24741): App foregrounded D/[Purchases] - DEBUG(24741): Cache stale D/[Purchases] - DEBUG(24741): [QueryPurchases] Skipping updating pending purchase queue since BillingClient is not connected yet D/[Purchases] - DEBUG(24741): Listener set D/[Purchases] - DEBUG(24741): Sending latest purchaser info to listener D/[Purchases] - DEBUG(24741): Starting connection for [email protected] D/[Purchases] - DEBUG(24741): Ending connection for [email protected] D/[Purchases] - DEBUG(24741): Billing Service Setup finished for [email protected] D/[Purchases] - DEBUG(24741): [QueryPurchases] Updating pending purchase queue D/[Purchases] - DEBUG(24741): No cached offerings, fetching D/[Purchases] - DEBUG(24741): GET /subscribers/%24RCAnonymousID%3A54b92a6c8e2b4eaf95123a1202f4a6a2 D/[Purchases] - DEBUG(24741): GET /subscribers/%24RCAnonymousID%3A54b92a6c8e2b4eaf95123a1202f4a6a2 200 D/[Purchases] - DEBUG(24741): Purchaser info updated, sending to listener D/[Purchases] - DEBUG(24741): GET /subscribers/%24RCAnonymousID%3A54b92a6c8e2b4eaf95123a1202f4a6a2/offerings D/[Purchases] - DEBUG(24741): GET /subscribers/%24RCAnonymousID%3A54b92a6c8e2b4eaf95123a1202f4a6a2/offerings 200 D/[Purchases] - DEBUG(24741): Requesting products with identifiers: basic_plan, rocket_plan D/[Purchases] - DEBUG(24741): Requesting products with identifiers: basic_plan, rocket_plan D/[Purchases] - DEBUG(24741): [QueryPurchases] Querying subs D/[Purchases] - DEBUG(24741): [QueryPurchases] Querying inapp D/[Purchases] - DEBUG(24741): [QueryPurchases] Querying inapp D/[Purchases] - DEBUG(24741): Products request finished for basic_plan, rocket_plan D/[Purchases] - DEBUG(24741): Retrieved skuDetailsList: SkuDetails: {"skuDetailsToken":"AEuhp4LJn3zz4D_JSBFhb4P3AnEPRTXcfPEga_kVN_wDN0WhuolUHP3lw79A2WRXj0Y=","productId":"rocket_plan","type":"subs","price":"IDR 50,000.00","price_amount_micros":50000000000,"price_currency_code":"IDR","subscriptionPeriod":"P1M","title":"Member Roket Terbang (Konekzy)","description":"Paket Roket Terbang membuka semua fitur dan akses di aplikasi Konekzy"} D/[Purchases] - DEBUG(24741): rocket_plan - SkuDetails: {"skuDetailsToken":"AEuhp4LJn3zz4D_JSBFhb4P3AnEPRTXcfPEga_kVN_wDN0WhuolUHP3lw79A2WRXj0Y=","productId":"rocket_plan","type":"subs","price":"IDR 50,000.00","price_amount_micros":50000000000,"price_currency_code":"IDR","subscriptionPeriod":"P1M","title":"Member Roket Terbang (Konekzy)","description":"Paket Roket Terbang membuka semua fitur dan akses di aplikasi Konekzy"} D/[Purchases] - DEBUG(24741): Requesting products with identifiers: basic_plan D/[Purchases] - DEBUG(24741): Products request finished for basic_plan, rocket_plan D/[Purchases] - DEBUG(24741): Retrieved skuDetailsList: SkuDetails: {"skuDetailsToken":"AEuhp4LJn3zz4D_JSBFhb4P3AnEPRTXcfPEga_kVN_wDN0WhuolUHP3lw79A2WRXj0Y=","productId":"rocket_plan","type":"subs","price":"IDR 50,000.00","price_amount_micros":50000000000,"price_currency_code":"IDR","subscriptionPeriod":"P1M","title":"Member Roket Terbang (Konekzy)","description":"Paket Roket Terbang membuka semua fitur dan akses di aplikasi Konekzy"} D/[Purchases] - DEBUG(24741): rocket_plan - SkuDetails: {"skuDetailsToken":"AEuhp4LJn3zz4D_JSBFhb4P3AnEPRTXcfPEga_kVN_wDN0WhuolUHP3lw79A2WRXj0Y=","productId":"rocket_plan","type":"subs","price":"IDR 50,000.00","price_amount_micros":50000000000,"price_currency_code":"IDR","subscriptionPeriod":"P1M","title":"Member Roket Terbang (Konekzy)","description":"Paket Roket Terbang membuka semua fitur dan akses di aplikasi Konekzy"} D/[Purchases] - DEBUG(24741): Requesting products with identifiers: basic_plan D/[Purchases] - DEBUG(24741): [QueryPurchases] Purchase of type inapp with hash pDyOVEI67zRm0y100dgqV+Aoa6g= D/[Purchases] - DEBUG(24741): [QueryPurchases] Cleaning previously sent tokens D/[Purchases] - DEBUG(24741): [QueryPurchases] Tokens already posted: [] D/[Purchases] - DEBUG(24741): Products request finished for basic_plan D/[Purchases] - DEBUG(24741): Retrieved skuDetailsList: SkuDetails: {"skuDetailsToken":"AEuhp4LKH1y_-kuDaJc4ex4keacx19Rv0IEpyBRhnRP85jbsk_E85x_JGvg1irb7N_8A","productId":"basic_plan","type":"inapp","price":"IDR 50,000.00","price_amount_micros":50000000000,"price_currency_code":"IDR","title":"Basic Plan (Konekzy)","description":"Paket berbayar untuk membuka fitur standar chat, komunitas dan ilmu"} D/[Purchases] - DEBUG(24741): basic_plan - SkuDetails: {"skuDetailsToken":"AEuhp4LKH1y_-kuDaJc4ex4keacx19Rv0IEpyBRhnRP85jbsk_E85x_JGvg1irb7N_8A","productId":"basic_plan","type":"inapp","price":"IDR 50,000.00","price_amount_micros":50000000000,"price_currency_code":"IDR","title":"Basic Plan (Konekzy)","description":"Paket berbayar untuk membuka fitur standar chat, komunitas dan ilmu"} D/[Purchases] - DEBUG(24741): Products request finished for basic_plan D/[Purchases] - DEBUG(24741): Retrieved skuDetailsList: SkuDetails: {"skuDetailsToken":"AEuhp4LKH1y_-kuDaJc4ex4keacx19Rv0IEpyBRhnRP85jbsk_E85x_JGvg1irb7N_8A","productId":"basic_plan","type":"inapp","price":"IDR 50,000.00","price_amount_micros":50000000000,"price_currency_code":"IDR","title":"Basic Plan (Konekzy)","description":"Paket berbayar untuk membuka fitur standar chat, komunitas dan ilmu"} D/[Purchases] - DEBUG(24741): basic_plan - SkuDetails: {"skuDetailsToken":"AEuhp4LKH1y_-kuDaJc4ex4keacx19Rv0IEpyBRhnRP85jbsk_E85x_JGvg1irb7N_8A","productId":"basic_plan","type":"inapp","price":"IDR 50,000.00","price_amount_micros":50000000000,"price_currency_code":"IDR","title":"Basic Plan (Konekzy)","description":"Paket berbayar untuk membuka fitur standar chat, komunitas dan ilmu"} I/flutter (24741): basic_plan I/flutter (24741): 50000.0 I/flutter (24741): rocket_plan I/flutter (24741): 50000.0 D/[Purchases] - DEBUG(24741): POST /receipts D/[Purchases] - DEBUG(24741): POST /receipts 503 E/[Purchases] - ERROR(24741): There was a problem with the Play Store. | Google Play Error: The project id used to call the Google Play Developer API has not been linked in the Google Play Developer Console.
Posted by Steve 12 days ago
Hi RevenueCat team, I have a subscription system in my iOS app that's mainly focused around an iOS Extension. Unfortunately StoreKit is not supported in the extension and I am unable to verify subscription status there. My workaround has been to store the subscription status in a shared User Defaults object that can then be accessed in the Extension, but the downside to this approach is that the user needs to re-open the main application on subscription renewal to verify they're still subscribed and update the User Defaults. I have been pushing yearly subscriptions to minimize the interruption, but it's still a pain and cause for churn. I have been meaning to set up a server for App Store Webhook updates and create a user management system to track subscription status instead of the User Defaults, that way users no longer have to re-open the main application on renewal to verify subscription status. However this is a significant amount of work and I was hoping to avoid it entirely by migrating to RevenueCat. My question is therefore, does RevenueCat support this? If I set up Apple's server-to-server subscription updates to point to RevenueCat, can I access the user's renewed subscription status through the SDK in my app extension without ever having the user open the main application and therefore processing the renewal transaction? I see there is a method that allows you to specify a `userDefaults` object on initialization of the SDK to work across app extensions, but does this still require the occasional opening of the main application to process renewals? In advance, thank you.
Posted by Aleksander S. 12 days ago
Hi! I just read your blog about subscriber attributes and I find it super cool, might be the thing that makes me go from free to the Analyse plan! My question is, could you use this feature literally for every kind of email? For example, can I use it for sending an email to everyone who has joined 5 days ago and they haven't subscribe yet? Or for example, can I send an offer to everyone who is not premium at this moment? Sorry if this question is dumb, I have never used Zapier so I don't really don't know what's possible here. Thank you!
Posted by Joan 13 days ago
Firstly, great guide! https://docs.revenuecat.com/docs/errors I'm just trying to build some custom error handling around it. This is tricky in React Native because the readable_error_codes are different on each platform. e.g. "STORE_PROBLEM" iOS vs "StoreProblemError" Android. This makes any logic complex and error-prone. Is there any chance of adding a key to the userInfo with a consistent key? Alternatively, so you have any recommendations for handling this? Thanks
Posted by Matt D 13 days ago
The app has a free trial that also requires a login. The flow is that the user first signs up using their login info, and then once we validate the login info we offer them a 14 day free trial before giving them access to the app services. I'm wondering where a "Restore Purchases" option should go in this case. On the login screen? Or within the app in the Accounts section? My ideal scenario would be that RevenueCat applies the receipt to whatever app_user_id they eventually login with after I call Purchases.identify (i'm using cordova), and removes those entitlements from any previous user accounts Do I need to anything else special in my application code?
Posted by Jordan 16 days ago
I submitted my app to the app store and was rejected because of: "Guideline 2.1 - Information Needed We have started the review of your app, but we are not able to continue because we cannot locate the in-app purchases within your app. - Unable to locate subscription" They included screenshots of all of my paywalls not loading the subscriptions. I know loading the subscriptions work because I've been testing them for the past few weeks and even checking them on the app while the apple review was in session and after. Is there a reason the subscriptions were not being loaded for the app reviewer but loaded for me?
Posted by Fran 17 days ago