-
-
Notifications
You must be signed in to change notification settings - Fork 659
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
NullPointerException in Android #600
Comments
Please try |
* 'master' of https://github.com/dooboolab/react-native-iap: (107 commits) Release 3.3.4 Keep valid SKUs in memory chore(package): update flow-bin to version 0.103.0 Fixes hyochan#600 Added missing types on updates in 3.3.0 chore(package): update @types/react-native to version 0.60.2 Release 3.3.1 (hyochan#596) Update travis with yarn Fix flow type for purchaseUpdatedListener Upgrade example project rn version chore(package): update @types/react-native to version 0.60.1 Fix hyochan#581 finishTransaction called automatically (hyochan#589) Update index.js.flow chore(package): update lockfile yarn.lock chore(package): update @types/react-native to version 0.60.0 chore(package): update lockfile yarn.lock chore(package): update @types/react to version 16.8.23 Fixes hyochan#577 (hyochan#578) Update @types/react-native to the latest version 🚀 (hyochan#575) Improve README (hyochan#574) ... # Conflicts: # ios/RNIapIos.m
I have a few crashes because of null pointer at line 504 now, on Android 8.1 in production build. v3.3.4
|
@lachtos Would you try |
I can't reproduce it so it's a bit hard to debug. These logs are from google play console crash reports. After some googling I found that there are some rare cases when the value returned from the google api is null, so there should be null checks like there are right now in 3.3.5 I can't afford to keep testing this in production so I threw the code inside a try/catch for now. |
I had an app crash in the pre-launch test in google play console, giving this error stack:
I don't get crashes yet on real devices, but since the code which caused this crash is fairly new (RNIapModule.java:496) I think it would be smart to take a look into this. Maybe it's just an environment issue and would not occur in real devices?
Also, I just had another pre-launch test on updated apk with no changes to the IAP module/code on the same android 4.3 device and it did not crash.
Version of react-native-iap
3.3.1
Version of react-native
0.59.10
Platforms you faced the error (IOS or Android or both?)
Android 4.3 | Galaxy S3
Expected behavior
No crash
Actual behavior
java.lang.NullPointerException
Tested environment (Emulator? Real Device?)
Google Play Console Pre-launch report
Steps to reproduce the behavior
Have google play console run a pre-launch test on the uploaded app
The text was updated successfully, but these errors were encountered: