Share via

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
  1. 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

    900+ people found this answer helpful.
    0 comments No comments

206 additional answers

Sort by: Most helpful
  1. Anonymous
    2020-07-27T20:25:59+00:00

    This issue is not fixed by unplugging the camera or a system restart. The only way to fix it is to install an older version of teams, though it is broken within 24 hours because Teams automatically updates to the broken version.

    This COMPLETELY breaks Teams for me, and makes it impossible for me to use Teams for group trainings (which can be in upwards of 100+ participants). I don't want to switch to Zoom, but I will have to if this is not resolved shortly.

    The worst part is that this issue happened in skype a few months ago. Why is it that Microsoft is breaking the most important feature for many of us who are having to do large-scale employee trainings from home?

    10+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-07-27T10:07:28+00:00

    Hello Grace/Microsoft,

    I am having the exact same issue using Mac Book Pro running OS: macOS Catalina version 10.15.6 and Microsoft Teams version: 1.3.00.18164.

    After this version update, suddenly Teams and Live Events is not recognising 'virtual cameras' NDI etc exactly as the other user Víctor JonathanLara Sánchez, above....was working fine before the update.

    This is a HUGE issue and there is a growing community online with the same problem....tried to uninstall and unplug  and restart and nothing worked....I checked with someone who has same Mac Book Pro and OS software as me but is running 'previous version of Teams before version: 1.3.00.18164. and everything is working fine...so the issue is with this Teams version update (version: 1.3.00.18164.).

    Can you URGENTLY advice when a fix is coming....basically I have had to stop my production in Teams because of this, please urgently address.

    thank you kindly,

    David.

    10+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-08-04T15:19:14+00:00

    Thanks for sharing @greghiggins3.  Your fix worked for me! 

    Anyone who is affected by this, please vote up the user voice bug here: 

    https://microsoftteams.uservoice.com/forums/908686-bug-reports/suggestions/40961347-latest-teams-update-breaks-virtual-cameras-micro

    10+ people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2020-07-30T00:38:49+00:00

    Excellent advice greghiggins3! 

    Your simple fix using Terminal commands above has worked to resolve my issues. Thank you ever so much for posting this.

    8 people found this answer helpful.
    0 comments No comments