dooboolab-community / react-native-iap

In App Purchase module for React Native!
https://react-native-iap.dooboolab.com
MIT License
2.81k stars 641 forks source link

RNIap.requestSubscription never return promisse RN 63.2 #1093

Closed dmorsoleto closed 3 years ago

dmorsoleto commented 4 years ago

Version of react-native-iap

4.5.3 (tested on 4.5.2 also)

Version of react-native

0.63.2

Platforms you faced the error (IOS or Android or both?)

IOS

Expected behavior

Request subscription and return a promisse

Actual behavior

When I call RNIap.requestSubscription nothing is returned and never ends the call, a promisse never return, nethern an error return. (Today I have an app in production mode with RN 0.61.5 and react-native-iap@4.4.4 thats using the same coding and all is working perfectly)

Tested environment (Emulator? Real Device?)

Real Device

hyochan commented 4 years ago

I recommend you to receive the purchase result via purchaseUpdatedListener. However, we might have to look into the regression issue you've provided.

stale[bot] commented 3 years ago

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "For Discussion" or "Good first issue" and I will leave it open. Thank you for your contributions.

frknnay commented 3 years ago

I have the same issue, and I think it generally happens calling getAvailablePurchases first then requestSubscription.

stale[bot] commented 3 years ago

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "For Discussion" or "Good first issue" and I will leave it open. Thank you for your contributions.

stale[bot] commented 3 years ago

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.