-
-
Notifications
You must be signed in to change notification settings - Fork 647
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
getProducts and getSubscriptions are empty #1231
Comments
Same here? |
Please try to clean cache of Google Play Services app and try again. |
It was solved with easy solution. I did sync google playstore account again. After sync completed, it is working. |
@MaoPeng94 Looks like this is many asked question. Could you kindly support more direction in this thread on syncing account? (for other users) |
Also here is a great article to handle such an issue. |
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 for now, please feel free to reopen if needed |
is there any solution for iOS ? |
@ZeeshanAhmadKhalil Please try to add the storekit if you're testing on simulator |
Version of react-native-iap
5.2.3
Version of react-native
0.63.4
Platforms you faced the error (IOS or Android or both?)
Android
Expected behavior
getProducts and getSubscriptions should not return an empty array
Actual behavior
getProducts and getSubscriptions return an empty array
Tested environment (Emulator? Real Device?)
Real device
Steps to reproduce the behavior
I already configured it on IOS the app is working fine
On Android I published the app on internal test and my main account on the internal test release in among the test users.
My product is a subscription I do not know if I have to do something else
My subscription is active
My release is accessible for internal test
The text was updated successfully, but these errors were encountered: