An API this library relies on will be turned off June 20, 2024

[RandomEngy]

This library calls https://fcm.googleapis.com/fcm/connect/subscribe for the final FCM subscription step, which I confirmed with the Firebase team to be slated for removal on June 20, 2024. This is not in the explicit list of URLs affected but is considered part of the "Legacy Web SDK".

[KillTrot]

Do you have any official ressource for that, where I can find more information and needed changes?

[RandomEngy]

I linked to the official resource...

[developerfromjokela]

Hmm, that's troubling. Did firebase team advise to which API endpoint we should change to keep it running? @RandomEngy

[RandomEngy]

They did not. They referenced this guide to setting up FCM on a web app. I think the best bet right now is adapting from the firebase-js-sdk source code.

Per our engineers, the endpoint https://fcm.googleapis.com/fcm/connect/subscribe is included in the list of APIs that will be deprecated. It's part of Legacy Web SDK, although users may call it directly before. For now, I think you'll need to use FCM Web SDKs for obtaining FCM registration tokens.

I've also filed a request to include the endpoint in our FAQ page to avoid confusion moving forward. Let me know if there's anything else I could help you with.

[saenzramiro]

Any updates on this?

[RandomEngy]

I took a stab at this today and decided I'm going to give up and use Amazon SNS for my desktop apps instead of trying to get FCM working. It has actual support for running in NodeJS and Rust. Fixing this library would mean implementing the web push protocol from scratch.

[alchemicas]

Hello! Given that this library seems to not be supported by the author anymore, it's using soon-to-be deprecated APIs and has various bugs accumulated over time, I decided to write my own version.

It does everything that push-receiver already does and a little bit more. For the people who are going to migrate to my library, there is also a function exposed for retro-compatibility that subscribes to FCM using the sender ID.

Documentation: Aracna FCM Docs
Source: Aracna FCM Source

[RandomEngy]

Oh heck yes. I was looking more into SNS and it's not really a good replacement for proper push. I think I may actually be able to save push notifications in Rust/Tauri and update fcm-push-listener by following this library.

[saenzramiro]

@alchemicas Sounds interesting! Thank you for sharing your library. Does it support Electron?

[developerfromjokela]

@alchemicas is there a possibility to not use FCM credentials like in this library? Or has the methodology changed in new API?

[alchemicas]

@alchemicas Sounds interesting! Thank you for sharing your library. Does it support Electron?

Hi @saenzramiro , yes it does work with Electron, only on the main process of course.

@alchemicas is there a possibility to not use FCM credentials like in this library? Or has the methodology changed in new API?

Hi @developerfromjokela , I can't give a 100% accurate answer because we're always talking about APIs that are not documented anywhere by Google, everything that is inside these libraries is an effort of reverse engineering. Having said this, the way the latest Firebase js sdk does things is with a new registration endpoint that requires an auth token generated with Firebase API Key, App ID and Project ID.

Maybe, and I say maybe, we could find an alternative way by reverse engineering the API calls made by native apps using FCM, but the way the web sdk does things is what's currently in my library.

If you're worried about exposing your Firebase api key, I'm pretty sure it's safe to have out in the open 👍

[developerfromjokela]

@alchemicas can I use sender ID argument? I have a third party service I want to receive push notifs from, with push-receiver i just put it there and it worked. In arcana i coudln't quite figure out.

[alchemicas]

@alchemicas can I use sender ID argument? I have a third party service I want to receive push notifs from, with push-receiver i just put it there and it worked. In arcana i coudln't quite figure out.

You can @developerfromjokela , just use the subscribeToFCM function. But by June you'll have to figure out a way to leverage the new APIs and generate tokens through registerToFCM.

If you already have a sender id you should also be able to get the firebase config somehow if you do have access to the firebase console.

[developerfromjokela]

@alchemicas can I use sender ID argument? I have a third party service I want to receive push notifs from, with push-receiver i just put it there and it worked. In arcana i coudln't quite figure out.

You can @developerfromjokela , just use the subscribeToFCM function. But by June you'll have to figure out a way to leverage the new APIs and generate tokens through registerToFCM.

If you already have a sender id you should also be able to get the firebase config somehow if you do have access to the firebase console.

I just tried with both registerToFCM and subscribeToFCM and none of them receive notifications. But using push-receiver notifications get delivered.

[pedroGitt]

It does everything that push-receiver already does and a little bit more. For the people who are going to migrate to my library, there is also a function exposed for retro-compatibility that subscribes to FCM using the sender ID.

Documentation: Aracna FCM Docs Source: Aracna FCM Source
@alchemicas

• I just went through your documentation.. what is exactly the YOUR_VAPID_KEY ? The public key we generate from the "Cloud messaging" tab in the "Web Push certificates" section?
• One could have expected a symmetrical use of ./google-service-account.json file from sendFcmMessage() in registerToFCM(),
• I'm going to try your lib.. nice job!