Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RNIap.requestPurchase have no resolved promise result on iOS 14.0 version #1058

Closed
VEnom42 opened this issue Jul 29, 2020 · 7 comments
Closed

Comments

@VEnom42
Copy link

VEnom42 commented Jul 29, 2020

Version of react-native-iap

4.4.8, 4.5.0

Version of react-native

0.61.5

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

IOS (14.0)

Expected behavior

requestSubscription and requestPurchase methods should resolve promise on sucessful purchase.

Actual behavior

purchaseUpdatedListener receives the result of successful purchase but RNIap.requestPurchase(sku, false) and RNIap.requestSubscription(sku, false) have no resolved promise result. Actually there is no success callback execution. It works fine in previous ios versions and in android.

Tested environment (Emulator? Real Device?)

both

Steps to reproduce the behavior

  1. Set up purchases.
  2. Get real device with ios 14.0 or emulator with working StoreKit
  3. Try to get console.log from successful purchase:
RNIap.requestPurchase(sku, false).then(result => {console.log('result', result)});
//or
RNIap.requestSubscription(sku, false).then(result => {console.log('result', result)});
@MacroBet
Copy link

I'm having the same problem

@captaincole
Copy link

Also seeing this issue on iOS 14 beta 2.

@corasan
Copy link

corasan commented Aug 3, 2020

Weird thing is that it was working for me perfectly fine. I was using Iaphub to handle the purchase and started having this issue so I switched to using this package and it was working fine until yesterday.

It actually seems to be working, it does nothing after the purchase and you have to reload the app and then all the code after making the purchase will run.

@lempa
Copy link

lempa commented Aug 3, 2020

We're having the same issue in a mac catalyst app on iOS 13 / macOS 10.15.5.
The steps to reproduce the behavior are the same

@iaphub
Copy link
Contributor

iaphub commented Aug 3, 2020

Just submitted a pull request to fix the issue.
As soon as it is accepted, we will update react-native-iaphub to the latest version of react-native-iap with the fix 👍

@VEnom42
Copy link
Author

VEnom42 commented Aug 6, 2020

Fixed in 4.5.2.

@VEnom42 VEnom42 closed this as completed Aug 6, 2020
@n0umankhan
Copy link

+1 still having the same problem in IOS, I'm using 4.5.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants