You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can't understand why this functions are being called after error event was fired. Looks like there's a combination of 2 approaches used here.
The new promise is being create on each initialization and then it's resolved or rejected depending on the operation results along with sending events via DeviceEventManagerModule.
But as I understood from the docs, the only way of communication with the library is via events, promises are deprecated now.
Maybe I don't get something correctly, but from my point of view, the library shouldn't reject promises when sending error events.
@hyochan Any other ideas? I'm ready to contribute, just want to understand that I'm moving into the correct direction.
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.
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.
Version of react-native-iap
3.0.3
Version of react-native
0.59.10
Platforms you faced the error (IOS or Android or both?)
Android
Expected behavior
No unhandled promise warning
Actual behavior
Tested environment (Emulator? Real Device?)
Real Device
Steps to reproduce the behavior
Build Example App on the 3.0.x branch. Run on device, touch
Get Products
, then touchPurchase android.test.canceled
The text was updated successfully, but these errors were encountered: