-
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
[Bug]: Crash when call promptForPushNotifications, NullPointerException #1664
Comments
Hi @Kppro, from the stack trace it looks like you might be calling |
I'm having a simillar log as him. My initialization occurs when I build my dependency graph (probably a little after application create). I tried change it to Application.onCreate() but still receiving this exception.
|
Hi @brismithers , I am calling I did multiple test with the emulator but wasn't able to reproduce and I don't have a pixel device at the moment. (but maybe we only see pixels device because they are the first ones with the android 13 update) |
I'm having the same problem but on multiple android versions.
in my onCreate() but I get a lot of crashes from my users Here is my crash log:
the crash happens mainly on Redmi smartphones |
Same error occured and caught by Sentry for Pixel XL device (Pixel 4 XL (TP1A.221005.002)) : java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.content.Context.getPackageName()' on a null object reference
at com.onesignal.OSUtils.o(OSUtils.java:1)
at com.onesignal.l0.<clinit>(NotificationPermissionController.kt:4)
at com.onesignal.d3.D1(OneSignal.java:1)
at com.onesignal.flutter.OneSignalPlugin.J(OneSignalPlugin.java:2)
at com.onesignal.flutter.OneSignalPlugin.onMethodCall(OneSignalPlugin.java:16)
at xi.k$a.a(MethodChannel.java:2)
at ki.c.l(DartMessenger.java:2)
at ki.c.m(DartMessenger.java:2)
at ki.c.i
at ki.b.run
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.main(ActivityThread.java:7898)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)
java.lang.ExceptionInInitializerError: null
at com.onesignal.d3.D1(OneSignal.java:1)
at com.onesignal.flutter.OneSignalPlugin.J(OneSignalPlugin.java:2)
at com.onesignal.flutter.OneSignalPlugin.onMethodCall(OneSignalPlugin.java:16)
at xi.k$a.a(MethodChannel.java:2)
at ki.c.l(DartMessenger.java:2)
at ki.c.m(DartMessenger.java:2)
at ki.c.i
at ki.b.run
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.main(ActivityThread.java:7898)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)
|
the same bug is present for the ionic sdk too |
Updates? |
Hi, I subscribed to this issue because I had similar issue but on another SDK (react-native). |
buildToolsVersion = "33.0.0" the error is still there |
Has anyone been able to reproduce this issue in their project? |
Any update on this? |
Running into this as well. Has anyone been able to get a workaround to work? |
same issue here |
Same issue here on Flutter SDK |
Hello everyone! Apologies that this issue has gone stale. Much of our work in the last few quarters have been on a new major release where many improvements and enhancements are introduced. We will continue to investigate 4.x.x bugs, though we encourage you to update to our latest release as that will be the most-supported release going forward. Please see our migration guide for full details on upgrading. If this crash is still a current concern for anyone, please let us know update reproduction steps and we will investigate further. Thanks! |
What happened?
Crashs at our app startup on Pixels devices with Android 13 and latest release of onesignal sdk (4.8.2)
Steps to reproduce?
What did you expect to happen?
I expected no crash when calling promptForPushNotifications on an android 13 device
OneSignal Android SDK version
Release 4.8.2
Android version
13
Specific Android models
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: