Forum Discussion
Potential bug: List view.
Additional information
This may be more complicated than I imagined, as it seems this is only an issue when you also had a pre-existing default team error, as shown below.
I'm not a Teams person, so I have no idea how to identify the inaccessible Team, or where such a setting would be specified/stored, given InPrivate mode ensures no configuration settings are stored between sessions (hence why I have to re-set up Teams from scratch every day).
The crosscheck (which I'll leverage as a workaround) I just ran entailed:
- Within the Teams application, choose the "Activity" sidebar option;
- Find a message related to a Team channel and select it;
- Click the channel link below the message title/heading;
- This takes you into the channel view, where "list view" works just fine thereafter.
I've had the initial post login inaccessible channel message for over a month now without any issue, so it can't be the sole cause for the Teams web v2 hang. But it's clearly an important aspect in conjunction with this month's Windows update.
Cheers,
Lain
Additional information
After step 3 (above), switching from Teams v2 ("new Teams") back to classic Teams - via the New Teams toggle under in the Settings and more menu - works flawlessly.
No issues/hangs with list view (which is the default layout mode in classic Teams) whatsoever.
This is a better workaround than the clunky one I outlined above, but it would be nice if someone could still test the original scenario.
Cheers,
Lain
This problem seems to have "magically" resolved itself in the past 30 minutes, as I can no longer reproduce the hanging issue.
Cheers,
Lain
I spoke too early, as the previous "magic fix" only lasted a day.
That's the same pattern I've seen in other issues where there's been underlying CDN issues, but apart from that one "magic fix" day, the list view fault's remained present.
Cheers,
Lain