May 06 2021 04:29 AM - edited May 06 2021 04:47 AM
Hello
We have a problem with Microsoft Teams breaking down. After logging in to the client's scope (switching the team from main 'company' scope to client Team), the application turns off and then returns to our scope. Operating system is Linux Ubuntu 20.04, Teams for linux application. The same is true for the different versions of the teams app from 1.3.00.25560 to version 1.4.00.7556.
So in other words:
We open Teams application, login to main account (confirm with SMS OTP), then I change Team (scope) from company-team-scope( MyCompany), to client-scope (CompanyX), the application closes, opens again, asks for login confirmation (in the Authenticator), the Teams window with correct client (CompanyX) scope, I see all messages, Teams, Activity, etc. BUT the windows closes itself in 1 second, and login-back to MyCompany main account Team scope.
So regardless of my initial skepticism, I did provide answers as follows:
Ctrl + Alt + Shift + 1
Fri Apr 16 2021 11:14:38 GMT+0200 (Central European Summer Time) <14721> -- info -- Logout event occurred due to reason:userStorageMisMatchWHY does it happen? What do you see in the logs on the server side?
If you are from Microsoft or Techdata, this is the support case:
We would like to inform you that your [Techdata Cloud Support Services (CSS)] Support Request 129838 regarding issue "Microsoft Teams problem in Linux Ubuntu" has been escalated to Microsoft and an engineer will be in contact with you shortly to work on the issue reported. MSFT SR# 25334458
Logs
I can provide you with any logs
or
.config/Microsoft/Microsoft\ Teams/logs.txt
Just please tell me if I should obfuscate any confidential information.
Update:
I did find a machine with Windows operating system - as expected - switching client context works with Windows desktop Teams application.
So the problem may be with
1) something on Linux app,
2) change in Teams API that is not reflected in Linux App
3) error on Teams SERVER side, like some account parameter or sth
Update2:
I did try 3 different machines, 4 different operating systems
Ubuntu 20.04 (here Teams were working until 15.04.2021)
Ubuntu 18.04 (here Teams were working until 15.04.2021)
Ubuntu 18.04 (another PC, fresh Teams - not working)
Windows 10 (works)
so I think it is not a case with a cache, or having 'factory default' installation.
Offtopic:
I was told that Teams for Linux have no support, and that I should reach out personally to MS developers.
I hope this is the correct place!
I heard that Microsoft ❤️ Linux
This seems to be far from the truth.
Please look at this situation like a professional. You sell a product, force clients to use it (one way or another), then when it breaks, you say "not my problem".
Give someone 4-leg chair, and when one leg breaks, make him continue sitting on 3 legs, or tell him to find a solution, without providing any help.
I do not ask for much, I just ask you to do your job - check the Server side logs, check if everything is on with the account on the Server side, check if you did not BREAK YOUR API (as this happened in the past).
May 07 2021 01:42 AM
May 11 2021 12:28 AM
May 11 2021 04:03 AM
Jun 05 2021 01:53 PM
Jun 05 2021 02:08 PM - edited Jun 07 2021 02:42 PM
I also had no luck with the "clear cache" snippet.
A few other things I tried:
The only other clue I see is this error in my logs :
Sat Jun 05 2021 17:50:13 GMT-0400 (Eastern Daylight Time) <23633> -- error -- Error saving cookie
Maybe teams is trying to update the sqlite db in ~/.config/Microsoft/Microsoft Teams/Cookies and having a problem? The file permissions look fine: 600.
For now I'm using the browser client, but this is a bad workaround.
Jun 12 2021 02:04 PM
Jun 29 2021 07:19 AM
Same here, still does not work.
My guess is that M$ did change something on the API SERVER side, and the linux client is not compatible.
I'd really love to hear some answer from MS developer, OR M$ support member who know what Linux operating system is....
It is a shame, that M$ have no support team that understand linux, one want's to ask - how they develop Azure....
If anyone from M$ reads it, please forward the ticket to someone who can check Teams logs on the server side, or Teams developer...
Jun 29 2021 09:35 AM
SolutionJul 02 2021 05:30 AM
For me the log-in is not the problem
I'm able to switch to Guest organisation, but the app log-out itself within 1 second and revert to my main organisation scope 😕
As there are some messages about null token I guess there is an issue passing some authorization data
So this did not work...
Jul 12 2021 01:43 PM
Jul 17 2021 11:55 PM
Jun 29 2021 09:35 AM
Solution