Learn and Share

Since I’ve been implementing in-app-purchases for my app the past days, I wanted to share a couple of things I’ve run into. Maybe they are of help to someone or can be used for further RC improvements.Google Play appends the app’s identifier or app name to the purchase title. It’s best practice to strip these, if you are using a dynamic paywall screen. The RC docs say that you need to have published an app bundle to a Closed Testing track e.g. Alpha in Google Play. I found that it is sufficient to use the unreviewed Internal Testing track. This allows for a setup where you have a package name for different environments e.g. staging and production. React Native: The RC debug logs are not replayed in the Javascript logs. You’ll have to view the device logs. Connect the device by USB Cable, then: iOS: Use Console.app to filter for Process: My App and Purchases Android: adb shell logcat | grep Purchases.I’ll update this, if I run into something else.

Hi all, Some feedback/thoughts on offer codes. To set the scene, we’ve recently set up a b2b partnership and are using 12 month offer codes to provide their customers with access to our app. Offer code’s aren’t included in integration data, i.e. GCP exports and Facebook. Nor is there a way to filter for offer codes in customer lists. In order to track code consumption, we’ve had to set up web hooks, cloud functions and a custom dashboard. Not a massive issue, but the reason we’re paying for RC is to make these things easier.  Offer codes are marked as trials. For us, this makes no sense - we’re expecting (/hoping) to have thousands of these codes used. It’s going to boost our active trials rate by 12 months each, thus rendering the dashboard ‘active trials’ rate useless. Again, there’s no way to filter so we can’t get true active trials in the customer list’s either.  Lastly, I'd like a way to see on the customer profile if they’ve used an offer code.  Thanks for reading, hopefully the

As a developer, you probably spent time looking through the REST API endpoints to keep subscription status in sync with your backend, update subscriber attributes server side, etc.We would love to hear from you:Is there something you’d like to be able to do through the API that you can’t currently do? Are there any fields you’d like to see that aren’t currently returned from an endpoint?Thank you!

Hey RevenueCat Community! 👋I wanted to share a blog post I wrote recently about how you can use Entitlements for more than just in-app purchases. Since Entitlements can be granted manually as promotionals via the dashboard and REST API, you can actually use Entitlements as generic feature flags - all without being connected to any in-app purchase products at all.A good use case might be setting up beta features (maybe for only long-term paying customers, for example) and granting access to those beta features with an ‘empty’ entitlement. You could build this out as custom as you’d like - you could manually opt users into your beta from the RevenueCat dashboard, or even build an automated system from your own backend to let users opt-in to the beta themselves, all by tying into our promotionals API.I detail the process in the blog post, but would welcome any questions or comments!You can read the blog post here. 

The SwiftUi example app on this page https://docs.revenuecat.com/docs/sample-apps requires xcode 13 because of AsyncStream. Is there a SwiftUI example app that works in xcode 12.5?

Hi all,I’ve got some subscriptions defined in Google PlayStore console, but they where to test subscriptions a while back. Now we don’t use them within RevenueCat. But I can’t delete them in the PlayStore console (asked Google Support, but they told me that we can’t remove active products) These old products are never sold because we are stil in develop phase. My question now is, are these products every visible by customers? I don’t use them in RevenueCat and are not showing them in our app on the PayWall. But maybe they are somehow visible somewhere else? And even switch to or able to buy by customers? So is it safe to leave them in de Console (otherwise I have to delete the app in de PlayStore and make a new packageID with all the extra work)What do you guys think? Any advise? PlayStore Console: 

Hi RevCat community  Ok this might be bit of a strange question, but I've been inspired by what Duolingo have done with their recently announced family plan, where you can invite up to 5 others and only a single subscription is required (annual only, at higher price, which is smart).  I’m assuming with Aliases that RevenueCat would support a user inviting another user and that user not having to go through payment process as they tied to the original user (invitee), and if that original user churned or lost their entitlement, that all aliases on that same ‘purchase record’ would also lose access?  Has anyone else seen apps do shared subscriptions, beyond what apple offers with Family Plans. I know Spotify do duo plan. 

Hey,because of how our subscriptions work in general, we have decided to not use the RevenueCat SDK to create purchases, but announce them to our own API, which will in turn make an HTTP call to RecenueCat’s /receipts route, passing the neccessary data.Arguably the most important piece of data is the fetch_token from the app store.The problem arises when we’re trying to run automated integration tests via our CI server - without doing an actual purchase on an actual hardware device, we won’t have a valid fetch token, so the API will always answer with the (reasonable) error: "The receipt is not valid.".So my question is two-fold:is there any way to simulate a purchase for testing purposes? how to others solve the testing issue?Or is our use-case really this particularly rare?Regards,Markus 

There are a variety of things you may want to test about your iOS products: different pricing, free trial durations, introductory offers, and more. The RevenueCat Experiments feature will automatically divide your new customers evenly into two groups, where each group will have a separate “current” Offering. For more information about this feature: https://docs.revenuecat.com/docs/experiments  Bear in mind that this feature is currently in Beta and A/B testing is available on iOS only. When deciding to make an Offering current, double check that it works on all platforms supported by your app. This means while the experiment Offering will be available for customers on other platforms, the data is only calculated for iOS purchases. How often do Experiment results get computed?The LTV model is ran daily, typically every 24 hours after you first initiated the experiment.  What to do when seeing the 'Data will show in 24 hours' message after 24 hours?If it has been well over 24 hours since

Hi everyone,I’m looking to figure out a way to reset or extend a users free trial. At present, we have successfully set up an In-App Subscription on both iOS and Android with a one week free trial. We then hope to send the user a notification or email when their trial is almost over prompting them to refer a friend to the app, which they will be rewarded for by extending the trial for another week.The refer all mechanisms is fairly easy to do with deep links, the question is once we have detected that a user has successfully referred a friend, what is the best way to extend their trial? Additionally, I’m still trying to work out how this plays with Apple’s terms of service - it seems to be within the rules but any thoughts would be appreciated.Thanks everyone! 

When tracking webhook events and also using the API, there are data discrepancies how field values are presented or formatted. One such case is the Subscription#period_type. In a webhook event the value is uppercase but in the api it’s all lowercase. Another is the use of both millisecond timestamps and ISO 8601 datetime string. This makes for very awkward handling of RevenueCat’s data in our codebase. Granted, I realize this is not easy to reconcile in existing APIs but in the future I would hope the company can adopt standards for these fields that they stick to across their platform.  

 We’ve had a few reports about the offerings:completion: method on iOS not calling its corresponding completion block, specifically on iOS 15.In Flutter, React-Native, Cordova/Ionic and Unity, this method is called getOfferings. If you’re using async / await syntax, this will manifest as the await call not completing.  This seems to be a bug in iOS 15, where the underlying SKProductsRequest made by the SDK doesn’t call its completion handlers (in the form of delegates).  Once the bug manifests, it might prevent you from making purchases of other, regular items in Production, like downloading a new app from the App Store, even if you uninstall your app, until you reboot the device.The biggest telltale sign of this bug happening is finding the following line in the debug logs on iOS 15, but having everything work correctly on iOS 14:[BackgroundTask] Background Task 12 ("SKProductsRequest"), was created over 30 seconds ago. In applications running in the background, this creates a risk of

Hey everyone, I’m curious what folks’ approach is regarding the Epic-vs-Apple decision? Is anyone making plans already to explore linking out of the app to a web paywall? Or are you going to wait and see how things turn out?At RevenueCat, we’re currently playing around with a few options to support potential use cases (of course, pending what exactly will and won’t be allowed), and I’d love to get a feeling for the level of interest in the topic.JensHead of Product @ RevenueCat 

Customer Lists are a powerful way to organize and export your customers based on certain app interactions or important characteristics such as their current subscription status.When you export customers, RevenueCat creates a compressed CSV (CSV stands for comma-separated values) with the filtered customers as well as their attributes. The compressed CSV uses the gzip compression algorithm with a .gz extension. Decompressing on macOSFor most exports, using the default macOS Archive Utility will be enough to decompress the exported file. Occasionally, due to a bug in Archive Utility, the file may fail to decompress with the error message ‘Error 79 - Inappropriate file type or format’.When this happens, you have a few options:Use the built-in Terminal to decompress the file with the following command:gzip -d /path/to/file.gzUse a third party tool like Keka to decompress the file Viewing the data in a spreadsheetOnce the file is decompressed, you can import it into spreadsheet software lik

We change our prices time to time on store and when  the prices increase and customer cancel and resubscribe, they usually email us through support.Is there a way we can modify the price on revenue-cat for specifically for disappointed customers. How can we compensate these customers with some kind of offering? 

