-
Notifications
You must be signed in to change notification settings - Fork 370
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
[Bug]: Multiple errors on initOneSignal SDK #1869
Comments
Observed similar issue on Redmi 5 Plus, Android 8.1.0, OneSignal Android SDK version 5+ Logs:
|
@IvanGarza07 Thank you for reaching out many of these issues have been resolved by releases since 5.0.0 although there may be still be existing issues. If you are able to reproduce any of these issues on the latest release any reproduction steps would be helpful |
i updated to latest version (5.0.3) but the errors persist, i try to reproduce the errors but can't reproduce the errors i dont have idea how to do that. I had to downgrade oneSignal to 4.8.3 version |
@emawby one more note, we're using Proguard/R8 in the app, maybe this related to the issue somehow. And the issue is reproducible not always, around 70% probably, sometimes it did not crashed the app. |
I believe there are a couple distinct issues and want to make sure nothing is missed: JSONException 'Value test3 at key..' and 'Value at lon...' java.lang.Exception - Unrecognized operation: login-user-from-subscription* java.lang.NullPointerException |
@brismithers yes there are a different issues and I guess these issues didn't fixed because I'm used the latest version and the problems still present in the app, I had to downgrade the 4.8.3 version. I cant give you more information cause I cant replicate the issues when run my app but in production the issue appear a lot. |
No problem @IvanGarza07 and sorry for your headaches. Once we create a release containing the fix for #1884 I hope you are able to get give v5 another try! Regarding the last issue (the java.lang.NullPointerException) if it does happen again please post the stack trace. I'll close this issue once the next release is out. |
What happened?
The sdk present these errors since version 5.0.0:
these happen when execute the OneSignal.initWithContext(context, BuildConfig.ONE_SIGNAL_KEY)
Steps to reproduce?
What did you expect to happen?
i expected the SDK initiate normally
OneSignal Android SDK version
5.0.0 and above
Android version
13, 12, 11, 10, 9, 8
Specific Android models
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: