Microsoft Edge with Chromium suddenly stops working with Google Meet (Update)

Updated April 26, 2022: Despite the current situation, Google says that it plans to back up Meet with Border on Chromium upon its release into general availability. In a argument to Neowin, a Google spokesperson said the following:

Nosotros view the increased adoption of Chromium and WebRTC equally positive for the entire Unified Communications industry. With the recent release of programmer previews for Border, we are thrilled to be able to offer a new preview feel of Hangouts Meet, and nosotros plan to officially back up it one time it becomes mostly bachelor.

Microsoft's new Edge browser based off the open-source Chromium Project and then far has had a peachy start with daily builds in the Canary ring, which then feed into the weekly release for the Dev channel.

However, former betwixt yesterday and today Run across, Google's spider web-based video and voice meeting service, stopped working. Users looking to join a Google Meet encountered a bulletin informing them "Run into doesn't work on your browser" with download links to Chrome or Firefox instead. (Even worse, in our Edge Dev build the tab but crashes when nosotros tried to log into the service).

Current fault message Edge (Chromium) users see.

Due to the early exam phase of Edge with Chromium one could chalk this upward to some changes on Microsoft's end – after all, that is the point of this open testing. However, the mistake of Run across appears to fall at the feet of Google instead.

By irresolute the browser User Agent to "Chrome – Windows" using F12 > ... > More tools > Network atmospheric condition > and reloading the meet.google.com website the service suddenly works.

Changing the User Amanuensis to "Chrome" for Windows fixes the issue.

That result suggests Google has fabricated a recent change on their terminate that blocks the new Edge browser from using Meet. Besides, Microsoft Edge Dev has non been updated in a week, yet it also suffers from this issue suggesting that any the trouble is it wasn't caused by a contempo update to the Canary aqueduct.

Interestingly, Microsoft has a unique User-Agent for its new Edge browser to distinguish information technology from the current one that'south native to Windows 10. Microsoft uses "Edg/75.0.131.0" with a noticeably absent "east" versus the standard "Border/18.18362" so that things similar this would not happen.

Top: Microsoft's new User Agent string. Bottom: Erstwhile Edge User Agent cord.

The question is – if Google did add "Edg/75.0.131.0" to its block list of Google Meet why did it do so? While it's easy to suggest malice, at that place could be other reasons every bit well. On the other hand Google does have a long history of such shenanigans making them hard to trust.

Microsoft Edge, Chromium, and Glimmer FAQ: Everything you need to know

For at present, users tin can spoof their User Agent to get around the issue with Google Meet, just we anxiously await to see if a more permanent fix happen first.

We've reached out to Microsoft for a annotate.

Xbox Insiders Update

This huge Xbox 'Quick Resume' update will requite gamers more control

Microsoft is adding a new feature to Xbox consoles, allowing y'all to permanently shop up to two games in a Quick Resume state at all times. The feature is heading out commencement to Xbox Insiders in the Alpha testing ring before striking the general public.

Source: https://www.windowscentral.com/microsoft-edge-chromium-suddenly-stops-working-google-meet

Posted by: grahamuncin1992.blogspot.com

Share this post