bug: android notification not triggers onMessageReceived if the app is killed

[NLueg]

Plugin(s)

• Analytics
• App
• App Check
• Authentication
• Crashlytics
• Cloud Messaging
• Performance
• Remote Config

Did you test the latest version?

• I use the latest version

Platform(s)

• Android
• iOS
• Web

Current behavior

When I trigger a notification for my Android device (it doesn't matter if silent or not) the onMessageReceived method of the FirebaseMessagingPlugin is called but not forwarded to my app.

I investigated the issue a bit more and the problem is that getFirebaseMessagingPluginInstance returns null as you can see in the screenshot. And this is because the staticBridge is null because the plugin (and the whole activity) is not loaded.

Expected behavior

Notifications should trigger the Capacitor listener for onMessageReceived even if the application is killed.

Reproduction

https://github.com/NLueg/android-killed-notification-issue

Steps to reproduce

It's actually not easy to provide an example for such issues as this would require publishing the firebase configuration. Do you have a solution for this? If you never heard of such a problem I will try to add it to the example

1. Install the @capacitor-firebase/messaging plugin
2. Send a notification to the opened app (onMessageReceived is called)
3. Close the app
4. Send the same notification again (onMessageReceived is not called)publishing

Other information

Capacitor doctor

Latest Dependencies:

@capacitor/cli: 5.2.2
@capacitor/core: 5.2.2
@capacitor/android: 5.2.2
@capacitor/ios: 5.2.2

Installed Dependencies:

@capacitor/cli: 5.2.2
@capacitor/core: 5.2.2
@capacitor/ios: 5.2.2
@capacitor/android: 5.2.2

Before submitting

• I understand that incomplete issues (e.g. without reproduction) are closed.

[robingenz]

Hi @NLueg, thank you for your request!

Notifications should trigger the Capacitor listener for onMessageReceived even if the application is killed.

It triggers the listener, but only on the next app launch, not immediately. If the app is killed, then no method can be called in the WebView.
If you want to execute code while the app is killed, then you have to write native code that does not run in the WebView.

[NLueg]

Thank you for the fast response! Okay, actually I already thought that. But I hoped that you already have a solution for this 😆
When I am able to solve this, I will post the solution here.