Recently active topics

I havé the same problem can you help me this is my email : bilalneufcink@gmail.com

I have`Purchases.shared.attribution.enableAdServicesAttributionTokenCollection()`which according to https://www.revenuecat.com/docs/integrations/attribution/apple-search-ads should give me the following fields:https://cln.sh/41P1JJ7THowever these are the fields that I see:https://cln.sh/dPCvFb77 I have used ASA Basic in the past, but have been using advanced for months.Is there anything else that I’m missing?

Google released new version of Next Gen AdMob SDK. Does RevenueCat support that?

Could you please provide an update on support for monthly subscriptions with a 12-month commitment in the Apple App Store?The iOS SDK 5.76.0 appears to include some initial support. However, it does not yet seem possible to create or configure subscriptions with a monthly billing plan in the admin interface.Do you have an estimated timeline for when full support will be available?

Hi RevenueCat community,I'm working on a React Native app and running into a persistent issue with anonymous-to-identified user merging. Would love some help figuring out if this is expected behavior or something I'm doing wrong.Background & Initial SetupMy app originally required registration before any in-app purchase could be made. After an App Store rejection (purchases shouldn't require registration), I updated the flow to allow anonymous purchases first, with registration happening later.Restore Behavior: Transfer to new App User IDThe Flow I Want1. User launches app → anonymous purchase made (no account yet)2. User registers/signs in → anonymous ID merges with their account ✅ (this works fine)3. Subscription expires → user signs out4. User relaunches app → makes a new anonymous purchase5. User signs back into their existing account → new purchase should merge/transfer to their accountWhat's Actually HappeningStep 5 fails. After signing back in, the subscription shows as inac

Hi team,I am trying to understand why RevenueCat completely missed/dropped a successful Stripe payment recapture for a user on May 21st. The event simply does not exist on the RC timeline, even though Stripe successfully charged them.Here is the exact comparison of both timelines:Stripe Payment History: May 7, 1:01 PM: $0.99 (Subscription creation) - Succeeded May 14: Initial $19.99 billing cycle due (Failed) May 18, 8:05 AM: $19.99 (Payment Recaptured) - Succeeded May 21: Initial $19.99 billing cycle due (Failed) May 31, 11:03 PM: $19.99 (Payment Recaptured) - Succeeded May 28: Initial $19.99 billing cycle due (failed) Jun 1, 7:03 AM: $19.99 (Payment Recaptured) - Succeeded RevenueCat Customer Event History: 2026-05-28, 8:01 PM: Renewed subscription ($19.99) (Matches Stripe's May 31/Jun 1 block) 2026-05-21, 9:03 PM: Cancelled due to a billing error 2026-05-21, 9:03 PM: Had a billing issue 2026-05-14, 9:05 PM: Cancelled due to a billing error 2026-05-14, 9:05

Hi! We’re looking into moving a multitiered model and I’m currently designing some paywalls for this.I’d like to use the Footer component to be able to have the purchase button always visible at the bottom with the plan length choice on top of it, but I’m unable to get the selected tab to effect the contents of the footer.Is there any way to make this work currently?

Hey, does your roadmap have Accessibility improvements or configurability on the roadmap?We have a need to fulfill the requirements of European Accessibility Act (Directive (EU) 2019/882) and we have noticed that currently the Paywalls don’t seem to offer good support for accessibility.Recently the ability to disable font scaling in Paywalls, did fix one of our issues. Otherwise we have been able to work around it by adjusting our paywall and doing small hacks and adjustments to them in order to improve the Accessibility.So I was wondering if you have Accessibility improvements coming in the roadmap and when might these improvements be scheduled?

Hey, we ran into small issue when testing our integration. If user cancels the current subscription from Play Store, it gets to a state where it is “isActive = true” and “willRenew = false”.It seems the Paywall doesn’t check for the “willRenew” state when deciding to trigger the upgrade/downgrade flow when user tries to purchase the same subscription from Paywall. Instead of dealing it as a new purchase the Paywall seems to attempt to do a Upgrade/Downgrade to that product. Which then errors out from play store.I would expect the Paywall to allow user to renew the current subscription, instead of attempting to do a upgrade to the same purchase and then erroring out.In this flow the Upgrade/Downgrade to an other product did work as expected, so no issues with those. 🤖‼️ BillingWrapper purchases failed to update: DebugMessage: Account identifiers don't match the previous subscription.. ErrorCode: DEVELOPER_ERROR. SubResponseCode: NO_APPLICABLE_SUB_RESPONSE_CODE. No purchases received🤖‼

Coreball game is the main center ball that keeps rotating during gameplay. It acts as the base where all other balls or pins must be attached. The player’s main goal is to shoot pins one by one so they stick to the core ball without touching any existing pins. As levels increase, the speed and direction of the core ball rotation change, making the game more challenging. Core Ball represents balance, timing, and patience, because one wrong move can end the level instantly.

After a DEFERRED replacement (A → B), Google Play marks the active subscription as “Plan change”, but RevenueCat SDK for Android doesn’t seem to expose this state where the active subscription is pending a plan change.Could this be exposed from the RevenueCat SDK for the active subscriptions? I don’t seem to get any information from the RevenueCat Android SDK that the plan is about to change and to where the plan is going to change to. The backend does receive the “PRODUCT_CHANGE” webhook, but client side isn’t able to access the same information.Seems to me also that the Paywall’s ProductChangeCalculator  purchases-android/ui/revenuecatui/src/main/kotlin/com/revenuecat/purchases/ui/revenuecatui/data/ProductChangeCalculator.kt at main · RevenueCat/purchases-android is not doing any logic to handle the pending case, so if you attempt a second downgrade from the Paywall while the previous is pending you get.“Paywall purchase error: One or more of the arguments provided are invalid.”, whi

When I tried adding revenuecat  into base44 I am getting several errors and the above image is one of them. How do I make revenuecat  for in app purchases as apple does not allow stripe and Base44 only integrates with stripe. What steps do I need to do to integrate it into base44 to accept payments as I know I’m not doing something right. Could someone give me a prompt for base44 to integrate revenuecat. 

Hey everyone,I came across this previous discussion about Apple’s new “monthly subscriptions with a 12-month commitment” feature:https://community.revenuecat.com/sdks-51/monthly-subscriptions-with-a-12-month-commitment-7629?tid=7629&fid=51Since that topic is now closed, I wanted to ask about the current state of support on the RevenueCat side.If we enable this billing option in App Store Connect for an existing yearly subscription product, should everything continue working normally in RevenueCat without any additional changes?Main things I’m wondering about:- Will entitlements continue behaving normally?- Will RevenueCat webhooks continue firing the same way?- Any differences in renewals / expiration handling?- Is there any way to detect this billing model via SDK or webhooks?- Any known issues or edge cases before enabling it in production?We rely pretty heavily on RevenueCat webhooks + entitlement logic, so I just want to make sure enabling this on Apple’s side won’t unexpectedl

Hi everyone,I’ve created my app in App Store Connect and set up both an in-app purchase and a subscription. However, the In-App Purchase section does not appear on the app version page, so I can’t attach the products for review.At the moment, both products show Developer Action Required, but inside each item everything seems filled out and ready for review. I’ve also confirmed that the tax forms, business forms, bank details, and other agreements are accepted.The app itself got accepted, but the in-app purchase/subscription was returned, so I’m trying to finalize the deployment and resubmit everything correctly.I already tried checking the app version and submission flow, but the IAP/subscription section still doesn’t show up. Has anyone run into this before? What usually needs to be fixed so the section becomes visible and I can submit the app together with the IAP/subscription for review?Thanks in advance.

I’m building a web-based TV app where users scan a QR code on the TV to complete payment on their phone. I’m using purchases-js and calling getOfferings() to display products for the current offering.However, the packages array is coming back empty, even though I’ve created a Stripe product for each package under each offering.I noticed that when I add a Web Billing product, it shows up correctly in the offerings, but the Stripe products do not appear.Is this expected behavior for the Web SDK, or am I missing a required configuration step for Stripe products to be available through getOfferings() in a web application?

Hello!We’ve setup a Web Purchase Link for an offering using RC Billing. One of the packages supports a free trial period. The link support promo codes. We notice there’s some conflicting information on the page about how much the user will pay after the trial ends when using a promo code. In the example below, we’re using a 100% off promo code. On the left side it’s clear that after the trial ends, the user will pay $0; however, on the right side there’s disclaimer text explaining that after the trial ends, the user will pay the full price of $129. This has led to some questions and confusion. Is there a way to ensure the disclaimer text updates to handle the promo code? Thank you for your help!

Hello RevenueCat Support Team,We are experiencing an issue with the getOfferings() function in our iOS app (Swift/SwiftUI).Details:In our RevenueCat dashboard, we have two packages within the same Offering:Weekly package (subscription) Yearly package (subscription)Both products are properly registered and published in the App Store, and we have confirmed their "Approved" status in both App Store Connect and RevenueCat.However, when getOfferings() is called in production (App Store build), only the weekly package is returned. The yearly package is missing from the offerings response.We have confirmed that:Store product IDs match exactly with RevenueCat product IDs Entitlements are correctly linked to both products The Offering includes both packages Both products show "Approved" status in App Store Connect The issue does not reproduce in sandbox (debug builds or TestFlight) , both packages return correctly The issue does not reproduce when Xcode is attached to the production build Waiti

Hi there, for context I’ve already sent a support ticket regarding this issue but wanted to get better visibility here as it’s a pressing matter for us to be able to experiment in this manner. Our Setup:SDK: react-native-purchases 9.15.2 (iOS SDK 5.67.1)Platform: iOS (React Native / Expo)Placements: 9 placements defined in-app (e.g., x, x_upsell, y_upsell, etc.)Targeting Rule: One live catch-all rule (no audience conditions) that maps each placement to a specific control offering. The "for all other cases" fallback is set to No Offering, with default set for "when not using Placements."Experiment config: Paywall design experiment with all 9 placements specified (different offering only at the x placement, all others kept the same as the targeting rule). Fallback offerings A/B are set. Targeting by app_version >= X.X.X. Enrollment: 100%. The Problem:Experiments using new_and_existing enrollment mode do not actually apply to users, even when the user clearly matches the targeting cond

It would be helpful for the SDK to allow apps to submit custom Anonymous App User IDs with their Configure() calls. These would be used instead of generating a $RCAnon app user ID, but would still be Aliased if/when the user subsequently signs in and the app calls .login().In my case, my app can provide a more persistent anonymous identifier than what $RCAnon accomplishes, which leads to a better user experience, but we refrain from doing so because we get undesirable Transfer Purchases to New App User ID behavior instead of the aliasing that happens with $RCAnon.It we could get that aliasing behavior with a custom AppUserID, we would supply our persistent anonymous identifier and the end-user would have a better experience.

Does RevenueCat Support Purchases in (X) Country?RevenueCat supports subscriptions and in-app purchases for any country that is supported by the app stores (Apple, Google, Amazon) and Stripe. What if my country is only partially supported?If you want to support in-app purchases in Bermuda, for example, RevenueCat will work for all users in Bermuda, and they can make purchases in the Apple App Store and Amazon Appstore, but not in the Google Play Store.If a Bermudian user purchases a subscription on an Apple device, they can still access their subscription on an Android device if you properly support cross-platform usage of RevenueCat. Stripe purchasesStripe works differently from the app stores. If you as a developer have a bank account in a supported country, then you can collect payments globally. So, in the table below, if a country does not have a √ for Stripe, that does not mean you cannot collect Stripe payments from users in that country. It simply means your bank account/busine

Seems the Android Paywalls show Material3 Alert Dialog. Are there plans to make these customizable or disable them so we can show the errors in style that matches the rest of our App? Only way we have found to do this, is to resume(false) in onPurchasePackageInitiated and then taking over the entire purchase flow, but we would prefer to let the Paywall do the work.Even if we keep the default dialogs, their body seems to use non-localized Strings for the error message. Which also makes them bad for non-english users. https://github.com/RevenueCat/purchases-android/blob/de4475520fb0353daddbae2fccf2f402332688ea/purchases/src/main/kotlin/com/revenuecat/purchases/errors.kt#L56

Hi, Any update on changing the timestamps you’re sending to Customer.io via the direct integration from ISO to Epoch? I asked in this post before: Customer.io doesn’t run on ISO, they use Epoch. As it stands, this integration isn’t very useful (the most important piece of data that I need in Customerio is the user’s expiration date!).

I am building an iOS app using: SwiftUI Firebase backend RevenueCat Apple In-App Purchases The goal of the referral system is:“Invite a friend, they get 50% off a premium lifetime purchase, and once they successfully purchase, you also get access to the same 50% discounted purchase.”Importantly: users NEVER get premium access directly from a custom code premium access is ALWAYS granted through Apple IAP / RevenueCat entitlement the question is mainly about the referral mechanics and App Store guidelines compliance Scenario A — Apple-native offer codes Use Apple Offer Codes generated through App Store Connect API Store/generated codes are managed on my backend User A invites User B User B receives an Apple offer code for 50% off User B redeems through Apple redemption flow and purchases through normal Apple IAP RevenueCat webhook confirms purchase Backend then unlocks another Apple offer code for User A User A can then redeem their own 50% Apple offer code Scenar

I have an introductory offer applied to a one time purchase on the google play console with legacy compatibility checked. Whilst the UI in the app shows the discounted price when I click to purchase it and the google billing bottom sheet surfaces, its showing the full price. Is this a gap in your SDK to support introductory offers for one time products?

13