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 No 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 No comments

206 additional answers

Sort by: Most helpful
  1. 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 No comments
  2. Anonymous
    2021-04-15T08:25:28+00:00

    Mope, even the web-app in Microsoft Edge on my new M1 Mac doesn’t detect the cam.

    So with now over 5 hours complaining about negative tests and system tweaking I simply have got the meaning, that Microsoft Teams sucks.

    Perhaps they should ask the colleagues from Skype how it works?

    There is no chance to see a preference for Mic or Cam in the preferences.

    It simply hasn’t got the Menu part for Hardware

    Uwe

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-04-08T10:24:53+00:00

    Thank you so much! Its so sad that such a big company is not able to fix this issue over years....

    There are so many problems, like cmd+ tab is not allways working...but Microsoft dosent care ... I wish Slack would buy Teams :D

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-03-30T14:36:56+00:00

    Iriun, EpocCam and the NDI virtual camera all three work on my MacBook, regardless if I use the SIP-method or the one with disabling Team's code signature to make virtual cameras appear in the list. The only thing that fails for me is the virtual camera of OBS Studio 26.1 and that only fails to send a picture, but has a working preview. This new problem started with the update to 1.4.00.7175.

    Maybe we have two different problems with the 1.4.00.7175 version, as you and others described a blank screen when a virtual camera is selected.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments