Recently, a simple yet terribly annoying bug is affecting everyone in the world.
When someone chooses to join a meeting using a browser, as Guest, Teams saves a cookie called “teamsAnonymousUserName.” This cookie is then used to auto-fill the username field everytime that person joins another meeting.
The problem here is that the latest update not only saves the username itself, but also writes two inverted commas (%22). This is a big problem because every time a user logs in, Teams adds another inverted comma and a “\” to the already existing inverted commas saved.
Cookie progress example:
0 meetings joined — Cookie content: empty
User joins meeting as: John (Guest)
1 meeting joined — Cookie content: %22John%20(Guest)%22 — "John (Guest)"
User joins meeting as: "John (Guest)"
2 meetings joined — Cookie content: %22%5C%22John%20(Guest)%5C%22%22 — "\"John (Guest)\""
User joins meeting as: "\"John (Guest)\""
3 meetings joined — Cookie content: %22%5C%22%5C%22John%20(Guest)%5C%22%5C%22%22 — "\"\"John (Guest)\"\""
etc., etc., etc.
After several meetings, we end up having users as "\"\"\"\"\"\"\"\"\"John (Guest)\"\"\"\"\"\"\"\"\"
Is there any way the Microsoft Teams team can take a look into this?
This is particularly serious for public meetings where the user name doesn't even fit the screen and, thus, is not visible (e.g. "\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\…).
