-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
NullPointerException when restarting the foreground service with a null intent #2298
Comments
Line 25 in 5e7d4ee
Should the null intent case be handled here? Or, would changing the foreground service start type to '
|
have you sloved it ? |
I did not. Stopped using this feature, it was too unstable in my case. |
Any update with this? |
try this code:
|
@k104h8KX @aly7yaNasser @cevargasing Sorry this happened to you guys. This issue has been re-discovered in #2446 with an apparent means to reproduce the crash, and a proposed fix. I suggest you subscribe to that issue for follow-ups, and see my comment for more details. Try using |
I'm getting a
Fatal Exception: java.lang.RuntimeException: Unable to start service com.dexterous.flutterlocalnotifications.ForegroundService@d50aeda with null: java.lang.NullPointerException: Attempt to invoke virtual method 'java.io.Serializable android.content.Intent.getSerializableExtra(java.lang.String, java.lang.Class)' on a null object reference
t seems to happen when the app is in the background and the user taps on the foregroundservice notification. I'm not able to reproduce it myself, caught by Crashlytics.
Using the default: '
START_STICKY
', I would just need the tap on the foreground to open the app.Current implementation:
What am I missing here?
The text was updated successfully, but these errors were encountered: