Get Help

Hello! I have a subscription with grace period 14 days, if this subscription is expired and now on grace period i get this JSON: [app1800_sub_personal_monthly] => Array ( [billing_issues_detected_at] => 2021-08-27T08:29:54Z [expires_date] => 2021-09-12T08:29:50Z [grace_period_expires_date] => 2021-09-12T08:29:50Z [is_sandbox] => [original_purchase_date] => 2021-07-27T08:29:52Z [ownership_type] => PURCHASED [period_type] => normal [purchase_date] => 2021-07-27T08:29:50Z [store] => app_store [unsubscribe_detected_at] => ) Not so long ago, these fields were different and I use field “expires_date” to understand that the subscription expired and he now in the grace period

Hi guys! I do subscriptions for my app. A have 2 entitlements (Standard, Premium). And I have 3 periods for every entitlement (1 month, 6 month, 1 year). There are 6 products at all. As I understand, a can't use default packages for this, and I need to create custom package for every product? For example: place “1 month standard” and “1 month advanced” in to default MONTHLY package. Because now, I created 6 custom packages. Am I doing everything right? Can you give me some details about this please.

This is the apple reason We noticed that your Kids Category app includes analytics, advertising and collects, transmits, or has the ability to share personal information or device information with third parties. Specifically: - Your app includes third-party analytics or third-party advertising with the ability to collect, transmit or share identifiable information, including, for example, IDFA. We found that your app references the ASIdentifierManager API, which provides access to a user's IDFA, in the following location(s) in your binary: • /System/Library/Frameworks/AdSupport.framework/AdSupport It would be appropriate to remove all instances of “ASIdentifierManager” from your app, even if they are not utilized in your app's functionality. after looking in my app directory and looking for any Ads support framework/library I found that Revenuecat support Ads how can i disable collecting idfa

The question is for an iOS app - My setup is that I am using my backend to give access to “Pro” features through the API and I am using Revenue cat to process the payment. Sign up comes after the purchase is made and it is optional to the user. I want to understand how I should give access from the backend to users who are making a purchase but do not sign up? This approach should also work when the user comes back and restores purchase after uninstalling the app.

Hello, I’m testing out revenuecat and tried sending receipt data from the iOS app store for a couple of customers using the receipts endpoint. Revenuecat showed the transactions for the imported users correctly but the total spent for the imported customers shows as zero. I even tried adding the “price” property on the REST request to no avail. Know what might be up? I need to migrate data for a few 1000 customers and so its critical that it work correctly. Thanks

I have a problem with my app. As long as I installed the app to my iPhone with Xcode, everything was working (Apart from the fact that having configured the products from the Xcode file and not from the App Store, in the end the purchase failed). Now that I uploaded the app to testflight, when purchasing a product I can’t even see the iOS purchase popup. Could It be the fact that there is no longer the Xcode purchases configuration file and that the one on the App Store hasn’t been approved yet? I can I fix that?

Google Play sent a reminder: “Starting on August 2, 2021, all new apps must use Billing Library version 3 or newer. By November 1, 2021, all updates to existing apps must use Billing Library version 3 or newer.” Does RevenueCat already use the Billing Library v3 or is there anything we would need to do to make sure the transition is smooth? Thanks!

I am trying to look at when users start a free trial cancel the subscription. I exported a customer list from RevenueCat and have been looking at the data in Excel. In Excel the columns that I am looking at are trial_opt_out_at and trial_start_at. Does anyone know how to convert the values in these columns to dates from the numbers that they are set. Currently the values in these columns look like - 1629693003000.

HI there! I’m hoping you will able to help. Here is the error Item Unavailable, id the correct, in the google account all is also ok. It’s closed testing, and also testers, devices and so on is ok. The app got prices from the cat, but still it doesn’t work. We also can’t make a test purchase via cat and didn’t seen any tries in the sandbox dashboard. Maybe someone know what to do next Thanks in advance

We’re currently migrating to RevenueCat. In the past we had many products on Android/iOS mainly for pricing tests where user subscribed to. We don’t offer these products anymore but of course these users should still have access to the PRO features. Do we still need to add all these legacy products (subscriptions) in RevenueCat too, so we can find out they have a valid subscription? Or do we only have to set up the products that we actually want offer in the app? And will this affect analytics somehow when products are not added? Best Janis

Here is the Setup: 1. App is a race car game where user has different cars they build. 2. User can buy new parts for each of their cars. 3. Upgrades are onetime, non-expiring purchases. 4. One upgrade is for one car only. 4.a. if user wants to upgrade tires for two cars...the user makes two purchases of product ID "nrp_tire_lvl3_199" User Scenario: 1. User is managing two cars (A, B, and C). 2. User wants to upgrade tires on car B. 3. User makes purchase of "nrp_tire_lvl3_199" 4. Our server receives the Web hook notification of the purchase. ??? How can we tell the server which of the User's cars to apply the upgrade to? How can the Server know to apply the upgrade to Car B?

Ok, so I read and think I understand how the Restore Settings work, but have some further clarification settings. We’re in the process of migrating to a new backend where all users will need to sign up again with a new system where they will get user IDs. These user IDs are the ones that will not be recycled changed. We don’t want a scenario where users can log out of their new accounts, create a new one, restore subscriptions (mint a new subscriber), then give those credentials to someone else or what have you. That’s why we want to have the Block Restores enabled, but we aren’t sure how to handle the migration process from the old version of our app to the new one. What I was thinking - first, we don’t enable this Block Restores Setting and let everyone migrate to the new login system, restore purchases if they need. Our old version is also using the old SDK and we aren’t calling reset user ID anywhere - what will happen when we upgrade to the new SDK and haven’t called login yet? Wi

We have enabled a/b experiments and are testing what experiment performs best. We also have analytics around what SKUs users are seeing. We’ve noticed that our default variant is seen 70% of the time and variant B 30%. It’s hard to tell if this is a RevenueCat issue or whether our users are that skewed in terms of who is looking at the paywall. Any ideas on why we would see such an uneven distribution?

In the list of possible integrations I see Braze but not Iterable. What is currently the best way to send Revenuecat events to Iterable?

Hi! As this image shows, the customer started a trial and seems to have converted three times. Only 1 showing a CAD value. Then 2 times opted out of renewal after that. I was wondering what is going on?

Hi there! I have a question about RevenueCat logIn (and Blocking Transfers) as introduced in: Suppose this is how my iOS/Node app is designed to work: I have a user database and each user has a unique record and id. We require users to sign up with email and password before they’re shown the purchase flow. We use their unique database record id as the RevenueCat appUserID when purchasing a package. Our RevenueCat app is set up to Block Transfers. If I understand this correctly, this means that as long as a user logs in with the right appUserID, they should have the appropriate entitlement everywhere. That includes different devices on iOS, Android, and web that log in with the right appUserID and use the RevenueCat offerings API. Additionally, if the an entitled user signs out, and someone else logs in from the same device (different appUserID), RevenueCat will pull in THEIR entitlement, which may or may not exist, and would trigger their own Purchase flow if needed. In the other words

We’ve recently started to use mParticle and like the seamless integration of events from RevenueCat to mParticle. There is however something missing. We want to know per user what there current subscription status is (unsubscribed, trial, subscribed). Right now we would need to implement a service that would ingest this data. Is there another way to get this directly into mParticle? Are there any plans to add this functionality to the integration? Thanks, Wolfgang

We have setup the mParticle Integration to forward subscription event data to mParticle. Currently this fails for most of `trial_started` events originating on Android. Other events are reported successfully. Steps to reproduce: Opening our App in the Dashboard Select Analytics > mParticle from the left Scroll down to “Recent Events” Expected All requests are successful and return a status code of 2xx. Actual `trial_started` events originating on Android fail with a 400 status code. This is impacting our analytics stack heavily and a fast fix is highly appreciated. If you need further input from us let us know.

Hi, Do I need to implement anything in the RevenueCat setup or within my app to handle the grace period if I enable it?

Hi guys, how can I cancel an Apple subscription for existing users? We are switching to free business model and I need to do it somehow. what is the easiest way? Best regards, Alex

I’ve got a question about values that are dumped out via the S3 ETL, and how it relates to taxation. Suppose we have a subscription with a price set as $10 USD in the Play store. The Play Store seems to set regional prices based on current exchange rates and local taxes. Say, for example, that same $10 USD now shows in Australia as $15.49 AUS (the conversion rate, plus 10% tax, plus “country-specific pricing patterns”, according to Google). If we had a purchase go through in Australia, what can we expect to see in the data on S3, specifically for price_in_purchased_currency? I’d expect the price_in_usd to be 10.00, and the purchased_currency be AUS, but what will the price_in_purchased_currency be? Will the price_in_purchased_currency be the final price that was charged to the customer, or will it exclude the tax? Is the behaviour the same for purchases made through the App Store? We’re trying to sort a few things out before we have actual purchases flowing through. Unfortunately testi

Hello, I’m currently integrating RevenueCat and making test purchases with and without StoreKit Configuration file using a sandbox account. But I noticed that these sandbox events are being sent to my integration partners. My MixPanel and AppsFlyer are reporting these events as revenue which I do not want, as I expect to do much more test buys in the future and this will mess up my OKRs. Is there a way to optionally disable these web hooks and integrations for sandbox events?

I’m receiving the following error message and I would like to check other situations where I can handle such errors, but I couldn’t find anything, no article nor documentation. { "code": 7242, "message": "No promotional entitlements to revoke for this subscriber."} Is there a way to receive all possible error codes and their meaning so that I can better handle it when communicating with the REST API and avoid unnecessary errors?

As a product designer, I’m finding a bit difficult to get evidence and examples online of the checkout process in order to create the necessary user flows for the project I’m currently working on… My team is currently considering using Apple Pay, Stripe and Google Pay as payment alternatives for the Flutter app we are building, and I would like to see the checkout process sequence, examples and any specific UI styling needed in order to provide everything the dev team needs to build it into the app. It would be good to have some references and/or resources for designers that are not GitHub experts or that can’t create the sample project by themselves. Thanks!

On one of my devices, I’m consistently getting nil in PurchaserInfo for both originalApplicationVersion and originalPurchaseDate. Based on what I’ve read in the docs and elsewhere, I thought in the sandbox I should always expect originalApplicationVersion to be “1.0” and originalPurchaseDate to be 2013-08-01. I did notice that in the header for both of these properties, it says: @note This can be nil, see -[RCPurchases restoreTransactionsForAppStore:] But that function doesn’t exist. This seems like pretty odd behavior, since it’s only happening on one of my devices, both in TestFlight and running through Xcode. I can’t confirm it easily, but I think one of my TestFlight testers is experiencing it too. I also tried a few different versions of the SDK and the issue was the same. Purchases iOS 3.12.3 iOS 14.7.1