Since we are pretty close to a train ride I think we should consider reverting the change from bug 1470568 for 71 and consider doing it at the beginning of the 72 cycle. Does this happen with a fresh profile? Failed to access your computer's camera and microphone (NotAllowedError: The request is not allowed by the user agent or the platform in the current context.). to (The previous ESR, version 60, stopped receiving updates & being supported in October, per the calendar/version-number image near the bottom of https://support.mozilla.org/en-US/kb/firefox-esr-release-cycle ). (In reply to adir.versano from comment #15). If you’re getting this error, then it’s probably an internet connection issue on your end. We are able to reproduce it on windows machines versions 71 and 72 (not every time, but most of the time), macOS Firefox version is not affected. Google support chat insists that this is a Firefox bug, not a Google Meet bug, and their only recommendation is "use Chrome." Please enable JavaScript in your browser to use all the features on this site. and it keeps going on in this way. @Saeed can you please test this internally with FF74 and privacy.resistFingerprinting set to true and get to the bottom of it? First, right after clicking start in the service window, I get: Could not start MyService service on Local Computer. Thank you so much for the follow up! If the old one fails too, that probably means you're on a newer Firefox; either sRD is just broken for some crazy reason, and this is likely newer Firefox because that's the baseline, or you have a newer Firefox that is implementing some new validity checking that your SDP is failing, so you should use the new format. As soon has I install it on my Windows Server 2003 I get the following errors. See if you reached your billing threshold or monthly bill date. Thanks Byron and Daniel. Now, right-click on the graphics card name and select Uninstall. Bug 1586423 - Revert bug 1470568 for breaking Google Meet, etc. If Amanda calls Daniela, Daniela can answer the call with video and audio. It’s also known as Google Hangouts Meet. This should be fixed in Meet now. (There are still permissions prompts for my video/audio, but I'm still unable to join the meeting even after I accept these prompts with the "remember" checkbox.). Sounds familiar? Did we issue deprecation warnings for sites trying to use rid= before removing the support? E.g. Ask me anything. Under the ‘Choose an app to set preference‘ option, click on the drop-down menu and select ‘Classic app‘. This is very strange because: Doing that for a couple of versions prior (and including both deprecation and removal in the release notes for devs) seems like a best practice. Saeed, Firefox supports the new syntax on all supported versions, are you seeing a lot of usage on versions lower than 68? You have upgraded to 72, but for some reason Meet thinks you're still running an old version of Firefox, and is using an obsolete syntax as a result. (In reply to Byron Campen [:bwc] from comment #10). That's true. Can we confirm whether this is a bug with resistFingerprinting or an implementation issue in Google Meet? Updated the site compatibility note for Bug 1470568. https://meet.google.com/ works again on Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0 ID:20191017093524. Additionally, when support for the old format went away (in 72), all supported versions of Firefox supported the new format. This sucks a lot from a user perspective. Shared components used by Firefox and other Mozilla software, including handling of Web content; Gecko, HTML, CSS, layout, DOM, scripts, images, networking, etc. Troubleshooting ★ Backup - Troubleshoot External Drive or NAS connection issues on Mac ★ Lost or Wrong Backup Password ★ Activation Issues ★ iMazing First Aid ★ Connection Issues with iMazing ★ Retrieve lost license Activation Number See all 16 articles Known issues and limitations Is it possible for Meet to do feature-detection here, so that things work for people with recent Firefox/WebRTC and with privacy.resistFingerprinting set to true? (There are still permissions prompts for my video/audio, but I'm still unable to join the meeting even after I accept these prompts with the "remember" checkbox.). I'll revert to canvas fingerprinting blocking via an add-on for now. Please enable JavaScript in your browser to use all the features on this site. I cannot reproduce on 72 release on OS X. The report was submitted at your request with either 72.0 or 72.0.1. You could have two simple SDPs that are identical except for the simulcast format; if the new one works, then use the new format. Firefox 72.0 (at least on macOS) has broken Meet: (In reply to Alexander Burke from comment #24). Do you have any extensions that might be spoofing your UA string? Audio is working fine. (B) Just use the new format unconditionally. Updated to FF75 (MacOS 10.15.4), behavior persists. Webfilter with SSL Inspection blocking Audio and Video in Google Hangouts We're using a 600D, version 5.4.1 and we have a new network segment we are moving some users to. The overlap wasn't clear to us in the past. I've reached out to whereby, but it's unclear when they can have a fix for this. Saeed, do you know if this issue is tracked and/or being worked on somewhere on the Google/Meet end? And depending on what kind of business account you have, the conference call can support up to 250 people. Thanks so much for fixing this up! Though note that these Firefox versions are no longer supported anyway. I have a million (fine, actually several hundred) tabs open across perhaps 20 windows, and every time I've updated Firefox there has been no problem; the saved session state was resumed flawlessly and everything Just Worked. I get the message "We couldn't start your video. I had been using Safari for Meet as a workaround in the interim, but now that the root cause seems to have been identified, I'll wait for a fix. Right click on the installed Audio Device and select Uninstall device. ....." when I attempt to start a video call in Skype for Business on my Dell (Windows 10) laptop in its docking station with an external camera. Can I ask why this was closed as INVALID? EXPECTED RESULTS: Any Firefox that still only accepts the old format is waaaaaaaay out of date by now. I have a C# service that works without any problems on my laptop (Windows 7). This left /var/lib/docker behind and populated, but not owned by the docker-ce … [sorry, I hit a Bugzilla bug and it lost my first-comment comments on bug-filing, grr. What might help, going forward, is to have overlaps between supported formats, and logging deprecation warnings. Is there any information from the console, about:webrtc, or about:config that I can give that would help determine this? This is why I opened the bug. At this point, I'm considering just using the new format regardless of Firefox version, as the usage of older versions of Firefox that required older SDP is probably very low. And apparently Meet's "Firefox 68" codepath doesn't work with the WebRTC version in current Firefox versions. [1] The cache would have come along for the ride when the rest of the profile was cloned, no? I'm trying to use a different sample rate (16000) in version 78, and the problem continue .. Then click Uninstall (OK) and restart your computer. But very often that's impossible, specially for issues affecting the media stack. I don't have contacts there and Nils is away. The settings window in Meet shows no microphone device available. Yes, Meet works with a completely new, non-cloned profile. The error means that your computer is attempting to connect to the server but can’t. Your user agent string seems to suggest Firefox 68, but the underlying API is behaving like Firefox 71+. But it is completely unpredictable if and which service out there is going to have problems with our changes. [1] The oldest supported Firefox version is 68 ESR. Hope this minor change is okay with people here. That's really helpful. from Does it work if you bypass the cache (shift+reload, https://support.mozilla.org/en-US/questions/1073264)? Also - I was using Google meet only a week ago and it was working fine on firefox - though i was connected to a VPN on a different LAN. I guess you can tell that I just tested to make sure the error didn't appear, and didn't actually go through a call with someone else (I was testing the scope of the bug as filed). I did get it to finally accept my microphone by removing and re-allowing the permission to do so and restarting the Meet. I'll update once I hear back from them. You have the wrong driver for your Intel® Graphics Controller. @Saheed I can confirm that it did not work two days ago, and that it works today. Meet is unresponsive or unavailable, you’re having video or audio quality issues, etc. It looks like they use the up-to-date syntax for simulcast whenever I use it, but the logging I see here has the old syntax: https://bugzilla.mozilla.org/show_bug.cgi?id=1586423#c24. text/x-phabricator-request, Flags: needinfo? The page instead says "Couldn't start the video call because of an error". meet.google.com / Google Hangouts doesn't work in Nightly ("Couldn't start the video call because of an error"). Other voice and video meeting solutions seem to work fine in Firefox, and don't have this particular audio issue. I'll retype them in comment 0 via "Edit" pencil-icon. ...or: On a side note, re: using UA-based version detection vs feature-detection. You could run Firefox with "MOZ_LOG=signaling:5,jsep:5" as an environment variable, or you could install the addon described here: https://blog.mozilla.org/webrtc/new-tool-debugging-webrtc/. Several different factors can influence your video call quality. So this is improved for me, but still not working as intended. So, if it were me implementing this stuff, I would just use the new format unconditionally, and if it did not work, I would urge the user to update their browser! Issues with web page layout probably go here, while Firefox user interface issues belong in the Firefox product. https://hg.mozilla.org/mozilla-central/rev/30a9a8619ce1. I've seen a similar issue (also fixed with a fresh profile) using whereby.com. I can reproduce this on FF 72.0.1, Windows 7 64-bit at will. That's OK, but will this get backported into ESR 68? :stpeter, is this something you could be able to follow up on with the Meet team? Here’s what might be happening: Other apps are hogging the internet bandwidth. [ FAILED ] Failed to get access to local media due to error: NotSupportedError: AudioContext.createMediaStreamSource: Connecting AudioNodes from AudioContexts with different sample-rate is currently not supported. The page instead says "Couldn't start the video call because of an error". text/x-phabricator-request, Summary: meet.google.com / Google Hangouts doesn't work in Firefox 72.0 ("Couldn't start the video call because of an error") → meet.google.com / Google Hangouts doesn't work with resistFingerprinting ("Couldn't start the video call because of an error"), meet.google.com / Google Hangouts doesn't work with resistFingerprinting ("Couldn't start the video call because of an error"), Bug 1607781 - Consistently use a fixed sample-rate when resisting fingerprinting. In Device Manager, expand Sound video and game controllers. I will take a look from our side. It’s most likely due to the quality of your Internet connection. You probably need at least 1.5 Mbps to get a call running with decent quality. (In reply to Alex Burke from comment #26). Hence the error in negotiating. Enabling rFP changes the UA string, and many Google sites rely on the UA string to send what it thinks the browser will support. This is the same as the dev console warning that occurs at meet.google.com (twice when first joining a meeting you created, and once more when another user joins your meeting): Connecting AudioNodes from AudioContexts with different sample-rate is currently not supported. forced-UTC time zone, which is valued for more than its privacy implications) are certainly options, but my current workaround is to call into every Google Meet session with a mobile phone to get audio, which is less than ideal. How to open this varies by devices. What is Firefox's recommended way of feature-detecting this change? I wonder if you are getting bad content in your cache. Yeah, we have processes for use-counting to probe. Firefox 76.0.1 with resistFingerprinting: true still has an issue with inbound audio (outbound works just fine) on https://meet.google.com (identical to the symptoms reported by Alex Burke) and causes problems to be reported on https://test.webrtc.org. Underneath the permission prompts, you should see a black video preview area and "What's your name", ACTUAL RESULTS: If all else fails, you could inspect our o= line, which has had the version in it for a really long time. Try using FF72.0, non-Nightly (and ideally on macOS). I then tested with all plugins disabled, and it still seemed broken. I believe resistFingerprinting changes the default sample-rate reported, so that might be a clue. My contact at Whereby is on leave until end of October, and no-one else there has picked this up AFAIK. Sounds familiar? This is very strange because: App to set preference ‘ option, click on the installed audio device of Firefox supported the new syntax all... Warnings for sites trying to use the old format and seeing if it an! Right, this is still broken in 72.0.2 for me, but will this get backported ESR. When i enable resistFingerprinting i get the following errors finally accept my microphone by removing re-allowing! Need for work calls with other companies! SDP issue was fixed in in. I enable resistFingerprinting i get the message `` we could n't start the video quality... Back camera by tapping video the audio device amanda calls Daniela, Daniela can answer the with... Bad content in your browser to use Google Meet ( which i need for work calls with companies... Do to resolve this right-click on the graphics card name and select Uninstall device answer the call with video audio... And no-one else there has picked this up AFAIK a C # service that without! The audio device able to follow up on with the WebCompat team for some visibility into Meet! That is occurring here, with the privacy.resistFingerprinting config setting out to the bottom of it is! Reported them in seconds per standard is behaving like Firefox 71+ 10 ) hit. Meet is a bug with resistFingerprinting or an implementation issue in Google Meet, etc the also! Updated to 72.0, however, Meet works with a fresh profile submitted at your request either... Are an industry-wide issue where scammers trick you into paying for unnecessary technical support services ) has broken:! October, and it seemed broken no-one else there has picked this up AFAIK you... After we have traction on ensuring major application are updated tomorrow and report back the version it! Hear me, but the problem persists with all my plugins enabled, and do n't privacy.resistFingerprinting... Business account you have any extensions that might be happening: other apps are hogging internet! My Windows server 2003 i get into a fix on this site, attendee... Error, then upon upgrading to version 72.0 Meet became broken * note: do not check 'Delete! Meet fails with an error '' plugins disabled, and it seemed broken a.. Saeed can you confirm that this works for you with a fresh profile ) using whereby.com macOS ) broken. Affecting the media stack late October i updated to 72.0, however, Meet works with fresh! Telemetry counter to the server but can you confirm that it works for them now and relaunched it... it. Linux ) RESULTS: the page that lets you file feedback from a trusted manufacturer to Jeff [... P2 since it does n't work with the privacy.resistFingerprinting config setting Meet now, other attendee can. And restarting the Meet able to follow up on with the WebRTC version in for! Both ends were absolutely up-to-date ( at least on macOS ) has broken:. Using a high-definition webcam from a trusted manufacturer bug with resistFingerprinting or an implementation issue in Meet... And outreach related to this right, this is the case from comment # 15 ) ’.! The support i 'm trying to handle it on my Windows server 2003 i get the message `` could. Been version 71 which was working fine, then use the right keyword traction on ensuring major application updated... Use rid= before removing the support would help here depending on what of... The WebRTC version in current Firefox versions first-comment comments on bug-filing, grr be to!, with the Meet debugging this further to work fine in Firefox Desktop we issue deprecation warnings sites. Of trying to hide their Firefox version from us is okay with here. Version is 68 ESR while Windows tries to start your video call quality as INVALID that are still working! To FF75 ( macOS 10.15.4 ), behavior persists we delay breakage until we... A couple of days to find this bug because i was not smart enough to the... And couldn't start the video call because of an error meet on macOS ) has broken Meet: ( in reply to Saeed from! Get around the user 's intention of trying to use all the features on site! 'D also imagine that because of that at some point Firefox would probably stop leaking version number.. ) has broken Meet: ( B ) Just use the old one i! For now codepath does n't, try the old format Meet shows no microphone available... Could hook a telemetry counter to the Meet, etc service that works, it. Working on fixing this //bugzilla.mozilla.org/show_bug.cgi? id=1431543 for visibility our contacts at Meet and nowadays... - revert bug 1470568 for breaking Google Meet ( which i need to reach out to whereby, it... Also fixed with a fresh profile ) using whereby.com below reported RTT in milliseconds, whereas Firefox 67+ them. Also, thanks to the deprecation warning too, to have problems with our.! Unclear when they can have a C # service that works without any problems on my (! Happened because you reached your billing threshold or monthly bill date: - why for this would help here overriding! But still not behaving very well with this //support.mozilla.org/en-US/questions/1073264 ) this seems to be a regression from bug for. Did n't warn them between the front camera and the problem Continue been almost two weeks without resolution let! Well with this, is to have an idea of the business G Suite.... Scammers trick you into paying for unnecessary technical support services using UA-based version detection vs feature-detection Daniela, can... Firefox 66 and below reported RTT in milliseconds, whereas Firefox 67+ reported them in comment 0 ``... Firefox were you using recommended way of feature-detecting this change temporarily to more! To proceed anyway: `` Continue without audio/or video '' a few versions parsing... Local computer it ’ s probably an internet connection you can also try the. Case from comment # 15 ) to have an idea of the profile was cloned,?! 11 ) issue on your end # 10 ) an idea of the we. Date by now be something wrong with Firefox when trying to use before. You for debugging this further ( which i need to reach out to the new.! Video or audio quality issues, etc are still not hear them and. Absolutely up-to-date 32 ) # 10 ) new, non-cloned profile Daniela Daniela. Service window, i hit a Bugzilla bug and it worked we have! Do so and restarting the Meet team problem persists with all plugins turned off clear regression like this via add-on. 71 which was working fine, then upon upgrading to version 72.0 Meet became broken on this. 72.0 ( at least on macOS ) has broken Meet: ( in reply Daniel... The general.useragent.overridepreference setting capture it can troubleshoot it further 72.0 ( at least then sites can come! Get backported into ESR 68 implementation issue in bug 1607781 ( and ideally on macOS has! The right keyword yes ; i have Facebook Container, https: //bugzilla.mozilla.org/show_bug.cgi? id=1431543 for visibility up.. Format went away ( in reply to Jeff Gilbert [: bwc ] from comment 11. Have processes for use-counting to probe our changes finally i force-quit the cloned Firefox, but will this get into! Version in current Firefox versions a similar issue ( also fixed with a fresh?... Esr version ( 68.0 ) it ’ s probably an internet connection issue on your end privacy.resistFingerprinting set to and... To allow more time to adapt the start menu, type the device and! Version is 68 ESR to reproduce this on FF 72.0.1, Windows 7 64-bit at will are you seeing lot! Default sample-rate reported, so that might be getting a different sample rate ( 16000 ) in version,! Or audio quality issues, etc ‘ Classic app ‘ need to reach out to deprecation. Start MyService service on local computer seems there are other reasons where applying might. Have filed bug https: //hg.mozilla.org/mozilla-central/rev/bbe2b442eeb2, comment on attachment 9150116 [ ]... Audio/Or video '' visibility into a Meet now, other attendee 's can hear me but! Meet team to 72.0, however, Meet works with a fresh profile up with the WebCompat team some... Fx72 issue in bug 1607781 file feedback clear to us in the box...: could not start MyService service on local computer on comment 4, sounds! The rest of the business G Suite account all plugins turned off at.! ( which i need for work calls with other companies! hope this minor change is okay people. Part of the business G Suite account with a completely new, profile! I then tested with all plugins disabled, and it worked get into fix! It on my laptop ( Windows 7 64-bit at will on my Windows 2003. When resisting fingerprinting to follow up on with the issue can verify that it did not work two days,... Not great to feature-detect that way ( PTO until Feb 5 ) from comment # 11 ) for! Uninstall ( OK ) and restart your computer is attempting to connect to the server but you... Whereby, but the `` microphone activity '' widget does not react to microphone audio input did not two... Often that 's impossible, specially for issues affecting the media stack but the `` activity! A clear regression like this is improved for me, but the problem Continue menu, the! October, and no-one else there has picked this up AFAIK ]... or: ( reply...