Community-edition: Microsoft Teams fails to load

[JPaulMora]

I've included the webpage logs, it loaded just fine the first time and reloading seems to break it.

Thanks
teams.microsoft.com-1566006529406.log

> Rambox 0.6.9
> Electron 4.1.4
> darwin x64 18.6.0

[welcome[bot]]

Thanks for opening your first issue here! Be sure to follow the issue template!

[kosi2801]

Ok, confirming issue is occuring since about a week.

Steps to reproduce

1. Set up a Teams account, login to teams and use as normal
2. Close/shutdown Rambox
3. Restart Rambox
4. Switch to Teams tab and login if required

Expected behavior

Teams shows up

Actual behavior

Only white background displayed in tab. Teams not visible.

ENVIRONMENT

Rambox: v0.6.9
OS: Linux Mint (5.0.0-23-generic)
Arch: x64

[noxer]

Some additional info

After a while (> 10 min) it displays an error page about problems to load Teams and offers to sign you out so you can sign in again. It does not help, though. Deleting the Teams tab and setting it up again helps until Rambox is restarted.

[noxer]

This seems to be a duplicate of #2375

[pietrushnic]

In developer console I see 3 warnings like this:

The FetchEvent for "https://teams.microsoft.com/_#/conversations/?ctx=chat" resulted in a network 
error response: a redirected response was used for a request whose redirect mode is not "follow".

[fhibler]

Confirming this bug as well on OSX.

[ZEROF]

HI,

Same here, white page. I think that you need to read this https://teams.microsoft.com/dl/launcher/attribution.txt, if not you can't use integration anymore. That is my guess.

[timeterror]

Hi,

I've been experiencing the same issue, but have noticed that if I open the developer tools, _delete the cache_, disable the cache (default), and enforce the _Edge - Windows user agent_ that it seems to work without the need for removing the Teams tab.
Reloading the tab a few times doesn't cause any issues, but sadly the problem does return as soon as the developer settings have been reset again. Luckily, the developer settings seem to linger for a single restart which requires this workaround only to be used every other restart (just be sure to keep the developer tools open until the teams tab has loaded).

[Tha-Fox]

I have the same issue.
Rambox: v0.6.9
OS: Arch Linux
Arch: x64

My laborious manual workaround:
1) Delete the cache
2) Remove Teams service
3) Add Teams

I'm not sure if it matters, but for me this started occurring around the same time when we enabled MFA.

[m-s-]

My routine is a bit simpler, based on the current waiting pull request:

• open developer tools for the Teams tab
• go to Application > Service Workers and Unregister
• Reload the tab

This way I don't lose the login information and can keep using it. Not sure if there's a way to inject a script to do this unregister step.

[noxer]

You can also use the custom script

Object.defineProperty(navigator.serviceWorker,"register",{value:()=>Promise.reject()});

Source: https://github.com/ramboxapp/community-edition/issues/2347#issuecomment-530483570

[requiem240sx]

I have had the same issue all month, we also have some very strict MFA (with okta) that I thought was the reason. Can confirm the above custom script fixed my issue, thank you very much! My sanity is restored!

[fvulich]

Fixed: https://github.com/ramboxapp/community-edition/commit/2de8e8e41b73ff2492813850b20f4bd5b0b46c3f

[kosli]

Teams stopped working for me in 0.7.0 (and 0.7.1), even with the custom script applied, which worked before in 0.6.9 :-(

[ZEROF]

Solution for Linux users:

1. Remove your Teams APP (you need to start over)
2. rm -rf .config/Rambox/Partitions/teams_*
3. Add Teams APP again

All working ok without script.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.