"Classic Teams will soon be unavailable for use" warning header

[rslagmolen]

Describe the bug Since this morning, this build of teams start with a warning header : Classic Teams will soon be unavailable for use. To use the new Teams, update your browser to meet requirements or contact your IT admin. See requirements

NB: I'm still on 1.4.14 as the 1.4.15 is not yet in the AUR

To Reproduce Simply open the client

Expected behavior We should be on the new Teams (if possible)

Screenshots

Desktop (please complete the following information):

• OS: GNU/Linux - Manjaro (based ArchLinux)
• Installation package: AUR (it use the tar.gz source archive then build from source using "yarn electron-builder")
• Version: 1.4.14

[elhennig]

Same here, see https://github.com/IsmaelMartinez/teams-for-linux/discussions/1141

[jbauerrfid]

I am getting the same deprecation warning as well:

• OS: Ubuntu 22.04 LTS
• app: teams-for-linux 1.4.14, provided by snap

It would be sad to lose teams-for-linux, I really like it, and I don't want to use the PWA from Microsoft.

[bymck]

I have the same problem. Classic Teams will soon be unavailable for use. To use the new Teams, update your browser to meet requirements or contact your IT admin. See requirements

[ChristoSnake]

I used this method (shared in various threads here) to force Teams v2.

Right-click the Teams icon in the taskbar, then select the Debug option. Select the Console tab at the top of the debug screen. Type the following in the console at the bottom of the debug screen, then hit Enter:

document.location.href = 'https://teams.microsoft.com/v2/'

If that does not work, follow the same steps but type both of the following commands (with an Enter after each):

window.localStorage.setItem("tmp.isOptedIntoT2Web", true)
document.location.href = 'https://teams.microsoft.com/v2/'

It should automatically load Teams v2 after a restart..

[grizewald]

Same message for me, with the latest 1.14.15 version of Teams for Linux but fixed by the second set of commands in ChristoSnake's message. Thanks!

[christoph-teichmeister]

I used this method (shared in various threads here) to force Teams v2.

Right-click the Teams icon in the taskbar, then select the Debug option. Select the Console tab at the top of the debug screen. Type the following in the console at the bottom of the debug screen, then hit Enter:

document.location.href = 'https://teams.microsoft.com/v2/'

If that does not work, follow the same steps but type both of the following commands (with an Enter after each):

window.localStorage.setItem("tmp.isOptedIntoT2Web", true)
document.location.href = 'https://teams.microsoft.com/v2/'

It should automatically load Teams v2 after a restart..

The fix proposed by @ChristoSnake worked for me! Thanks a lot! :heart:

[elhennig]

I used this method (shared in various threads here) to force Teams v2.

Right-click the Teams icon in the taskbar, then select the Debug option. Select the Console tab at the top of the debug screen. Type the following in the console at the bottom of the debug screen, then hit Enter:

document.location.href = 'https://teams.microsoft.com/v2/'

If that does not work, follow the same steps but type both of the following commands (with an Enter after each):

window.localStorage.setItem("tmp.isOptedIntoT2Web", true)
document.location.href = 'https://teams.microsoft.com/v2/'

It should automatically load Teams v2 after a restart..

Works for me. Is this is change persistent?

[dom976]

How can the debug option be accessed from Gnome with the Flatpak app version?

[christoph-teichmeister]

How can the debug option be accessed from Gnome with the Flatpak app version?

@dom976

[madzaf]

How can the debug option be accessed from Gnome with the Flatpak app version?

In teams, you can also press Alt and a gnome window menu will appear. The Debug menu is in "Application"

[christoph-teichmeister]

Alternatively, in Teams, hit CTRL+D

[dom976]

Thank you all, I cannot see the icon in the toolbar because an extension hides it. Anyway, both CTRL+D and Alt trick work.

[mburkeSencon]

As per other comments, I had this issue on the 1.4.15 version. Using the steps @ChristoSnake put out has fixed the issue.

Thank you!

[riccardo94p]

I used this method (shared in various threads here) to force Teams v2.

Right-click the Teams icon in the taskbar, then select the Debug option. Select the Console tab at the top of the debug screen. Type the following in the console at the bottom of the debug screen, then hit Enter:

document.location.href = 'https://teams.microsoft.com/v2/'

If that does not work, follow the same steps but type both of the following commands (with an Enter after each):

window.localStorage.setItem("tmp.isOptedIntoT2Web", true)
document.location.href = 'https://teams.microsoft.com/v2/'

It should automatically load Teams v2 after a restart..

This worked for me as well, thank you! :1st_place_medal:

[ChristoSnake]

Works for me. Is this is change persistent?

Yes, it is.

Be aware that the taskbar icon will not show a notification count after switching. I'm using KDE's built-in notifications as a workaround:.

[jbauerrfid]

I can confirm https://github.com/IsmaelMartinez/teams-for-linux/issues/1156#issuecomment-2022136873 is working in the Teams snap on Ubuntu

Edit: it appears this also survives restarts of the Teams snap.

[jd-philips]

