Latest Teams update breaks Virtual Cameras - Microsoft Teams Version 1.3.00.18164
Mac OS Catalina 10.15.5 - Just prior to the update to 1.3.00.18164, Teams was able to utilize my OBS and Wirecast virtual cameras which I use all the time. Now Teams doesn't see them and yep, the permissions for screen recording, etc are all accounted for and I disabled and re-enabled the settings, as well as restarting the app(s), including Teams, etc. and the machine. Previously, I was able to choose the appropriate virtual camera. Now I only have access to the Mac's built-in webcam. Obviously, this is not ideal.
The version that did work for sure was 1.3.00.15561.
Thank you for your reports on this. Microsoft is working to re-enable secure support for virtual camera apps on the Mac client. Until then, you can use the virtual camera in Teams in Chrome or Edge on your Mac.
We will update here and at the link below when there is more news: https://docs.microsoft.com/microsoftteams/troubleshoot/teams-on-mac/virtual-camera-doesnt-work-macos.
The page linked says "This issue is fixed in Teams client for macOS version 1.4.00.8872 and later versions," but I have updated and the cameras still do not show.
Rafal Lukawiecki commented
@Jay Chrome. The reason this has not been resolved after a year of waiting and over 776 votes is because Microsoft do not care about non-enterprise users or indeed anything that doesn't increase your Azure spend. Zoom has won this battle and Teams will only get worse. Teams is increasingly failing "normal" users with its poorly managed authentication and authorization and a myriad of usability design mistakes especially concerning scheduling and managing Teams calls. History of incompetence repeats itself: MSN Messenger, Windows Messenger, Skype, Skype for Business, Lync, and now Teams. Adieu.
Jay Chrome commented
May 7, 2021: Microsoft has still not sorted this out after 10 months. Why does it take so long to solve this simple issue?
Guy F commented
Alex (Teams Engineering) No it doesn't work in Chrome!
How long is it going to take Microsoft to sort this!!!
Peter Ringelmann commented
+1 please fix. This is very annoying given that Teams is the only application I currently cannot use with my webcam setup.
The signature removal works for me without a problem even in new versions, but doing that seems risky, making this delay from the MS team even more irresponsible, cause people are kind of using this a lot now.
Could you at least provide an update on the issue, and please refrain from any usual customer service nonsense without substance, there has to be a clear reason why this still has not been addressed just because we are M$ and we can choose to ignore this problem.
We are still awaiting for an official solution from Microsoft.
How long does MS need to fix this? We are now 7 month + since the reply from Alex, and still no solution that I am aware of.
An update from MS would be highly appreciated.
Please fix this as a matter of priority. We can no longer use Teams while this persists.
I really require an update to this. The sudo terminal cmds seem to have broken using a Dante AVIO USB adaptor as my microphone and speaker.
Update: Fix below ist NOT working anymore for me on macOS Mojave (10.14.6) with Teams version 1.4.00.7175, using Iriun Webcam. Previous version 1.4.00.4971 still works.
Can anyone confirm this? After having removed all signatures from 7175 as listed by @TehIndianSpartan, Iriun Webcam is listed in Teams settings but only shows a black screen.
I found a workaround. greghiggins3 found it.
As of version 1.3.00.28778 the process has changed and the above workaround is no longer valid. In order to get this fix working on the latest version of Teams, additional commands will need to be entered. Keep in mind, these commands are relative to where you have Teams installed, so if it is in a different location, you'll need to adjust the file path accordingly. So as it stands currently here are all of the commands (must be entered one by one and not pasted in one big block) that will need to be entered:
xcode-select --install (only if you haven't already)
sudo codesign --remove-signature "/Applications/Microsoft Teams.app"
sudo codesign --remove-signature "/Applications/Microsoft Teams.app/Contents/Frameworks/Microsoft Teams Helper.app"
sudo codesign --remove-signature "/Applications/Microsoft Teams.app/Contents/Frameworks/Microsoft Teams Helper (GPU).app"
sudo codesign --remove-signature "/Applications/Microsoft Teams.app/Contents/Frameworks/Microsoft Teams Helper (Plugin).app"
sudo codesign --remove-signature "/Applications/Microsoft Teams.app/Contents/Frameworks/Microsoft Teams Helper (Renderer).app"
Microsoft sort this out. Beyond a joke now
Why is this still not Resolved. This Simply is unacceptable. The browser version is a horrible workaround.
Microsoft needs to resolve this ASAP.
This is simply unacceptable behavior from Microsoft side, this makes the product simply unusable.
@Joerg K. You're answer is undeservingly unnoticed, it works, thanks so much! People check out Joerg K.'s comment at January 21, 2021 8:00 AM - it's a good workaround.
Ronald Jacobs commented
By the way, using the browser version is NOT an option and not a good work-around. The browser version of Teams has too many other limitations during meetings such as the maximum number of participants that are visible. Also very important for teachers.
Ronald Jacobs commented
Extremely bad situation that it takes more than 6 months to fix this. In our company this has been the reason for all teachers to move to Zoom. It takes to long for such a simple thing to fix it. Microsoft get your priorities straight and fix this ASAP!!!!!
This is kind of absurd that this isn't fixed.
Neil Despres commented
This also seems like it broke virtual microphones, like Krisp and Background Music, 2 apps I use for noise filtering and audio mixing.
Brad Kennedy commented
Any update at after 6 months?