Google app user ID detection method #605
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Preview this PR here: https://dev-docs.revenuecat.com/pr-605/ |
codykerns
approved these changes
Jan 17, 2025
mcastany
approved these changes
Jan 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation / Description
Creating a new PR since the previous PR was before the doc restructuring. I removed the big diagram for paths depending on what restore behavior you're on because after looking at it again, it provides a lot of details that makes it unnecessarily complicated to understand. Especially since it just distills down to 1) do the account IDs match the app's app user id and 2) if you're using Google pub/sub + the SDK, use the anonymous app user ID detection method
Changes introduced
Linear ticket (if any)
Additional comments