I'm getting this message in the web version under Linux. I'm on Fedora 39, Chrome 122.0.6261.128 (Official Build) (64-bit). The requirements page don't mention browser requirements.

[Bartwillemsen]

The fix of @ChristoSnake works and is persistent, until you log out to switch account. I am working from 2 Teams accounts and whenever I need to switch I also need to apply the V2 fix again.

Can't this fix somehow be integrated in Teams for Linux? Because without it, soon the application will not work out of the box.

[jd-philips]

I can't believe Microsoft is in the midst of removing ALL SUPPORT for Linux, even in the web version. Just goes to show that they haven't changed at all.

[jbauerrfid]

I see it in our company:

• all the management is working on Microsoft Windows and using Teams
• all devs are working on Mac or Linux (UI prefers Mac, and backend prefers Linux), they use mostly Slack, and Teams only if they must because they don't like it

so Microsoft should consider why this is the case...

[antimatter84]

I can't believe Microsoft is in the midst of removing ALL SUPPORT for Linux, even in the web version. Just goes to show that they haven't changed at all.

I am confused. Where did you get the info that they would remove all Linux support? I thought the PWA was created for all sorts of operating systems.

[jd-philips]

I am confused. Where did you get the info that they would remove all Linux support? I thought the PWA was created for all sorts of operating systems.

I'm on the web version and I still got that message. It may be just a technical mistake by Microsoft.. but this is the requirements page I'm pointed to: requirements and I see a lot of references to unsupported OS. Hopefully Microsoft clarifies this.

[christoph-teichmeister]

I'm on the web version and I still got that message. It may be just a technical mistake by Microsoft.. but this is the requirements page I'm pointed to: requirements and I see a lot of references to unsupported OS. Hopefully Microsoft clarifies this.

But if the fix suggested by ChristoSnake works for this Electron client, shouldn't you be able to just do the same in your browser and you're good to go again? :smile:

Microsoft is not necessarily dropping any support for linux, it is "dropping support" for the Teams classic version

[jmergy]

confirmed here the debug commands worked. I have multiple organizations in Teams and looks good. Debian 12.5 on XFCE

window.localStorage.setItem("tmp.isOptedIntoT2Web", true)
document.location.href = 'https://teams.microsoft.com/v2/'

[misha-grigorov]

I'm on the web version and I still got that message. It may be just a technical mistake by Microsoft.. but this is the requirements page I'm pointed to: requirements and I see a lot of references to unsupported OS. Hopefully Microsoft clarifies this.

But if the fix suggested by ChristoSnake works for this Electron client, shouldn't you be able to just do the same in your browser and you're good to go again? 😄

Microsoft is not necessarily dropping any support for linux, it is "dropping support" for the Teams classic version

Thanks for the idea. I can confirm that the fix works for Linux PWA as well.

[ChristoSnake]

I'm on the web version and I still got that message. It may be just a technical mistake by Microsoft.. but this is the requirements page I'm pointed to: requirements and I see a lot of references to unsupported OS. Hopefully Microsoft clarifies this.

It seems that they support Firefox (except WPA) and Chrome/Edge (including WPA):

This extension will do the trick if you really want to run it as a Firefox WPA.

[jd-philips]

But if the fix suggested by ChristoSnake works for this Electron client, shouldn't you be able to just do the same in your browser and you're good to go again? 😄

The issue is not whether or not the fix works, the fix should work in the browser though for the web app I'm assuming you load it from ms servers every time (more or less). The issue is: is this a sign that Microsoft is dropping Linux support altogether?

Microsoft is not necessarily dropping any support for linux, it is "dropping support" for the Teams classic version

The requirements page it is pointing me to isn't mentioning Linux or a path forward for me using their web app. It might just be confusing Microsoft language but it's suspicious.

[jd-philips]

It seems that they support Firefox (except WPA) and Chrome/Edge (including WPA):

This extension will do the trick if you really want to run it as a Firefox WPA.

where did you see this?

[jijojosephk]

Trust the devs here :smile: we'll find something out. The app will not stop. It will have the basic functionality. At least clearing the local storage and start over. The new teams will be loaded. But just like I mentioned you can do the basic things like in the web browser, we'll study the react implementation and fix the broken pieces. Until then relax :+1:

[jd-philips]

That's cute @jijojosephk but this repo is only a viewport for a Microsoft hosted application, if Microsoft really wanted to remove support for Linux no dev would be able to do anything about it. Changing useragents would not be enough if they really wanted to drop Linux or any other OS support. That was my concern because if that was their intention then we needed to raise awareness of it now not when it's a done deal.

[jijojosephk]

@jd-philips They can't never drop support for web browsers. The moment they drop support, this app will die. That's very unlikely to happen. So don't worry. We'll have some challenges but we'll see someone coming in who has knowledge in react and taking the torch and run forward. Sit tight!

[jijojosephk]

Meanwhile all can join the matrix chat group here: https://matrix.to/#/#teams-for-linux_community:gitter.im

[jd-philips]

@jd-philips They can't never drop support for web browsers.

