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, purchases won’t be transferred on the same device.
Can you help me validate if this is correct?
Best answer by sundeepView original