Cannot get the active entitlements in Sandbox environment when having same type of entitlements in Prod.

[menghaozhang]

• I have updated Purchases SDK to the latest version
• I have read the Contribution Guidelines
• I have searched the Community
• I have read docs.revenuecat.com
• I have searched for existing Github issues

Describe the bug
The user data in prod environment will override the sandbox environment for active entitlements. I have same entitlements type(not exactly same as different expire dates.) in both prod and sandbox env when using customerInfo?.entitlements.activeInAnyEnvironment I can only get the prod env active entitlements. Which is fine. But when using customerInfo?.entitlements.activeInCurrentEnvironment I get no active entitlements no, as empty.

1. Environment
   1. Platform: iOS
   2. SDK version: 4.32.0
   3. StoreKit version:
      • StoreKit 1
      • StoreKit 2 (enabled with usesStoreKit2IfAvailable(true))
   4. OS version: 17.0
   5. Xcode version: 15.x
   6. Device and/or simulator:
      • Device
      • Simulator
   7. Environment:
      • Sandbox
      • TestFight
      • Production
   8. How widespread is the issue. Percentage of devices affected.
2. Debug logs that reproduce the issue. Complete logs with Purchases.logLevel = .verbose will help us debug this issue.

Logs here

3. Steps to reproduce, with a description of expected vs. actual behavior

• Create a user with same type of active entitlement in both prod and sandbox env.
• Use customerInfo?.entitlements.activeInCurrentEnvironment to fetch the data.

Expected behavior

• Client should get expected data same as shown in console in corresponding environment.

Actual behavior

• In sandbox env, the result is empty.
• In prod env, the result is correct.

4. Other information (e.g. stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc.)
   If I "remove" the active entitlement from prod env user(either transfer to another user or delete it), I can get correct active entitlement in sandbox env.

5. Additional context

[RCGitBot]

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

[aboedo]

@menghaozhang thanks for reporting! You're correct. The underlying issue stems from the fact that our backend sends only one product per entitlement, so if you have an entitlement from both sandbox and production, this situation can happen.
We'll take a look at possible fixes for this.

[menghaozhang]

I see, thank you @aboedo!

[DabbyNdubisi]

Hi, wondering if there's an update on this issue, as it's happening for me while I test.

In my case I have a granted promotional entitlement on a user (which from what I understand applies to both sandbox & production), but when I try to make a sandbox purchase for a product tied to the same entitlement it fails.

The underlying issue stems from the fact that our backend sends only one product per entitlement, so if you have an entitlement from both sandbox and production, this situation can happen.

Is it safe to assume then that this issue wont happen in production when the environment of the granted entitlement matches the environment of the product being purchased?