You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2.Add your Firebase App ID and API secret for your iOS app and/or Android app
81
81
82
-
82
+
To set up your Firebase App ID, navigate to `Google Analytics > Admin > Data Streams > iOS/Android > Add Stream`. Open the App Stream to find your Firebase App ID. Copy and paste into the RevenueCat settings page.
83
83
84
-
3. Add your Firebase App ID and API secret for your iOS app and/or Android app
85
-
86
-
To set up your Firebase App ID, navigate to Google Analytics > Admin > Data Streams > iOS/Android > Add Stream. Open the App Stream to find your Firebase App ID. Copy and paste into the RevenueCat settings page.
To find your API secret, in the same _App stream details_ page select "Measure Protocol API secrets". Create an API secret. Copy and paste into the RevenueCat settings page.
91
87
92
-
93
-
94
-
4. Select whether you want RevenueCat to report sales in purchased currency (original currency or in US dollar)
95
-
5. Select whether you want sales reported as gross revenue (before app store commission), or after store commission and/or estimated taxes.
96
-
97
-
Remember to select 'Add Integration'.
88
+
3. Select whether you want RevenueCat to report sales in purchased currency (original currency or in US dollar)
89
+
4. Select whether you want sales reported as gross revenue (before app store commission), or after store commission and/or estimated taxes.
98
90
99
91
### Events
100
92
@@ -124,7 +116,7 @@ Simulate a new user installing your app, and go through your app flow to complet
124
116
125
117
Navigate to Google Analytics > Reports > Realtime. Here you will be able to confirm events have been successfully dispatched to Google Analytics. It can take up to a few seconds or minutes for your events to appear.
You have completed the Google Analytics setup! You can stop here or continue with the rest of the documentation to learn how to set up the Firebase Extension.
- (optional) Give a name to the Firestore collection where "events" will be stored
186
178
- (optional) Give a name to the Firestore collection where "customers" will be stored
187
179
- Enable or disable custom claims set in Firebase Auth with user's active entitlements. If set to “ENABLED”, the extension will consider the `app_user_id` of the user to match the user’s Firebase Authentication UID and set a “Custom Claim” with their current active entitlements
188
180
- Enter your RevenueCat Firebase Integration Shared Secret. This can be found in the RevenueCat Firebase Extension settings page. Select 'Generate shared secret' and copy it. Paste the generated shared secret in the installation prompt.
6. Once the extension is installed, navigate to Firebase > Functions in the sidebar. Copy the 'Trigger URL' and paste this into the RevenueCat Firebase Extension settings page.
216
208
217
-
![](/images/4416a89-Screen_Shot_2022-04-14_at_11.18.59_5355014091f6b4f845181de8a51a3157.png"Screen Shot 2022-04-14 at 11.18.59.png")
@@ -233,55 +225,55 @@ This portion of the installation is done through the command-line interface (CLI
233
225
1. Run `firebase ext:install . --project [project-id]`
234
226
To find your `project-id`, go to your [Firebase console](https://console.firebase.google.com/u/0/). Select your project and navigate to Project settings to copy the ID and replace `[project-id]` in the command.
235
227
236
-
![](/images/5a32c66-Screen_Shot_2022-04-14_at_11.30.52_c10aa54a363b7984b0eaff7f61e1fde7.png"Screen Shot 2022-04-14 at 11.30.52.png")
5.`Enter a value for RevenueCat Webhook Events Firestore collection:` Give a name to the Firestore collection where "events" will be stored. If left blank, RevenueCat will not save events.
6.`Enter a value for location of the customers collection:` Give a name to the Firestore collection where the customer information will be stored. If left blank, RevenueCat will not save customer information.
7.`Which option do you want enabled for this parameter (custom claims set in Firebase Auth with the user's active entitlements):` If you want to use the custom claims feature, which allows for automatic checking for Entitlements, select `ENABLED`.
8.`Enter a value for RevenueCat Firebase Integration Shared Secret:` This can be found in the RevenueCat Firebase Extension settings page. Select 'Generate shared secret' and copy it. Paste the generated shared secret in the installation prompt.
10. Once the extension is installed, navigate to Firebase > Functions in the sidebar. Copy the 'Trigger URL' and paste this into the RevenueCat Firebase Extension settings page.
277
269
278
-
![](/images/4416a89-Screen_Shot_2022-04-14_at_11.18.59_5355014091f6b4f845181de8a51a3157.png"Screen Shot 2022-04-14 at 11.18.59.png")
##### Note about the App User ID's in the Customers collection
281
273
282
274
The document ID's in the Customers collection will always be an App User ID. Specifically, it will be the customer's most recently active alias. This means that the document ID for each customer may switch between [anonymous ID's](/customers/user-ids#anonymous-app-user-ids) and [custom ID's](/customers/user-ids#logging-in-with-a-custom-app-user-id), if they are both used in your app. If you would like to only use custom ID's, you can [learn more about that here](/customers/user-ids#how-to-never-see-anonymous-app-user-ids).
283
275
284
-
![](/images/a8c5e19-Screen_Shot_2022-04-15_at_2.08.18_PM_619e3596f4922cb3f94a3b66553145a6.png"Screen Shot 2022-04-15 at 2.08.18 PM.png")
@@ -299,15 +291,13 @@ Simulate a new user installing your app, and go through your app flow to complet
299
291
300
292
While still on the Customer View, select the purchase event in the [Customer History](/dashboard-and-metrics/customer-history) page and make sure that the Firebase (Firebase function) integration event exists and was delivered successfully.
301
293
302
-
![](/images/02ff787-Screen_Shot_2022-05-09_at_7.09.39_PM_06eb1d4e603c44b7ebcdf717b95bfbe0.png"Screen Shot 2022-05-09 at 7.09.39 PM.png")
303
-
304
294
#### Check Firestore Database Collections
305
295
306
296
Navigate to your Firebase dashboard > Firestore Database to find events sent for your collections.
307
297
308
-
![Customers collection](/images/6e4ad8e-Screen_Shot_2022-04-25_at_13.19.54_7fa618d818ff07466a87db2428fbca92.png"Screen Shot 2022-04-25 at 13.19.54.png")
Copy file name to clipboardExpand all lines: docs/sdk-guides/ios-native-3x-to-4x-migration.mdx
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,9 +49,9 @@ To start us off, our framework name changed from `Purchases` to `RevenueCat`!
49
49
50
50
Select your target in Xcode, then go to Build Phases, and ensure that your target's `Link Binary with Libraries` section references `RevenueCat`, and remove the reference to `Purchases` if it was still there.
|||
|||
55
55
56
56
**Note:**
57
57
@@ -78,10 +78,10 @@ Select your target in Xcode, then go to Build Phases, and ensure that your targe
78
78
references `RevenueCat`, and remove the reference to `Purchases` if it was still there.
|||
|||
Copy file name to clipboardExpand all lines: docs/test-and-launch/app-store-rejections.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,11 +29,11 @@ Usually the reviewer will include a screenshot with the problem they encountered
29
29
30
30
Often times, purchases will work fine in Sandbox and Testflight, but App Store Review will not be able to fetch products. It's important to ensure that you are submitting your in-app purchases with your app for review. If an app has not previously had in-app purchases approved on the App Store, an option to submit them will appear on the main app version page.
31
31
32
-
32
+
33
33
34
34
To see this option, you must first fill in all required metadata so that the status of any in-app purchases you intend to use is 'Ready to Submit'.
35
35
36
-
36
+
37
37
38
38
If you've already released a version of your app containing in-app purchases, you can create new products in App Store Connect without having to release an update to your app. You'll have to submit new products for review independently of a new app version, and they must be in the 'Approved' state before they'll be available for purchase.
In order to use the overlay, you need to include the debug view library which is available on Maven and can be included via Gradle. Currently, this is only available as a Jetpack Compose Composable.
Copy file name to clipboardExpand all lines: docs/test-and-launch/debugging/caching.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ RevenueCat caches data in several places to improve performance. This includes t
11
11
12
12
In the Overview, the data is usually not cached and these subscription metrics will be updated in real-time. New Customer and Active Users may be cached for 1-2 hours. For some larger customers, subscription metrics may be cached for 1-2 hours as well.
In each metric, you can hover over the circle icon in the bottom right corner of the card to see how recently the data within that card has been updated.
0 commit comments