search

mutesync / mutesync-browser-extension

Extends mutesync desktop app to web clients.
MIT License
8 stars 3 forks source link

Recent changes caused Google Meet to stop reporting status #2

Closed aav7fl closed 2 years ago

aav7fl commented 2 years ago

Hi. Recent changes made in c3d8a7262bf5dd547b957613ca8d39d10ccd5625 caused the extensions to stop working on my Mac with Google Meet.

I do see the Connected to mutesync server message (running against the Mütesync 5.0.6 desktop client). I'm wondering if there are issues with the triggering of the new socket.on("*") functions?

~My workaround was rolling back to bb0d3d0981cd283f6323d634530652d838ad4e02. Once I did that (built locally and manually installed to my Chrome browser) everything started working correctly for me again.~

My workaround does not seem to be consistent. See comment below.

aav7fl commented 2 years ago

I think I've spoken too soon. It appears to still be exhibiting the same behavior on the old build of the extension. It's very sparingly picking up on my Google Meet status when I'm in meetings. Maybe there was a change with Google Chrome recently. (Running Version 100.0.4896.88 (Official Build) (x86_64))

aav7fl commented 2 years ago

Chrome has been updated to Version 100.0.4896.127 (Official Build) (x86_64).

Mutesync extension has been updated to 5.0.1

Mutesync mac client is 5.0.6.

I still see the Connected to mutesync server log message in the console, but no reporting anymore. Did the labels change in newer versions of Google Meet?

AtiqGauri commented 2 years ago

unable to reproduce on macOS m1 machine with chrome: Version 100.0.4896.88 (Official Build) (arm64) mutesync app and extension are at the same version mentioned by @aav7fl

aav7fl commented 2 years ago

Hi. I'm on an Intel Mac (Monterey 12.3.1).

It started April 13 and it was happening sporadically. Starting today I was unable to get it to detect any meetings at all.

I had tried everything from fully restarting chrome, reinstalling the extension, restarting the app, restarting the monitoring, unplugging the button, and searching for any rogue mutesync processes.

Then I decided to reboot. It works now. Guess I'll never know why it stopped working.

Solution: I rebooted my Mac and it works.