`purchasePackage` is never resolved nor rejected

TL;DR

How to purchasePackage is never resolved nor rejected.

Steps

1. Issue RevenueCat/react-native-purchases#579 (closed, 19 comments): - [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 Description Starting with March the 6th, the Purchases.purchasePackage promise is neither resolved nor rejected.
2. If Purchases.purchasePackage never resolves or rejects, check your addCustomerInfoUpdateListener callback: calling Purchases.getCustomerInfo inside it deadlocks, which is exactly what happened here. That deadlock was fixed in the next release (purchases-ios PR 241). Note some Android users still reported it later, so if you're on a current version and it persists, open a fresh issue with logs rather than reopening this one.

Expected: That deadlock was fixed in the next release (purchases-ios PR 241).

When to use

You are seeing this: Note some Android users still reported it later, so if you're on a current version and it persists, open a fresh issue with logs rather than reopening this one. Use this skill when you run into "purchasePackage is never resolved nor rejected".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Edge cases

• Note some Android users still reported it later, so if you're on a current version and it persists, open a fresh issue with logs rather than reopening this one.

Sources

• https://github.com/RevenueCat/react-native-purchases/blob/main/CONTRIBUTING.md
• https://community.revenuecat.com
• https://docs.revenuecat.com/
• https://github.com/RevenueCat/react-native-purchases/issues
• https://github.com/RevenueCat/react-native-purchases/issues/579

In gh:RevenueCat/react-native-purchases#579, the reporter ran into: Issue RevenueCat/react-native-purchases#579 (closed, 19 comments): - [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 Description Starting with March the 6th, the Purchases.purchasePackage promise is... The verified answer was: If Purchases.purchasePackage never resolves or rejects, check your addCustomerInfoUpdateListener callback: calling Purchases.getCustomerInfo inside it deadlocks, which is exactly what happened here. That deadlock was fixed in the next release (purchases-ios PR 241). Note some Android users still reported it later, so if you're on a current version and it persists, open a fresh issue with logs rather than reopening this one. Source issue: https://github.com/RevenueCat/react-native-purchases/issues/579