firebase.messaging.getToken() edgecase when push notification is set back to default (ask)

[thomasmburke]

[REQUIRED] Describe your environment

• Operating System version: macOS Mojave Version 10.14.6
• Browser version: Google Chrome Version 78.0.3904.97
• Firebase SDK version: 7.0.0
• Firebase Product: Firebase Cloud Messaging

[REQUIRED] Describe the problem

The issue I have identified was introduced in version 7.0.0 of the firebase-js-sdk. I do not run into this issue in versions previous to 7.0.0. The issue occurs when a use grants notification permissions, gets a FCM token, then updates the notification permissions in the browser back to Ask (default), reloads the page, grants notification permissions again in Chrome, and get an error when trying to getToken at this point. Note: subsequent calls to getToken don't face this issue.

Steps to reproduce:

The problem occurs after taking the following steps:

• Call Notification.requestPermission() and user grants permissions

• Call firebase.messaging.getToken()

• Set notification permission in browser back to Ask (default)
  

• Call Notification.requestPermission() and user grants permissions

• call firebase.messaging.getToken()

• get DELETE https://fcmregistrations.googleapis.com/v1/projects/{project_id}/regis.../{FCM_token} 500 error and this specific error from FCM: "FirebaseError: Messaging: A problem occured while unsubscribing the user from FCM: FirebaseError: Messaging: A problem occured while unsubscribing the user from FCM: Internal error encountered. (messaging/token-unsubscribe-failed). (messaging/token-unsubscribe-failed)."

• call messaging.getToken() again

• get new token, no error this time.

Others have encountered this issue as well on Google Groups:
https://groups.google.com/a/google.com/forum/#!msg/firebase-developer-cuf/dGU1SnJ1cz0/GMa_WvWGBwAJ

Relevant Code:

The firebase javascript messaging quickstart encounters this issue:
https://github.com/firebase/quickstart-js/tree/master/messaging

Specifically, I think the update needs to be made here:
firebase-js-sdk/packages/messaging/src/controllers/base-controller.ts
Lines: 136-137

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[bjgrosse]

I also ran into this error just as the OP described.

[mindiii006]

I am also getting this issue.

[rommelpe]

Thank for the report. I was able to reproduce this using the quick start guide and filed an internal report (b/144697421).

I'm just wondering if you y'all happen to consistently facing this issue. There are times that I can only reproduce it on the initial load or upon requesting permission several times. Are there any particular patterns you notice that significantly contributes to the issue (aside from what mentioned)?

[thomasmburke]

Hi rommelpe,

This issue only arises after the a reset of notifications permissions and reload of page and then works properly with an additional reloaded pages. Aside from what I mentioned there are no other patterns that contribute to the issue identified.

Thanks, and let me know if there are any other questions.

[Nox04]

I'm getting the same issue when I remove the push notifications permission and reload.

[gherman-cs]

I am also getting this issue.

[thayannevls]

I'm getting the same error :(

[mmermerkaya]

Thanks for the report. I can consistently reproduce the behavior and I'm investigating the issue.

I'd like to ask everyone to please refrain from posting "This is happening to me too" comments and instead use the add reaction feature on the OP to add a thumbs up to issues that you consider important.

[TrackMyToken]

Any update on this issue?

[mmermerkaya]

Hello, sorry for the lack of updates. Looks like the problem is in our backend, but there wasn't much progress as we've had a code freeze last week (because of black friday). I should be able to give you a better update or even a fix later this week.

[NaghamHalabi]

Can we have the latest updates regarding this issue?