Get Help

When integrations aren't working as expected, debugging can be challenging. This guide is designed to walk you through the steps you should take to identify what could be going wrong, and steps you can take to resolve any issues. Identifying the issueWhen debugging integrations, we usually hear about three categories of issues:No events are being sent from RevenueCat into third-party Only some events are being sent from RevenueCat into third-party All events appear to be sent, but the data in third-party does not match RevenueCatWe'll dig into each of these categories further in the sections below. Check that events are being sentThe first thing to check is if any events are being sent from RevenueCat into the third-party. This is easy to check in the RevenueCat dashboard under the integration settings for your app.Below every integration configuration, y

Sometimes a user will say they've made a purchase but they don't seem to have access to the content in RevenueCat. What gives? There are several reasons why that might happen, and this article will walk you through what you can do to troubleshoot.If there's no purchases showing in the RevenueCat dashboard it means that either no receipt was sent by that App User ID, or the receipt that was sent didn't contain any purchases. In this case you should:Ask the user to Restore Purchases (or someway trigger the restoreTransactions() SDK method). Restoring will re-sync the current receipt on the device with RevenueCat, and unlock any associated content. There are cases, such as network connectivity failures, where the receipt may never make it to RevenueCat after a purchase. There is automatic retry logic built into the SDK to handle these

How often is data updated in the RevenueCat dashboard? Latency of data in the RevenueCat dashboard depends on what you're viewing and how you've set up your app. We can break down the data into three categories:Transactions Charts and metrics Customer ListsTransactions in RevenueCat are new purchases and renewals (including free trials). Transactions will be shown in real-time - this includes the Customer History timelines. For data points other than transactions, things like billing issues detected, auto-renew status changes, etc., will be automatically detected by RevenueCat every few hours, but can be sped up to near real-time by enabling platform server-notifications.Charts and metrics are c

This is the most common error from RevenueCat that can also lead to unexplained App Store rejections. Unfortunately, this error occurs when Apple's /verifyReceipt endpoint is down and unable to verify purchases. In sandbox, these errors can be fairly common since the sandbox environment is not as robust as production. In production, expect these errors less often. If your app is working in sandbox mode while testing on your own devices, this is likely an issue with the App Store. App ReviewThis issue seems to affect new apps (apps that have never been released on the App Store) during their first review more than apps that have previously been released on the App Store. Generally, the best course of action is usually to re-submit your binary or try to explain the situation to the reviewer. (Some developers have reported that they had to submit their binary over ten times before it started working as expected for the reviewer!)