Skip to main content
Question

PLEASE HELP Multiple account subscriptions under the same Apple ID - Im so lost...

  • April 26, 2026
  • 2 replies
  • 13 views

Forum|alt.badge.img

I’m at the point where I don’t even know what I’m missing anymore.

I’ve been trying to get this working for over three weeks now, and I just keep running into the exact same wall. I’ve rebuilt parts of this multiple times, gone through the docs over and over, and I feel like I’m so close — but something is still off and I can’t see it.

What I’m trying to do is allow multiple users in my app (each with their own account) to subscribe, even if they’re using the same Apple ID. Basically like how YouTube lets you have different accounts each with their own subscription, but all under one Apple account.

So I set things up the way it’s supposed to work. I created multiple subscription groups in App Store Connect (A through H), each with their own products. Everything is approved, live, and has been for weeks. Then in RevenueCat, I created matching offerings for each group and wired them all up properly with entitlements.

On the app side, I’m logging users into RevenueCat using their own user ID (no anonymous users), and I built logic to check purchase history and pick the next available offering if one is already used. So in theory, if group A is taken, it should move to B, then C, and so on.

But no matter what I do, I keep getting hit with the Apple popup:

“You’re currently subscribed to this.”

Even in cases where I know I should be hitting a different subscription group.

What makes it even more confusing is that inside RevenueCat, I can see that the correct entitlement has been granted (like “Member B”), but the “current offering” still shows the default one. So it feels like something is falling back or not being respected, even though I’m explicitly trying to control it.

I’ve tried pretty much everything I can think of at this point:

  • Forcing logout/login on RevenueCat for each user

  • Clearing and invalidating cache before resolving offerings

  • Adding delays to wait for receipt updates

  • Retrying purchases with different offerings

  • Passing offering identifiers instead of objects

  • Rebuilding and reinstalling the app over and over

And I’m still stuck with the same result.

At this point I’m honestly just exhausted trying to chase this down. I don’t think this is a basic setup issue anymore — it feels like one of those edge cases where one small thing is wrong and everything else looks correct.

If anyone has actually implemented multi-user subscriptions like this on iOS with RevenueCat and understands what might be going on, I would seriously appreciate the help.

And to be completely real — if someone is willing to go through my setup or code and just help me fix this properly, I will pay. I just need to get past this so I can move forward.

Thanks in advance 🙏

2 replies

Tarek
RevenueCat Staff
Forum|alt.badge.img+5
  • RevenueCat Staff
  • April 29, 2026

Hi ​@miss.larose 

 

Tarek from RevenueCat here, happy to assist you!

 

The architecture you described looks sound, if your goal is to allow a given user (with the same Apple ID) to simultaneously subscribe to different subscription.

 

If the goal is different (you mentioned multiple users using the same Apple ID).

 

The popup you mentioned is shown by Apple when attempting a purchase in the same subscription group.

 

I would check the logic of "check purchase history and pick the next available offering if one is already used", since it might be where the error is.

 

Here's what you want to do:

  • Check the entitlement of the already subscribed user, say entitlement for offering C
  • Then for this user, show the D paywall

The fact that RevenueCat shows the correct entitlement ("Member B") but the current offering still defaults is a separate, expected behavior. RevenueCat's "current offering" reflects what would be shown to that user on the paywall when selecting current as offering in the SDK. It does not represent what they've purchased. It doesn't automatically switch based on purchase history.

 

feel free to explain your business case and the problem you're trying and I'll help you find the right architecture, perhaps there's a simpler solution.

 

Have an excellent day!

 

Best regards,


Forum|alt.badge.img
  • Author
  • New Member
  • April 29, 2026

Hi Tarek!

 

I have been doing quite a bit of research on how it should work. I have set us as mentioned 8x different groups of subscriptions (all the same one monthly one yearly) and have set up entitlements for each, offerings for each, and each their own paywalls.

 

As for:

I would check the logic of "check purchase history and pick the next available offering if one is already used", since it might be where the error is.
 

I have never learnt how do to coding and I have been building this app with the help of Claude and ChatGPT. I have tried to direct it many many times to check this and I am still getting the “user is already subscribed” when trying to purchase the next subscription. 
 

Unfortunately I am not experienced enough to be able to dissect the code myself to find where the true mismatch/issues are… would you by chance know of a professional or outfit that I could hire to look this over?

 

I have tried TopTal and I was unfortunately majorly let down and did not receive the assistance I needed. I feel like this would be a simple solve for someone who is experienced with codebase. I on the other hand have spent weeks trying to fix it to no avail. 😣

 

Any help I can get is very much appreciated!

And thank you for your response to this message.

Tamie Larose