Forum Discussion
I can't switch back to Teams chat with Alt+Tab on Mac
Ok, I found a "solution" to force Teams to use the notifications.
Simple version:
01. You go to your teams https://teams.microsoft.com02. When it asks for notifications, give the permission and that's it.
As an App in your dock:
02. You copy the URL from your logged-in teams-tab (01.)
03. You install Epichrome
(Very useful, you can wrap a Website as a App and it appears in the dock. Basically is MS doing the same with their "App" except it uses Electron, Epichrome uses Chrome or Brave.)
04. Start it, go through the wizard, when it asks for the URL, give your Teams-URL and a fine name for it.
(Icon can be automatically downloaded)
05. Start the new app, log in, give permission for notifications. Since it is basically a browser, it is forced to use the default MacOS Notifications. Alt-Tab works again.
Alternatively, there is a way to make a WebApp with chrome. But I never use chrome.
As probably someone mentioned before, this is by design to be able to show "non-Mac-OS-native" notifications, even if the user is not on the same desktop/screen than the main Teams window. But this is simply a bad design decision. None of the previously suggested workarounds work for me - nor am I willing to use the in-browser version of the app. Using the [cmd] + [tab] + [arrow up] is what comes closest to an acceptable workaround, but this still means I have to remember handling MS Teams differently to any other app and this is disrupting my workflow anyway.
So my question is: Microsoft, can anyone please give a statement whether you're working on a fix for this issue or not? This is really frustrating and I think reducing frustration should really be of higher priority than new features. Just an opinion on general software development. 😉
Did anyone else find a solution that makes [cmd] + [tab] working again long-term for Teams in multi desktop setups?
renems yeah we did. The way to fix it is google SLACK and download it.
Love the irony that the fix name, fittingly describes the Teams developers response to this bug.