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

No any response after changing the subscription plans (Android only) #707

Closed
hanomain99 opened this issue Sep 9, 2019 · 5 comments
Closed
Labels

Comments

@hanomain99
Copy link

Version of react-native-iap

3.3.9

Version of react-native

0.59

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

Android

Expected behavior

Should return any response (Better if receive a receipt)

Actual behavior

Doesn't return any response

Tested environment (Emulator? Real Device?)

Real Device - sandbox

Steps to reproduce the behavior

  1. Subscribe to a yearly subscription plan
  2. Then change the yearly subscription plan to monthly subscription plan

Description

  1. requestSubscription('yearly')
  2. Success
  3. Current subscription is active
  4. requestSubscription('monthly', 'yearly', 'mode')

Doesn't receive any response to purchaseErrorListener or purchaseUpdateListener

@hanomain99
Copy link
Author

hanomain99 commented Sep 10, 2019

We dug into the android native code in Iap module and after changing the subscription plan, only onPurchaseUpdated method is triggered in RNIapModule.java file.

onPurchaseUpdated method is triggered with a null value for purchases argument and startListening method is not invoked.

@stale
Copy link

stale bot commented Dec 10, 2019

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 stale bot added the 🚶🏻 stale Stale label Dec 10, 2019
@howg0924
Copy link

@asbarali We also encountered this problem. Did you find the solution in the end?

We tried RNIap 4.3.0 & 4.3.3, the issue is basically the same. The only difference is the registered purchase error listener will be called with the following error due to this change on 3.4.12:

{ message: 'purchases are null.',
code: 'OK',
debugMessage: '',
responseCode: 0 }

@hyochan May you give us some hint on this issue? Thank you so much~.

@stale
Copy link

stale bot commented Mar 26, 2020

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 stale bot added the 🚶🏻 stale Stale label Mar 26, 2020
@stale
Copy link

stale bot commented Apr 25, 2020

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.

@stale stale bot closed this as completed Apr 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants