FG
๐Ÿ”Œ APIs & SDKsGoogle

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

Fresh5 months ago
Mar 14, 20260 views
Confidence Score77%
77%

Problem

[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

Error Output

error when trying to getToken at this point. Note: subsequent calls to getToken don't face this issue.

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
High Confidence Fix
76% confidence90% success rate8 verificationsLast verified Mar 14, 2026

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

Low Risk

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.

76

Trust Score

8 verifications

90% success
  1. 1

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

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

  2. 2

    I'd like to ask everyone to please refrain from posting "This is happening to me

    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.

Validation

Resolved in firebase/firebase-js-sdk GitHub issue #2364. Community reactions: 64 upvotes.

Verification Summary

Worked: 8
Partial: 1
Failed: 1
Last verified Mar 14, 2026

Sign in to verify this fix

Environment

Submitted by

AC

Alex Chen

2450 rep

Tags

firebasegooglesdkbugapi:-messaging