• 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
A clear and concise description of what the bug is. The more detail you can provide the faster our team will be able to triage and resolve the issue. Do not remove any of the steps from the template below. If a step is not applicable to your issue, please leave that step empty.

1. Environment
   1. Platform: Android
   2. SDK version: 35
   3. OS version: multiple
   4. Android Studio version: multiple
   5. How widespread is the issue. Percentage of devices affected. -- all tested devices
2. Debug logs that reproduce the issue
   • no relevant logs produced (either in-app or from adb logcat)
3. Steps to reproduce, with a description of expected vs. actual behavior
   • have two subscription products (separate products, not base plans of the same product) in Google Play
   • subscribe to one of them
   • subscribe to the other product using DEFERRED proration mode
   • I am doing this via react-native-purchases with Purchases.purchasePackage(package, null, { oldProductIdentifier: <id>, prorationMode: PRORATION_MODE.DEFERRED })
   • the promise never resolves (i.e. onSuccess never fires), even though if I look at my subscriptions in Google Play the purchase did go through as expected
   • the promise should resolve when the purchase completes, as it does when other proration modes are used
4. Other information (e.g. stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc.)
   • I'm opening this on the purchases-android repo because it looks like react-native-purchases and purchases-hybrid-common are pretty thin wrappers, and AFAICT there's no reason within them that this flow should work with some proration modes but not others.
   • That said I'm happy to reopen on a different repo if that would help.
   • This issue describes exactly the same problem but seems to have had no traction.
   • This RevenueCat blog post describes a possible cause of the exact issue I'm seeing.

Additional context
Add any other context about the problem here.