That's not what I said, I'm talking about dropping support for Linux. They can drop support for Linux and still keep a web browser version. User-agent changes only gets rid of the most superficial checks which is why I said that if they really wanted to actively remove support for Linux (or any OS) they can.

[jijojosephk]

As long the web browsers are OS agnostic, how can they achieve that? All they did now is changed the technology stack of the teams app, from electron to webview2 and from angular to react. They want everyone to use teams that's why they provide web version of it. All their tech upgrades will not land in all OSes at the same time due to obvious challenges. Their priority as follows:

• Windows
• Mac
• Linux (This requires webview2 to be ported to linux) It may or may not happen. But they'll still have the browser variant so the teams-for-linux too.

[jmergy]

They will have to maintain browser access for all the various requirements they no doubt also have around various government and other considerations. I am just surprised they aren't even more doubling-down on browsers and platform-neutrality as they focus on their services revenue...

[ChristoSnake]

It seems that they support Firefox (except WPA) and Chrome/Edge (including WPA): This extension will do the trick if you really want to run it as a Firefox WPA.

where did you see this?

By following the link you provided earlier in the thread, specifically this tab :-)

[jd-philips]

As long the web browsers are OS agnostic, how can they achieve that?

Web browsers are multi platform, not OS agnostic so you have no idea what you're talking about. Web browsers aren't just html interpreters.

[jijojosephk]

From a websites's point of view they are. Don't you think so? Kindly stop fighting, that's not what we're here for.

[Bartwillemsen]

s not what I said, I'm talking about dropping support for Linux. They can drop support for Linux and still keep a web browser version. User-agent changes only gets rid of the most superficial checks which is why I said that if they really wanted to actively remove support for Linux (or any OS) they can.

But they are not going to drop support for Linux specifically. Nobody said they would. They are only phasing out Web Teams Classic in favour of Teams V2, which supports Linux. The only thing Teams for Linux needs to do is support that new version properly which it already does for the most important things.

[jijojosephk]

We're together in this!

[jd-philips]

From a websites's point of view they are.

That's only true if the developer of the website doesn't care enough to do a real check.

Kindly stop fighting, that's not what we're here for.

I'm not fighting. You replied to me and keep replying to me with an uninformed take and I'm correcting you.

[jijojosephk]

Probably we're looking at the topic from different point of views. It would be great if you can share your view on Multi Platform and Platform Agnostic. We must not say "I'm informed and you're not!"

[jd-philips]

If you can't tell the difference between the two why are you arguing? Your time would be better served reading rather than hijacking this issue with (yes) your uninformed take.

[jijojosephk]

Oh nice! I'm not hijacking. I've been helping teams-for-linux community for more than 2 years. These forums are for sharing knowledge and helping each other and not to show off your ego and superiority complex. I know you'd write something on top of this. Keep going! I'm done.

[rekyuu]

This is a GitHub issue, not a forum. Please take irrelevant discussion to a chat room so the discussion can remain focused on the issue.

[jijojosephk]

@rekyuu This is not an issue with team-for-linux. It can't be labeled so, if the dev can't do anything about warnings.

[ogghi]

I used this method (shared in various threads here) to force Teams v2.

Right-click the Teams icon in the taskbar, then select the Debug option. Select the Console tab at the top of the debug screen. Type the following in the console at the bottom of the debug screen, then hit Enter:

document.location.href = 'https://teams.microsoft.com/v2/'

If that does not work, follow the same steps but type both of the following commands (with an Enter after each):

window.localStorage.setItem("tmp.isOptedIntoT2Web", true)
document.location.href = 'https://teams.microsoft.com/v2/'

It should automatically load Teams v2 after a restart..

Second option with the 2 commands works just fine over here, after an allow pasting :+1: Thanks!

[sin-ack]

I used this method (shared in various threads here) to force Teams v2.

Right-click the Teams icon in the taskbar, then select the Debug option. Select the Console tab at the top of the debug screen. Type the following in the console at the bottom of the debug screen, then hit Enter:

document.location.href = 'https://teams.microsoft.com/v2/'

If that does not work, follow the same steps but type both of the following commands (with an Enter after each):

window.localStorage.setItem("tmp.isOptedIntoT2Web", true)
document.location.href = 'https://teams.microsoft.com/v2/'

It should automatically load Teams v2 after a restart..

Thank you for this, it worked :) Do you know whether this has any unintended side effects?

[ogghi]

Seems running just fine here! Also after restart etc.

[sekurilabs]

I used this method (shared in various threads here) to force Teams v2. Right-click the Teams icon in the taskbar, then select the Debug option. Select the Console tab at the top of the debug screen. Type the following in the console at the bottom of the debug screen, then hit Enter: document.location.href = 'https://teams.microsoft.com/v2/' If that does not work, follow the same steps but type both of the following commands (with an Enter after each):

window.localStorage.setItem("tmp.isOptedIntoT2Web", true)
document.location.href = 'https://teams.microsoft.com/v2/'

It should automatically load Teams v2 after a restart..

Thank you for this, it worked :) Do you know whether this has any unintended side effects?

You won't see notification counter on the icon in panel. Or any kind of notification.