RevenueCat Support Inquiry: Detecting Active Subscriptions on Shared Store account Before Purchase
Context
We have multiple users with separate accounts in our app using the same device and Store account. We're encountering an issue with subscription management when users share the same Store account.
Current Setup
- Platform: React Native
- SDK: react-native-purchases
- RevenueCat Setting: "Keep with original App User ID"
- Use Case: Scenario where:
- Device has one Store account configured
- Multiple users have separate accounts in our app
- Each user needs their own subscription, but they share the device (and Store account)
The Problem
Scenario:
1. User A logs into our app with credentials: userA@example.com
2. We call Purchases.logIn('userA_12345')
3. User A purchases Product X (e.g., Monthly Plan) using Store account: M
4. User A logs out
5. User B logs into our app with different credentials: userB@example.com
6. We call Purchases.logIn('userB_67890')
7. User B's customerInfo shows no active entitlements (because we use "Keep with original App User ID" setting)
Observed Behavior:
Case 1: User B tries to purchase the SAME product (Product X)
- RevenueCat returns an error
- Purchase is blocked
- ✅ This is working as expected
Case 2: User B tries to purchase a DIFFERENT product (Product Y - e.g., Yearly Plan)
- Purchase goes through successfully
- The subscription gets linked to User A (userA_12345) due to our "Keep with original App User ID" setting
- User B thinks they purchased as the amount got deducted but missing entitlements because User A gets the subscription
- ❌ This creates confusion and support issues
Our Core Question
How can we detect BEFORE initiating a purchase that the current Store account already has an active subscription associated with a different App User ID?
What We Need:
We need to show a pre-purchase validation message to User B:
"This Store account already has an active subscription associated with another account. Please use a different store account to purchase."
------------
Thank you for your assistance! This is causing significant user confusion and support burden, as users are purchasing subscriptions that get linked to different accounts.
