Greg Sakakihara

This appears to be a bug as it's intended that opening a notification should log notification_open, if enabled. Unfortunately ActivityLifecycleCallbacks doesn't have a callback for onNewIntent(), so the FCM SDK...

Just to clarify, this isn't actually resolving any strict mode violations, right? This appears to be adding a new test to prevent any new strict mode violations from being added...

For anyone that is not receiving FCM data messages on your Android TV app, how are you testing this? In my tests an app was able to receive data messages...

What are you testing this on? Emulator or an actual device? What version of Android is it running?

Can you test it on an emulator?

Unfortunately, if you won't test it out on an emulator, it is difficult to determine if it's an issue with FCM or an issue with the device's implementation of Android....

A quick update. We're looking into seeing if we can make notification logging more seamless in cases like this, but there's a good chance that it could take some time...

The FCM team has previously looked into allowing developers more control over when and how notifications are displayed by the FCM SDK, but this doesn't fit into the current roadmap...

@Khudoyshukur Yes, `FirebaseMessagingService`'s `onDestroy()` can be called immediately after it has returned from `onMessageReceived()` in certain cases, so it probably shouldn't be relied upon to continue work after the message...

Pretty much what @Khudoyshukur said. Due to the way FCM message handling works on Android, your app is subject to being killed after you return from `onMessageReceived` and you should...