-
Notifications
You must be signed in to change notification settings - Fork 373
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]: OneSignal 5.1.2 NullPointerException on OneSignal initialization #1990
Comments
We had the same problem with 5.1.2 and downgraded our SDK to 4.8.6. II will provide additional context when the crash occurs. Frequency of OccurrenceAbout. 0.1% of users (10 in 10,000) Android version8〜14 Specific Android modelsOccurs on a variety of devices. Device Status96% background Relevant log outputAlmost the same comment as above. Hopefully the problem will be resolved soon. |
I also had to downgrade the SDK to 4.8.7, waiting for the updates on this one. |
Crash information. I hope it will be helpful:
|
We have a fix that will lower and possibly fix all crashes related to this @bundleberk, @area51bis, @tikidunpon if you continue to seeing this issue after updating to 5.1.6 please let us know the new percentages of crashes the new stack traces. |
What happened?
I'm using OneSignal 5.1.2 on my android project. Some of my users are getting a nullpointerexception crash when initializing onesignal using OneSignal.initWithContext in application's onCreate.
Steps to reproduce?
What did you expect to happen?
Seems like SDK's ApplicationService.getAppContext cannot get the context I pass to OneSignal.initWithContext. This should not happen.
OneSignal Android SDK version
Release 5.1.2
Android version
13, 12, 11, 10, 9, 6
Specific Android models
No response
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: