Another possibility is that custom tabs is intercepting the FCM but not opening, and causing Chrome to not open either.

Matt, any idea?

Could you provide a code example of what you are sending to the FCM API?

Sadly the behavior will change depending on API call so would be extremely helpful.

Hi Matt. Here is how I'm making the call to the FCM API.


var firebaseAdmin = require('firebase-admin');

firebaseAdmin.messaging().sendToTopic(topic, payload).then(function(response) {
  console.log("Successfully sent message:", response);
  resolve(response);
}).catch(function(error) {
  console.log("Error sending message:", error);
  reject(error);
});

Could you provide an example payload?

Hi Matt. I am using strings for the notification in my payload. 

var topic = 'my fun topic';

var payload = {
  notification: {
    title: 'my fun title',
    body: 'my sample body',
    click_action: 'https://my-example-site.appspot.com/pages/my-page'
  }
};

What I think is happening:

If you use the quickstart demo it's a little easier to see the behavior: https://github.com/firebase/quickstart-js/tree/master/messaging

Steps to repro:

1. Get the demo working form quickstart-js
2. Open a custom tab
3. Using DevTools / Chrome://inspect, get the demo working on your phone
4. Send a notification with a click_action payload (The demo cURL command on the quickstart-js repo will do)
5. Hit home button on android device
6. Click on the notification
7. Notice nothing happens
8. Open tab and notice a message is received

What is happening is the logic in the messaging SDK is looking for open clients and focusing them. In the custom tab case, this is focusing the current tab, but it's not bring the app to the foreground on the device.

If you repeat the above steps but kill the app before clicking the notification, chrome is opened as you'd expect.

kelvincswatson@ -- Could you please update your Chrome to latest Stable #65.0.3325.109	and let us know you observations. Also, please revert to the Comment #9.

Thanks!

No feedback was received in the last 30 days from the reporter, so archiving this issue. Please re-open or file a new bug if necessary.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot