`purchasePackage` method hangs forever with DEFERRED proration. No information about DEFERRED subscription

[Bi0max]

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

Hi all,

I use a React Native SDK. I have several plans. When I want to downgrade to a cheaper plan, I try to use a DEFERRED proration mode. The change is successful on Google Play's side, but purchasePackage method hangs forever.

Also, when I use restorePurchases method, I do not get any update about a change in the plan. Which is probably logical, since I do not see any changes in my dashboard until the moment, when the plan actually changes (when the old plan expires).

I wonder, is it an expected behavior or a bug? And I am also surprised that this option was removed from v7 at all. How should we handle downgrades on Google Play?

Thank you!

1. Environment
   1. Platform: Android
   2. SDK version: I tried version 6.6.4. This link says that it should work in major version 6: https://community.revenuecat.com/product-updates/react-native-7-0-0-3412?tid=3412&fid=None. Latest version 7.6.0 does not have this option at all.
   3. OS version: Android version 14
   4. Xcode/Android Studio version: using expo
   5. React Native version: 0.72.5
   6. SDK installation (CocoaPods + version or manual): using expo
   7. How widespread is the issue. Percentage of devices affected.: Currently testing on my own device before launching into production
2. Debug logs that reproduce the issue: I have added Purchases.setLogLevel(Purchases.LOG_LEVEL.DEBUG); but I do not see anything in my log
3. Steps to reproduce, with a description of expected vs. actual behavior a.
4. Other information (e.g. stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc.)

Additional context Add any other context about the problem here.

[RCGitBot]

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