Also known in RevenueCat as the STORE_PROBLEM error, this error can occur when purchasing a product and indicates there was an issue verifying the purchase with the App Store or Google Play Store. The error can either come directly from Apple or Google’s libraries, or from RevenueCat’s backend when attempting to verify the receipt. Why does this error occur?The STORE_PROBLEM error occurs more commonly in sandbox than production, and can result from different causes depending on the store. Usually, it means there was a problem connecting to the store at the time of purchase—such as the store’s servers were down, or the user’s network connection failed, so the purchase could not be verified and completed.  RevenueCat will forward the underlying error, or the exact cause for the error, along with the STORE_PROBLEM error. Here is a list of possible causes from each store:Apple SKErrorUnknown. An unknown or unexpected error occurred. A “catch-all” error that may point to a problem with the

What to do when a customer says they purchased the product but didn't gain access? If utilizing RevenueCat’s Entitlement system, you should first confirm that the product is attached to the correct Entitlement.  If Entitlements are set up correctly, your end customer’s purchases may have to be re-synced with RevenueCat servers. This can be done either with a user-facing button in the app triggering the restore method or through the REST API with the `is_restore` field set to `true`. Note that restoring through the REST API requires your team to collect the customer’s fetch token at the time of purchase. For iOS, this is the base64 encoded receipt file and for Android this is the purchase token. You can read more about restoring either in RevenueCat’s documentation or in the following community post: https://community.revenuecat.com/featured-articles-55/do-i-need-a-restore-purchases-button-391  If you notice that your customer’s purchase is not populating in the RevenueCat dashboard,

Hey,I'm looking at my churn dashboard and I'm wondering wether our monthly churn and our annual renewal rates are good or bad compared to most consumer apps. I guess there is probably a pretty big variance depending on pricing and type of app, but it would still be nice to hear some data points from other consumer apps. When googling I find mostly data points from B2B SaaS which is a totally different animal.Can anyone share benchmark or a few links that explore this?  Cheers,Florian

RevenueCat proudly helps create an easy way to keep track of all your in-app transactions. However, although we manage your purchases, we don't process the payments for your subscriptions and non-renewing products.   The differences are best explained by understanding how RevenueCat interacts during the purchasing phase of a customer buying a subscription or non-renewing product.   When a user goes to your paywall, the SDK uses the product IDs from your current offering and retrieves the product information from the respective stores ( Apple/Google/Stripe). When the user selects a product to purchase, the SDK gets the product ID to send it to the store to purchase The store then processes the payment (charges the user via their payment option) and adds this product to the customer's receipt.  When the customer's receipt changes, RevenueCat has listeners that update the `PurchaserInfo` object (allowing customers to get access to the product/feature they purchased) and updates our

Hi! We put together a walkthrough of the dashboard on the RevenueCat Youtube channel. This may be helpful if you’re already up-and-running and want to learn more about the dashboard, or if you’re evaluating RevenueCat and want to get an idea of what you can expect. Let me know if this is useful and if there’s other content you’d like to see!  

Is there a way to display a specific product on the sales screen?The sales screen in my app is being controlled through my backend,with the way that the screen is built it’s important that i’ll have control over the specific In-App Purchase that’s being fetched.so if i can use the package identifier to fetch the product that would be great!unfortunately so far i haven't found this option or code in the docs...

If you don't have or don't want a full website, it can be unclear on how to proceed with integrating Stripe payments alongside your existing mobile in-app purchases. This sample project demonstrates how to use Stripe Checkout and webhooks to send purchase data to RevenueCat. Once published, you’ll be able to share individual links with users that will automatically redirect to Stripe, then send the receipt back to RevenueCat once the purchase is completed.It’s recommended that you know the basics about RevenueCat and Stripe before continuing with this project. Example Use-Cases Win-back email campaigns Send individual links to expired users to re-subscribe using Stripe checkout. In this case, you’ll need to have app user IDs and email addresses paired (typically from your own auth system).   SetupThe easiest way to use this sample is by deploying to Heroku instantly with the button below.Or you can deploy by clicking this link. The following environment variables should be set bef

Would love option to save a filter - e.g. longer free trial users, price tier 2. etc. We have multiple offerings, prices, and free trial tiers in App Store listings, and manually creating filters by selecting all the different offerings that fall into each category is a pain. 

I expected to logo to link to RC home page, just like docs.revenurcat.com,  instead it links to forum home page.

Congratulations to all you revenue cats! I’m looking forward to this new forum.  I especially appreciated the details about when to post versus when to contact support 1 on 1.