-
-
Notifications
You must be signed in to change notification settings - Fork 637
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
Invalid product Id on iOS #304
Comments
I can't read your language so are you sure it is in |
Also please refer to #256 who've explained the config step in detail. |
Yes, It says Ready to Submit. I forgot to translate for you. Sorry. |
Please refer to #256 and try again |
Hmm having similar issues with invalid productId |
Did you go over above issue I’ve mentioned? |
@dooboolab Thanks for the link. Followed it and it worked. Thanks for your great work on this library! |
Nice to hear the issue was resolved. I'm closing this issue. |
Problem solved.. My mistake was incorrectly filled out a tax form on the site Apple. Thank you) |
Version of react-native-iap
2.3.17
Main Library
expo: "30.0.0"
react: "16.3.1"
react-native: 30.0.0 from expo server
Platforms you faced the error (IOS or Android or both?)
iOS
Expected behavior
Returning list of subscription
Buy subscription
Actual behavior
Our app is already approved and ready for sale on App Store and all products is "Ready for Submit" but still when i call RNIap.getSubscriptions it returns empty [] and I call buySubscription(ProductId) it returns "Product Id Invalid"
Tested environment (Emulator? Real Device?)
Emulator and real device
Steps to reproduce the behavior
I make all steps in the tutorial.
Make sandbox user in Role & Users and connect to real device.
Make two items form subscription.
RNIap.initConnection always return true.
Question:
Q1: I need some backend for working with RNIap?
Q2: Can i get list of subscription in emulator or real device without publish to Testflight?
My code:
p.s. I spent 3+ days searching for a solution and nothing helped me.
The text was updated successfully, but these errors were encountered: