v9 api has no equivalent to GetToken in firebase/messaging/sw & is therefore impossible to use in Chrome Extension

[samdoeswork]

[REQUIRED] Describe your environment

• Operating System version: Windows10
• Browser version: Chrome latest
• Firebase SDK version: 9.0.0-beta.6
• Firebase Product: Messaging

[REQUIRED] Describe the problem

Steps to reproduce:

I am trying to use FCM to trigger onBackgroundMessage in a Chrome extension.

I found the API reference has methods specific to Service Workers (https://firebase.google.com/docs/reference/js/v9/messaging_sw) & was able to successfully call getMessaging in a chrome extension with manifest v3.

However there is no getToken() equivalent method - so it's not possible to target individuals.

In general I've spent hours trying to setup v9 api with Chrome Extensions manifest v3 and there is absolutely no documentation on this topic.

Relevant Code:

Here is my best effort. I cannot get onBackgroundMessage to actually trigger in any Chrome Extension scenario (manifest v3) & additionally cannot access tokens.

import { getMessaging, onBackgroundMessage} from "firebase/messaging/sw";
async initFCM() {
    const firebaseApp = initializeApp({ ... });
    const fcm = getMessaging(firebaseApp);
    onBackgroundMessage(this.fcm, (payload) => {
      console.log("Received background message ", payload); // never triggers
    });
  }

[zwu52]

@samdoeswork, thanks for reporting. Looking 👀

[zwu52]

@samdoeswork Sam,
It was intentionally to left out getToken from the sw entry. Getting token in old version of sw was buggy.

I have created a test extension with manifest

...
  "browser_action": {
    "default_popup": "popup.html"
  },
  "background": {
    "page": "background.html"
  },
...

and I am able to get a token with by calling getToken inside a popup script and receive messages. Have you tried calling getToken that way? (if you could share a repo I could look that would be helpful too)

Note: I have limited experience on extensions, interested in knowing your setup and use case

[google-oss-bot]

Hey @samdoeswork. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@samdoeswork if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.