Implement chrome.gcm API

Question

Implement chrome.gcm API

Closed this issue 4 years ago · 18 comments

Would it be possible for Edge to implement the chrome.gcm API so that extensions can receive push messages?

Answer 1 · 2020-02-11T21:28:56.000Z

Definitely this. It's a deal breaker for a lot of people, including myself. I would switch to Edge in a heartbeat if it wasn't for this.

Answer 2 · 2020-02-12T21:06:28.000Z

I second that

Answer 3 · 2020-02-17T07:20:52.000Z

Any news on this? I see that Edge is on v80 now.

Answer 4 · 2020-03-04T01:13:25.000Z

I was absolutely in love with Edge Chromium until I came to realize it was the root cause of me not being able to copy and paste between my phone and laptop anymore. @joaomgcd is a prolific developer, and Microsoft would be remiss to ignore this feature request.

Until then I'll be returning to Chrome. You were so close, Microsoft. 20+ years of IE hell almost forgiven.

Answer 5 · 2020-03-04T23:21:29.000Z

@joaomgcd , according to Google the chrome.gcm API is deprecated and the solution is to migrate to FCM. Is that an option? That page says the FCM SDK works on any browser that supports Push API which includes Edge 79 and 80 (the Chromium-based versions).

Answer 6 · 2020-03-06T13:50:12.000Z

I already migrated Join to FCM but Chrome still uses the chrome.gcm API to deliver the messages. They did not remove that part yet.
However the fcm SDK for javascript (last time I checked) doesn't support multiple registration tokens which Join needs to stay low cost as it is now...

Answer 7 · 2020-04-21T20:46:02.000Z

Sadly, I ended up here because of this exact issue. +1 for Microsoft correcting this.

Answer 8 · 2020-06-09T10:46:06.000Z

We do not have any plans of providing chrome.gcm in Edge because it depends on Google's push messaging service. The use of GCM requires developers to register with developers.google.com, which creates a secret used for authentication. This prevents us from standing up a Microsoft service that offers equivalent functionality since we cannot authenticate developers.

As an alternative, we request you to use service worker push messaging as a replacement for chrome.gcm in Edge. Service worker push messaging uses Microsoft’s push messaging service in Edge and Google’s push messaging service in Chrome. Both push services implement the same IETF standards so the push messaging services should work the same. Here’s a good reference for the same: https://web-push-book.gauntface.com/introduction/.

Answer 9 · 2020-06-17T06:52:20.000Z

We are closing this issue for now. If you think, there are some unanswered questions, please feel free to either reopen this issue or create a new one.

Answer 10 · 2020-07-10T02:19:19.000Z

This should be re-opened. Many addons need this or at least a workaround

Answer 11 · 2020-08-05T19:22:47.000Z

@Simpuhl as a workaround, we request you to use service worker push messaging as a replacement for chrome.gcm in Edge.
Is there a specific issue that you are facing that we could help with?

Answer 12 · 2020-08-05T19:25:11.000Z

@Simpuhl as a workaround, we request you to use service worker push messaging as a replacement for chrome.gcm in Edge.
Is there a specific issue that you are facing that we could help with?

I just started using Messages app and it works with Edge. So I am going to stop using the Join app

Answer 13 · 2020-08-05T19:52:07.000Z

Hi guys ! Glad to see this issue reopened, I am an avid Join user but not since it sort of shutdown when I switched to Edge. Now @joaomgcd is a great developer and as I understand it it requires chrome.gcm or something like that to keep the cost low.... I am not as experienced as he is. I would love to see this app work again, that makes me sad to see people dropping out of Join because of this compatibility issue. Thanks guys and much love Edge is a superb browser ! Hope we can resolve this soon enough. ;)

Answer 14 · 2020-08-05T19:57:32.000Z

Thanks to @joaomgcd, Join has been available for testing on Microsoft Edge for a few weeks now: https://www.reddit.com/r/JoinApp/comments/hbjagc/dev_join_on_firefox_and_edge_available_for/

Answer 15 · 2020-08-06T06:49:39.000Z

@darthShadow Thank you so much for your answer I didn't know about that and now I do and I'm hyped ! 😄🤙

Answer 16 · 2020-12-01T01:10:15.000Z

Please add this. The current work around is weird.

Answer 17 · 2021-01-27T07:07:47.000Z

I request you to reach out to us at ext_dev_support@microsoft.com. Can you help us with the specific use case and how this issue affects your extension on Edge browser? This will help us in understanding the need of the API and henceforth prioritize the work around it.

Answer 18 · 2021-02-09T17:14:48.000Z

We are closing this issue for now. We are tracking only documentation related queries here. For any product related queries, do navigate to the Contact us (https://docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/publish/contact-us) page and reach out to the Edge extensions team directly. Thank you!