Microsoft Teams Mac OS client is not recognizing external cameras after updating to version 1.3.00.18164.

Anonymous
2020-07-24T04:03:58+00:00

Microsoft Teams Mac OS client stop recognizing external cameras (EOS Webcam utility, EpocCam, NDI client) after updating to version 1.3.00.18164; only MacBook Pro built-in camera is listed as available device.

※Update executed today (07/23) some hours ago.

Web app through browser (Edge) is OK, it kept external cameras listing and they work.

Does anybody had came across same issue after updating?

OS: macOS Catalina version 10.15.6

Microsoft Teams version: 1.3.00.18164

Microsoft Teams | Microsoft Teams for business | Teams for Mac

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2020-07-29T21:10:25+00:00

I had the exact same thing happen to me after updating to the latest version of teams.  However, I was able to come up with a solution that resolves the issue entirely.  It has to do with how Apple is starting to codesign specific apps to block 3rd party CoreMediaIO plugins.  If we remove that codesigning, then it will allow those 3rd party plugins to function again.

The fix is pretty simple.  First, completely exit out of Teams, then open Terminal and issue the following commands:

If you havent installed xcode previously, first run:

xcode-select --install

Then, run:

sudo codesign --remove-signature "/Applications/Microsoft Teams.app"

and:

sudo codesign --remove-signature "/Applications/Microsoft Teams.app/Contents/Frameworks/Microsoft Teams Helper.app"

Once you've issued those commands, open up Teams.  It should ask you for an administrator password to allow the (now) unsigned application to access your keychain.  Once entering your password and selecting, "Always Allow", the issue should be resolved. (At least until the next update to teams is released).

*****UPDATE*****

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"

******UPDATE #2******

I totally forgot about this thread and decided to take a look at it again. From the latest comments, it looks like a lot of you are already aware that this issue has officially officially fixed by Microsoft as of version 1.4.00.8872, so this workaround should no longer be required as long as you are up to date.

Source: https://docs.microsoft.com/en-us/microsoftteams/troubleshoot/teams-on-mac/virtual-camera-doesnt-work-macos

Was this answer helpful?

900+ people found this answer helpful.
0 comments

206 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-04-19T08:15:18+00:00

    This solution worked for my Mac Mini M1 with EpocCam virtual camera staightaway not just with Teams (1.4.00.8872.) but also with Skype.

    THANKS A LOT!!!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2021-04-15T12:21:52+00:00

    I found a very old way from a post in the middle of 2020. There told a guy that one should open up the invitation with SAFARI-Browser. And then choosing Web-Application of Teams, then the System will ask for admittance of cam and Microphone for Teams. This worked for me. That was the only way to start up the web-application proce4ss here for my Mac. So now I thinks it's ok.

    Uwe

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-04-15T12:13:14+00:00

    I opened a new thread for the issue(s?) introduced with the Teams app version 1.4.00.7175 for macOS:

    Problems with virtual cams introduced in Teams for macOS version 1.4.00.7175

    I think that they are not related to the rather old problem discussed here for months and months with two more or less suitable workarounds. (I have a strong feeling that nobody at Microsoft feels the need to fix that.)

    So please, when you experience the new problems (i.e. virtual cams are selectable with the known workarounds, but don't show an image at all or do so in the preview, but don't get transmitted), head over to the new thread and provide helpful additional context. I think we have two maybe related new problems here.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2021-04-15T11:39:45+00:00

    Hi Uwe,

    of course you can always start from scratch by simply uninstalling and reinstalling Teams. Since xcode seems to be installed on your system already, there is no need to execute "xcode-select --install" (as stated in the terminal message).

    Regarding the signature removal process : As of now, there is no other option available if you want to use your Teams installation with a virtual cam. If you are uncomfortable with using command line configurations, you could simply use the web version of Teams to make video calls, no problems there.

    That's not particularly right, there is another method, but with even more unwanted side effects: One can disable the whole code signing part of macOS's security system. In short: Boot up to the recovery (hold Cmd+R during startup until the apple appears), start a terminal there and enter csrutil disable. This disables the whole System Integrity Protection and that is never a good idea! Anyhow, after that, reboot normally. This method worked for me for a long time and I didn't have to repeat it after every update of the Teams app. For now, I am back to the remove-codesigning-method because I am the one who is asked by all collegues for solutions and I really don't want to advice them to disable the whole SIP. So I use the method I can advice to others. (More information about disabling the SIP in German can be found here: https://www.heise.de/mac-and-i/tipps/System-Integrity-Protection-SIP-in-macOS-deaktivieren-3946690.html )

    We don't have any M1-Macs so I cannot say whether both methods work there or not.

    All those methods don't affect the new problem introduced with 1.4.00.7175, where some or all virtual cams are selectable, but don't show an image or show a preview but the image is not transmitted.

    @UweFeldmann-Fikus You say that your Stream Cam doesn't work or doesn't show up at all. The Stream Cam is an external hardware camera, not a virtual camera. Both the solution from greghiggins3 and the one with disabling SIP in macOS entirely are targeting the problem that virtual cameras don't show up in the camera select list of the app an macOS since version 1.3.00.18164. It seems to me that you have another problem.

    Was this answer helpful?

    0 comments