SDKs

I'm experiencing an issue where some users are able to make repeated purchases without actually being charged. The problem is that multiple purchases are being reported with the same transaction_id as the original purchase. From the user's perspective, it looks like a new purchase was made, but no new transaction or payment actually occurred in the App Store.This leads to users getting access multiple times without paying again.

Hello, [Flutter App - PayWall]I’ve checked different topics related to mine and i can’t fix my issue.I wanted to show the close button on my paywall. But unfortunally even if i’m using :await RevenueCatUI.presentPaywallIfNeeded(paywallKey, displayCloseButton: true); As described in the doc, it’s not working. Some people said the button is only black for them but in my case, i can’t find any it at all, so i need help. Here’s what it looks like and i’m using this recent version :purchases_flutter: 8.10.4purchases_ui_flutter: 8.10.4 

Hi, i have been facing `there was a problem with the store` for over 2 weeks and don’t have a clue how to solve this issue. subscriptions have been working on my app in production but suddenly emitting errors when users are trying to subscribe. Weird thing is, it succeeds in sandbox mode with test cards but only fails in production with real payment methods. On official doc revenuecat suggests the following solutions:Google server is down → unlikely. it has been failing for ever 2weeks by 100% chance. Google Play Developer API Quota exceeded → Checked and only has 1 or 2 usages only Invalid Android package name in the RevenueCat dashboard → unlikely because it used to work before and still working in sandbox mode. Google Billing Client SERVICE_TIMEOUT error → Not sure if this is the case but what can i do if this is the issue?I have also went through the integration guide again and checked if my products and paywalls are valid. I have been receiving customer complaints and unable to re

Hey!Found issue with footer background color on iOS SDK version 5.34.0(latest at the moment). it should be black but now it's grey. Black or white system iOS appearance - the same result.  My Main Section setting for paywall at the screenshot (also black). I using .originalTemplatePaywallFooter() modifier for presenting footer in the iOS SwiftUI app. 

See also closed topic I would add my solution to that post but it is now closed for comments.Experience an issue on build where audioservice no longer worked if main activity became a fragmented activity.The solutions in the end was on the audioservice page itself: https://pub.dev/packages/audio_service , see ‘Integration as a FragmentActivity‘In the end this MainActivity.kt worked to resolve the issue for me:package com.something.appimport com.ryanheise.audioservice.AudioServiceFragmentActivityclass MainActivity: AudioServiceFragmentActivity() {}No changes were required in the AndroidManifest, the activity name still is android:name=".MainActivity"Hope this helps, I busted my skull on this one (and Claude’s, and Grok’s, ...)

unable to build android with on a flutter project enabled for paywalls. was working fine with previous purchases package but looking at below error. notes: tried updating java version to 17 and respective changes in gradle files etc..,increased minSdkVersion, separate note was able to build on iOS and paywall works as expected logs hereCaused by: java.lang.RuntimeException: Failed to transform '/Users/CC/.gradle/caches/modules-2/files-2.1/androidx.compose.material3/material3/1.1.0/dfa0976101de9daf0c4676fb7227fd540d4d1a08/material3-1.1.0.aar' using Jetifier. Reason: IllegalArgumentException, message: Unsupported class file major version 61. (Run with --stacktrace for more details.)  

Web SDK card declined doesn't inform the client that is being denied. Shouldn’t some kind of notification or some text appear to tell the user the card was declined?

Is it possible for developers to set an appAccountToken before a user makes a purchase? The reason being is because we want to create a pending transaction object on our server, send that object ID as the appAccountToken through RevenueCat’s purchase request, and then update that object on our server once we receive the webhook from RevenueCat where we can then update that pending transaction object with the transaction information from Apple/Revenuecat. We would need the appAccountToken to be sent through the RevenueCat webhook when it’s received from Apple. We need this to implement consumable and non-consumable products. Thanks!

Hello RevenueCat, We switched to RevenueCatPaywall system.It was working correctly and still is working most of our users, but paywall isn't displaying in 2 test device. When opening the Paywall, we send the information to MixPanel with an event whether it was displayed successfully or not.936,000 users were able to successfully view the paywall, but 156 users were unable to open it. We're requesting assistance with this issue.I am sending you the code we used to open Paywall below:private fun launchPaywallActivity() {        lifecycleScope.launch {            delay(200)            Purchases.sharedInstance.getOfferingsWith(                onError = { closeWithResult() },                onSuccess = { offerings ->                    offerings.current?.let { currentOffering ->                        assignedOffer = currentOffering                        val launcher = paywallActivityLauncher                        if (launcher == null) {                            closeWithResult() 

I'm running a React Native app and using the RevenueCat (RC) SDK.The RC SDK is initialized "successfully" with the below warnings.Please note that it says "you can still make test purchases with the RevenueCat SDK", however, the call to Purchases.getOfferings() returns empty.I have gone through the step-by-step troubleshooting checklist for iOS (which the below logs confirm), still, the offering are not being returned.=============LOGS=============[RevenueCat] ⚠️ RevenueCat SDK is configured correctly, but contains some issues you might want to addressWarnings:  • Your products are configured in RevenueCat but aren't approved in App Store Connect yet. This prevents users from making purchases in production. Please ensure all products are approved and available for sale in App Store Connect.  • The offerings 'standard-offering', … have configuration issues that may prevent users from seeing product options or making purchases.Product Issues:  ⏳ com.helloneighbor.starkeyranch.standard_1x

Hey, I'm using RevenueCat in my React Native app. When I attempt to purchase a subscription, the subscription sheet opens successfully, but after clicking "Subscribe," the process fails and returns an error.My product is already approved by the App Store, and I’ve tested it both in Sandbox and through TestFlight, but I’m still encountering the same issue.ERROR: ERROR  [RevenueCat] 💰 Product purchase for 'com.monthly_7D' failed with error: PurchasesError(error: There was a problem with the App Store., userInfo: ["source_file": "RevenueCat/StoreKitError+Extensions.swift:43", "readable_error_code": "STORE_PROBLEM", "NSLocalizedDescription": "There was a problem with the App Store.", "source_function": "asPurchasesError", "NSUnderlyingError": StoreKit.StoreKitError.unknown])

Description:Hi RevenueCat Support,I'm encountering a persistent BackendError (Internal server error) with the following message during in-app purchase attempts:[RevenueCat] 😿‼️ There was an unknown backend error. Internal server error.[RevenueCat] 😿‼️ RevenueCat SDK Configuration is not validWe encountered an unknown error that prevented the operation from completing. This is likely a temporary issue. Please try again in a few moments and, if the problem persists, contact support with this error: The operation couldn’t be completed. (RevenueCat.BackendError error 0.).Thanks,Dhaval Panchal

Hello I’m having trouble getting my custom fonts working with the paywall editor. Here is my expo-font config. The font I’m trying to add is AlfaSlabOne-Regular.ttf. `[        'expo-font',        {          fonts: [            './assets/fonts/AlfaSlabOne-Regular.ttf',            './assets/fonts/AlternateGotNo2D.ttf',            './assets/fonts/Roboto-Regular.ttf',            './assets/fonts/RobotoCondensed-SemiBold.ttf',            './assets/fonts/RobotoCondensed-SemiBoldItalic.ttf',            './assets/fonts/RobotoMono-Regular.ttf',            './assets/fonts/Roboto-MediumItalic.ttf',          ],        },      ],` I saw the conversation here but that version of expo fonts where you can put the android and ios fonts in the config requires Expo 53 which I’m not ready to upgrade to. Also, it looks like the add font UI changed in the paywalls and you now upload the font directly. It is working properly on iOS.Any ideas?  Thanks,Alan

Hello I have been working with RevenueCat just fine for a couple of months, and suddenly I started having problems with in some devices. The calls to get the customer info, and the offerings, are not returning anything, I can see the debug logs but the function just hangs and does not return anything not even an exception.Every call is under a try catch finally, I am logging every path and only the START is logged, and I can't get any information. Device: iPhone 13 Pro MaxiOS: 18.5Here are some logs:LOG  START - Getting subscription plan LOG  START - Getting subscription plan DEBUG  Token expired DEBUG  No Refresh token DEBUG  [RevenueCat] ℹ️ Configuring SDK using RevenueCat's UserDefaults suite. DEBUG  [RevenueCat] 👤 Identifying App User ID DEBUG  [RevenueCat] ℹ️ Observing StoreKit.Transaction.updates DEBUG  [RevenueCat] ℹ️ Debug logging enabled DEBUG  [RevenueCat] ℹ️ SDK Version - 5.30.0 DEBUG  [RevenueCat] ℹ️ Bundle ID - ***** DEBUG  [RevenueCat] ℹ️ System Version - Version 18.5 (B

It would be good to have some settings for close button to visible after some delay. My paywall is not hard paywall but i dont want to show that close button directly. Users searching for that close buttons directly in the onboarding. Really tried with 10 different person, they immediately clicked the close button. All the fullscreen skippable ads we see on the apps uses the same basic trick, they delay the close button. We need this, I was using legacy paywalls with custom swift view for paywall but i switched to new paywall builder. 

I am using purchases-kmp, and I keep getting Undefined symbol: _OBJC_CLASS_$_RCCommonFunctionality error when I build on Xcode. As far as my search is concern it is because I am missing the PurchasesHybridCommon, but attempting to install via swift package manager yields purchaseshybridcommon.git could not be resolved. Support says to use purchases-ios, but linker error persists. 

If I edit the “Badge intro offer text” Textfield I’m getting parsing errors. So I’m not able to publish my paywall anymore. There seems to be no error on my side if you ask me.The only way to fix is to delete the badge completely.In this case I have to readd the badge from scratch. As long as I don’t touch the  “Badge intro offer text” field everything works. But as soon I change a single character in the  “Badge intro offer text” field, the paywall is broken.

Basicly followed everything, checked documentation, checked on forum.checked on youtube this video is 2 weeks ago, btw he can have offerings in console dont know how is possible anyway:me I got this :[RevenueCat] [configure], You successfully installed the RevenueCat SDK. However, it's currently running in Preview API mode because it requires some native modules that are not available in Expo Go. All the APIs are available but have no effect. Please, use a development build to test the real behavior of the RevenueCat SDK.[RevenueCat] [getCustomerInfo] This method is available but has no effect in Preview API mode. WARN  [RevenueCat] [getProducts] This method is available but has no effect in Preview API mode. WARN  [RevenueCat] [getOfferings] This method is available but has no effect in Preview API mode.Did a test build but nothing just :Error checking subscription status:', [Error: There is no singleton instance. Make sure you configure Purchases before trying to get the default inst

Hi RevenueCat team,One of my users in China is encountering the following error when attempting to make a purchase:"The device or user is not allowed to make the purchase."The issue seems specific to their location or account. The subscription works fine for users in other countries.Can you help clarify what could be causing this?Thank you.

I’m getting the following error after trying to build with eas:✖ Build failed🍏 iOS build failed:The "Run fastlane" step failed because of an error in the Xcode build process. We automatically detected following errors in your Xcode build logs:- value of type 'AppTransaction' has no member 'appTransactionID'Refer to "Xcode Logs" below for additional, more detailed logs. These are my SDK versions:    "react-native-purchases": "^9.1.0",    "react-native-purchases-ui": "^9.1.0", Any solutions? The problem happens with android too. I tried downgrading to version 8 and that did not help either.

Platform: iOS (Ionic/Angular)Environment: SandboxProblem descriptionWhen user upgrades from a monthly subscription to an annual subscription, the upgrade is not reflected in getCustomerInfo() until the current subscription period expires and the new subscription becomes active.I have own paywall screen and wanna show that new subscription will be active from __date__.Apart from that I tried to reload app, invalidate cache and make sync. Also tried to request customerInfo from API ( but it doesn’t return any sub info ). 

It doesn’t seem like Purchases object can work with Mono anymore. It broke the prefab I’ve been using and setup with the Purchases object.

I custom using Adjust to log event.I need get transaction_id but I don't find data when purchased.if return customer info this the best

I'm encountering a 409 Conflict error when attempting to grant a promotional entitlement through the RevenueCat API. The request is failing consistently with the same error code.API Endpoint: POST /v1/subscribers/{subscriber_id}/entitlements/{entitlement_id}/promotionalWhat specific condition is causing the 409?

i update purchases_flutter 9.0.0 in google play show App must use Google Play Billing Library version 7.0.0 or later I would like to know if there is anything else I need to do to ensure that the system supports Google Play Billing Library version 7.0.0 or later.