-
Notifications
You must be signed in to change notification settings - Fork 368
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
Amazon (ADM) devices - Fatal Exception: java.lang.NullPointerException com.onesignal.OneSignalDbHelper.getInstance #1282
Comments
Thanks for reporting. I believe the issue has to do with OneSignal not calling This is something that can be added to fix this issue and some integration tests implemented to prevent a regression in the future. |
@jkasten2 is there any updates about fixes for the issue posted above? |
Any update here, we are also facing the same issue? |
1 similar comment
Any update here, we are also facing the same issue? |
We're seeing this too, in latest OneSignal React Native. On all types of devices, not just Amazon |
any luck on this one? also having this one coming on Sentry.
|
me too!
|
For those seeing this issue on Amazon devices this should now be fixed in 5.1.7. If you see an issue sending Amazon notifications please see #1936 (comment)
@jacklj This issue thread is specific to Amazon devices, if you are seeing a similar issue please open a new issue, as the stacktrace will be different for non-Amazon devices. |
Description:
We do not how to reproduce the issue, but we have a lot of crashes in Crashlytics console. Seems like happens on Amazon devices only with android version 5.1.1.
Environment
5.1.1 KFFOWI
5.1.1 KFGIWI
5.1.1 KFASWI
5.1.1 KFARWI
5.1.1 KFTBWI
Steps to Reproduce Issue:
Anything else:
(crash stacktraces, as well as any other information here)
The text was updated successfully, but these errors were encountered: