Skip to content
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

[firebase_messaging]: DisplayNotification.showNotification java.lang.IllegalStateException - Existing wake lock pid changed: 17169 to 21048 #16984

Closed
1 task done
Tom3652 opened this issue Jan 17, 2025 · 3 comments
Labels
Needs Attention This issue needs maintainer attention. platform: android Issues / PRs which are specifically for Android. plugin: messaging resolution: user This was a user issue, e.g. invalid configuration or code. type: bug Something isn't working

Comments

@Tom3652
Copy link

Tom3652 commented Jan 17, 2025

Is there an existing issue for this?

  • I have searched the existing issues.

Which plugins are affected?

Messaging

Which platforms are affected?

Android

Description

I have received a new crash from my live app when apparently FCM is trying to display the notification to the user ( i don't really know how it is working actually), so my comment is based on the StackTrace.

Reproducing the issue

I have no clue how to reproduce it since it happened on my live user in release mode.

Firebase Core version

3.10.0

Flutter Version

3.27.1

Relevant Log Output

Fatal Exception: java.lang.IllegalStateException: Existing wake lock pid changed: 17169 to 21048
       at android.os.Parcel.createExceptionOrNull(Parcel.java:3025)
       at android.os.Parcel.createException(Parcel.java:3001)
       at android.os.Parcel.readException(Parcel.java:2984)
       at android.os.Parcel.readException(Parcel.java:2926)
       at android.app.INotificationManager$Stub$Proxy.enqueueNotificationWithTag(INotificationManager.java:3032)
       at android.app.NotificationManager.notifyAsUser(NotificationManager.java:678)
       at android.app.NotificationManager.notify(NotificationManager.java:628)
       at com.google.firebase.messaging.DisplayNotification.showNotification(DisplayNotification.java:177)
       at com.google.firebase.messaging.DisplayNotification.handleNotification(DisplayNotification.java:111)
       at com.google.firebase.messaging.FirebaseMessagingService.dispatchMessage(FirebaseMessagingService.java:240)
       at com.google.firebase.messaging.FirebaseMessagingService.passMessageIntentToSdk(FirebaseMessagingService.java:204)
       at com.google.firebase.messaging.FirebaseMessagingService.handleMessageIntent(FirebaseMessagingService.java:190)
       at com.google.firebase.messaging.FirebaseMessagingService.handleIntent(FirebaseMessagingService.java:179)
       at com.google.firebase.messaging.EnhancedIntentService.lambda$processIntent$0(EnhancedIntentService.java:82)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
       at com.google.android.gms.common.util.concurrent.zza.run(zza.java:2)
       at java.lang.Thread.run(Thread.java:1012)

Flutter dependencies

Expand Flutter dependencies snippet
Replace this line with the contents of your `flutter pub deps -- --style=compact`.

Additional context and comments

No response

@Tom3652 Tom3652 added Needs Attention This issue needs maintainer attention. type: bug Something isn't working labels Jan 17, 2025
@SelaseKay SelaseKay added plugin: messaging platform: android Issues / PRs which are specifically for Android. resolution: needs-repro This issue could not be reproduced or needs an up to date reproduction on latest FlutterFire plugin. and removed Needs Attention This issue needs maintainer attention. labels Jan 17, 2025
@Lyokone Lyokone removed the resolution: needs-repro This issue could not be reproduced or needs an up to date reproduction on latest FlutterFire plugin. label Jan 21, 2025
@Lyokone
Copy link
Contributor

Lyokone commented Jan 21, 2025

Hey @Tom3652, I'm not reproducing this on my end. Please provide a full reproducible sample so we can try to reproduce it.
The user's phone would also help.

@Lyokone Lyokone added the blocked: customer-response Waiting for customer response, e.g. more information was requested. label Jan 21, 2025
@Tom3652
Copy link
Author

Tom3652 commented Jan 21, 2025

Hey @Lyokone, here are some additional info :

  • Phone's model : IPlay50S
  • Android version : 13
Image

Unfortunately i have never encountered this bug on my end and i am also unable to reproduce it.
I am raising the issue in case you may see something wrong that i wouldn't.

Can you confirm that the crash is caused by FCM plugin ?

@google-oss-bot google-oss-bot added Needs Attention This issue needs maintainer attention. and removed blocked: customer-response Waiting for customer response, e.g. more information was requested. labels Jan 21, 2025
@Lyokone
Copy link
Contributor

Lyokone commented Jan 21, 2025

Looking at the brand, it looks like the device is not very well known and pretty low end. If it only happens for this device, it's probably an issue with the vendor implementation. I'll close this issue since it's not something we'll be handling.

@Lyokone Lyokone closed this as completed Jan 21, 2025
@Lyokone Lyokone added the resolution: user This was a user issue, e.g. invalid configuration or code. label Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Attention This issue needs maintainer attention. platform: android Issues / PRs which are specifically for Android. plugin: messaging resolution: user This was a user issue, e.g. invalid configuration or code. type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants