-
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]: Fatal Exception: java.lang.NullPointerException when calling com.onesignal.core.internal.backend.impl.ParamsBackendService.fetchParams #1835
Comments
@dmytroreutov thank you for reaching out! We're investigating this. In the meantime, if you have any additional information you can share on the frequency of this crash or any other details provided by Crashlytics, it would be very appreciated! |
This is now becoming our #1 crash, @jennantilla is there any update on this issue? |
@jennantilla Any updates so far? This issue has ben reported for more than 3 weeks yet there is no action taken to fix it. |
+1 We're observing this issue too. |
+1 (version is 5.0.3) |
+1 We're seeing this issue as well. |
Hello has anyone been able to reproduce the issue locally? It looks like it could be happening when the app has been in the background and is then foregrounded? |
+1 (version is 5.0.3) |
+1 (version 5.0.2, on production we got a lot of crash like this) |
This should be fixed in the latest 5.1.2 https://github.com/OneSignal/OneSignal-Android-SDK/releases Please let us know if you continue to see this issue and provide the full crash log including affected devices and operating system versions. |
What happened?
I'm observing some crash reports in Firebase Crashlytics with the following stack trace:
Steps to reproduce?
What did you expect to happen?
Crashes should not happen
OneSignal Android SDK version
com.onesignal:OneSignal:[5.0.0, 5.99.99]
Android version
13, 12
Specific Android models
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: