quickstart-unity: MessageReceived event doesn't fire when app is in background

[REQUIRED] Please fill in the following fields:

Unity editor version: 2018.4.29f1
Firebase Unity SDK version: 6.16.x
Source you installed the SDK: Unity Package Manager
Problematic Firebase Component: CloudMessaging
Other Firebase Components in use: RemoteConfig, Analytics
Additional SDKs you are using: GoogleMobileAds
Platform you are using the Unity editor on: Mac
Platform you are targeting: Android
Scripting Runtime: Mono

[REQUIRED] Please describe the issue here:

FirebaseMessaging.MessageReceived does not fire when I click on notification and the app is opened from the background. I experience the issue in SDK versions of 6.16.0 and 6.16.1, I see no problem in version 6.15.2.

Steps to reproduce:

Open app.
Send notification.
Notification is received. OK.
Hide app (so it stays in the background)
Send notification.
Click on the notification to open the app.
Callbacks registered to FirebaseMessaging.MessageReceived do not fire.

reproducible with the Firebase Unity quickstarts, 100% of the time.

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 19 (9 by maintainers)

Links to this issue

Commits related to this issue

Using the recommended backwards compatible way of scheduling jobs introduced in Android O. We moved from using `IntentService` to `JobIntentService` in preparation for this change but the call to sch... — committed to firebase/firebase-cpp-sdk by a-googler 3 years ago
Merge main branch changes into dev. (#270) * Avoid double deletion of internal objects during cleanup. This has been observed during cleanup when a DocumentReferenceInternal is destroyed, its Fut... — committed to firebase/firebase-cpp-sdk by jonsimantov 3 years ago

Most upvoted comments

@npicouet, this very severe bug was reported 2 months ago and 6 weeks ago you found the problem. We experience it, too. When do you think this fix will be included in an update for Unity? It’s really needed!

jmmdk on Jan 19, 2021

Are you seeing the problem in 6.15.1?

As I said I tested all SDKs starting from 6.15.0. So yes, it exists. Now I am on 7.0.2, and it still here

The fix is ready in our internal systems and will roll out with the next release.

Did I correctly understand, that this issue existed for almost 1 year (or when that 6.15.0 was released) and only next Unity SDK will include the fix?

To be honest, I can’t figure out how such important bugs are

were generally admitted
were not resolved in a timely manner

In my opinion, this functionality is one of the most important - activation push notification with data transfer. Looks like that was important only to me and the creator of this ticket.

novavision on Jan 12, 2021