SDKs

I’m building a paywall that I would like to have a conditional ‘Close’ button on - in some cases it should be a hard paywall, but in others, I want the user to opt out. I’m showing the paywall with `PaywallView(offering: offering, displayCloseButton: <logic-goes-here>)`, but even if I send in a hardcoded true or false, it makes no difference. I’ve tried this with my Paywall equipped with a ‘Navigate Back’ button, and without, but the ‘displayCloseButton’ parameter never has any effect.

We’ve periodically been seeing a “There was a problem with the store” error when Android users try to purchase. Does RevenueCat have any logs that can help diagnose the error? Or how can I diagnose this problem?

Hello,We’ve got a Flutter app that requires user register / login and we’re providing the SDK with an App User ID tied to those credentials to allow our users to share the same subscription among multiple devices. This is working fine and we recover the same Entitlements no mater the device the user Logs In.What we’re having problems is with subscription management since many actions (Upgrade, Downgrade, etc...) will only work from the device that did the original purchase as stated in the docs: Managing SubscriptionsA user can only manage their subscription on the platform it was purchased from.Having the same App Account logged in in two devices with different G

I’m trying to use the new beta paywall builder, but I get this error despite having offerings and products setup. 

RevenueCat Paywall Not Displaying Despite Proper Configuration in React Native App.Environment- react-native-purchases: 8.5.4- react-native-purchases-ui: 8.5.4- react-native: 0.74.5IssueI'm encountering an error message stating "offering Default has no configured paywall" despite having already:1. Created a paywall in the RevenueCat dashboard2. Linked it to the Default offering configuration3. Properly integrated react-native-purchases and react-native-purchases-uiWhat I've Done1. Created and configured a paywall in the RevenueCat dashboard2. Linked the paywall to the Default offering3. Installed and configured the latest versions of react-native-purchases and react-native-purchases-ui4. Verified my API keys and configurationCode Implementationimport { View } from

Hi everyone,I’ve integrated RevenueCat’s React Native package into our Expo-managed app, and I’m running into an issue getting everything working in Testflight. I’ve added the getOfferings() and purchasePackage() functions into our app and everything is working as expected when running the app locally, but the app is crashing as soon as it’s opened in TestFlight. To create our build for TestFlight, I’m usingeas build --platform iosLet me know if I’m missing anything or if you need anything from my side to help resolve this issue.Thanks!

Hi!Any plans on updating the Arrow dependency? I saw in the libs.versions.toml that it is set to 1.2.4 and since my project was relying on 2.0.1 I was getting build errors (iOS Simulator). Downgrading my project dependency to 1.2.4 helped.I am not sure if there is something in my build.gradle I can set to avoid this but the downgrade was not a big issue for me.BestCorey

I am trying to set up my app for iOS to use my subscriptions. All my subscriptions are in ‘ready for review’ state. I always get this error when trying to fetch my subscriptions. Also my test flight seems to have issues not sure if this may be related but when trying to install it says ‘app unavailable or doesnt exist’I have uploaded my relevant binary I have added subscription relevant metadata I have completed all the agreements (paid and free apps)My issues areConfiguration error when trying to find offerings (API still works i believe and connects to apple but cannot fetch the offerings) Test flight not working properly (not sure if related)flutter: PlatformException(23, 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

Hi,I’m currently trying to figure out how exactly I’m supposed to show promotional offers when using the pre-built paywall created in RevenueCat and displaying it in a iOS app.I can confirm that the promotional offer exists in the .storekit file. 

In my mobile application, users can create accounts.When logging into an account, I call logIn() in the RevenueCat SDK to set a custom app_user_id.When logging out, I call logOut(). Subscriptions are only available to authenticated users. Users can create groups within the app.When a user purchases a subscription, premium access is granted to all members of their group. To handle this, I have a table in the database that stores data about the active entitlement: PremiumTable:• id (autoIncrement primary key)• Purchase date• Expiration date• groupId – the ID of the group that received premium access• ownerUuid – the ID of the user who made the purchase (I’m unsure whether to store app_user_id or original_app_user_id here). The issue I’m facing:1. A user creates a group.2. He purchas

I’m working in React Native and using the RevenueCatUI.Paywall from react-native-purchases-ui. Specifically, I’m using RevenueCat for purchasing subscriptions through Apple. One thing I am seeing is that on my paywall when a purchase is being processed, there is no visual indicator that the payment is processing. So my users are able to continue to press the purchase button and are prompted again through the Apple dialogs to complete the purchase even though it is still processing. Is there a way to disable the purchase button while the payment is processing? Would this need to be done in my code or through the Paywall builder in the RevenueCat portal?

We have encountered an issue where the user alias is created with a delay by using the following API:In java: Purchases.getSharedInstance().logIn( … ) Below is the timeline of our user: Because the delay described above, the Webhook notified our backend service with an AnonymuosID, and we do know about the alias happened afterward. Thus our own service cannot link the user’s REAL user id with the purchases and subscriptions they made. This happens quite often on our side (more than 2% of our users are impacted!!!!), and it has caused a huge data loss already. Please fix this as soon as possible, or let us know, what can goes wrong with the integration.

I have done everything as requested, but I still get an error, what should I do?

I am having issues with the RC Web SDK.  I followed the instructions to get setup, and have successfully added products to Stripe & added to my existing mobile app offerings.  I can now view my paywall with products:Paywall successfully displays products from Stripe.  The product identified is in sync between Stripe & RevenueCatWhen I click “continue” for either product it results in an error:error code 16The console shows a 500 error to the RevenueCat API:POST https://api.revenuecat.com/

Greetings, I am facing this scenario in sandbox:-User A subscribes to Subscription Group A, it is a success. User A logs out. User B logs in (Purchases.login(NEW_APP_ID)) (same App Store account) User B subscribes to Subscription Group B, it is an error.ERROR:  Product purchase for '<Subscription Group B>' failed with error: PurchasesError(error: There is already another active subscriber using the same receipt., userInfo: ["NSUnderlyingError": Error Domain=RevenueCat.BackendErrorCode Code=7102 "There is already another active subscriber using the same receipt. User A is now subscribed to Subscription Group A and 

   The recommended template is used, the default language is English and can be displayed normally;1 However, when I added a new language: Simplified Chinese, and set it as the default, the error occurred in the display.2 If the default language is English and I adjust the test region to mainland China, Chinese UI are not displayed. The interface still shows in English.  

When trying to crete a paywall using the new paywall beta builder, i can’t get the price to be shown, it always display the variable.Tried it 2 times, with entitlements and offerings from scratch, same issue. Is this a known thing, or I’m doing something wrong?Bonus: gradients’s don’t look like they look live as whiting the builder

Hi, I’m trying to implement a subscription system with multiple tiers in a Unity cross-platform app.My concern is if there is a way where a user that has activated a subscription in a platform can upgrade the subscription from a different platform.I have also seen that there is a “managementUrl” that can be used to guide the user to the correct portal in case that he wants to manage a subscription, but I cannot find that url in the Unity Revenuecat SDK.

I have an app that offers annual, monthly and lifetime subscriptions. They all access the same ‘premium’ entitlement. If a new in-app user account is created and I restore purchases, I am able to successfully transfer entitlements between users, provided that the parent App Store Sandbox account is the same. I’m using web-hooks, so whenever a ‘transfer’ event is fired, I can update my database to make sure it is in-sync with RevenueCat. I remove any subscription information from the ‘transferred_from’ user, and apply it to the ‘transferred_to’ user. This is working perfectly for restoring monthly and annual subscriptions. But there are issues for lifetime purchases. Purchase a lifetime subscription using App Store account ‘x’.  Sign out of Sandbox account ‘x’, and sign into a completely new, unrelated Sandbox account ‘y’ with no purchase history.  Create a new in-app account using the new Sandbox account.

Let’s assume I change my Terms of Service.At app start, I prompt each user to accept the new terms. Users who reject the new terms shall be denied access to the app.How do I handle users with a paid auto-renewing subscription?Is there a way to cancel this subscription? Or prevent auto-renewal? It seems illegal to deny access to my app, but continue to charge them. Not sure if it’s relevant for this question, but I use react native.

I have a question about the syncPurchases function when I have two users of my app on one Apple Id. What happens when I call syncPurchases after then calling logIn with another App User Id? I know that the restorePurchases function throws an error that the receipt is already in use (if I set transfer behaviour to not transfer), but syncPurchases does not do that. In fact, it doesn't do anything and I don't know what exactly is going on. Is it safe to call syncPurchases when users sign in to the app? Not on every startup but while calling my backend sign in function.

Hi folks,In the {{ product.price_per_month }}/mo section in Paywall V2, the price data always stays in USD currency. even though I have localized paywall for countries, the currency section is not localized according to the prices and currencies in the countries. But when I select the subscription package in paywall and continue, the currency is localized without any problem in the last confirmation section. Where do you think the problem is coming from? If you want I can show you in detail with screenshots?(I am trying all process on real device in testflight).

I just made a change to my v2 Paywalls, and the badges that I have are no longer rendering their backgrounds.  This was working fine today, until I made and published an unrelated change, so it seems something may have broken today.  Everything looks fine when viewed in the online editor. Images below - the ‘33% OFF’ text is the badge - the text can barely be seen in the after, but the purple background is no longer there. Before: After: 

We're currently testing the new Paywall v2 feature in our React Native frontend. Everything works as expected except for the badges. We've tried all possible configurations—rectangle, pill, image background, colored background, etc.—but none seem to render correctly. The discrepancy between the Paywall Editor and the actual rendered Paywall on iOS persists.Has anyone else encountered this issue? Any insights or workarounds would be greatly appreciated!Current versions:"react-native-purchases": "^8.6.1","react-native-purchases-ui": "^8.6.1"“react-native”: "0.76.7" "expo": "52.0.36"Attached is a screenshot of different approaches in the Paywall Editor preview and how it gets displayed on device.

What could be the reason that I cannot access my Google Play subscription’s free trial offer from the SDK by calling `aPackage.product.subscriptionOptions?.freeTrial`? It is always null.This is a new subscription product which I created after reading through your migration guide from 5.x -6.x. It was suggested there that I should create new subscription products, so I did. I used to have two products, one annual and one monthly. I created a new single subscription with 2 base plans and an annual which has the free trial offer. With the old setup and 5.x version this worked, but now I cannot see the free trial in the new base plan at all. Any help is appreciated. All base plans and the new offer are active in Play console and the products have been added to RC packages. Also this annual base plan looks to be “backwards compatible”.This happens with the latest 6.3.0 version of the purchases SDK.