01-14-2019 09:24 AM
01-14-2019 09:24 AM
We are witnessing some strange behavior during the interaction between two of our users in Teams.
User A starts a new chat with User B. as soon as User A sends their first chat message to user B, the chat window switches to their last chat with a different user, and their chat with User B is completely gone from the sidebar.
User B receives the message, has a chat history in the sidebar with User A, and can send messages to User A. When said message is sent, User A will receive a notification pop-up, but their Teams application will not have a chat with User B anywhere in the sidebar. If User A once again starts a chat with User B, the chat will behave as if this was the first chat ever started with User B (blank chat, with "You're starting a new conversation. Type your first message below" message).
Has anyone seen this? What would you recommend?
Desktop Support Analyst
01-14-2019 09:49 AM
01-14-2019 09:53 AM
01-14-2019 10:14 AM
Unfortunately, we can reproduce the issue in both the client and the web version.
I've opened a ticket with Microsoft.
I'll post the outcome here, in case anyone has the issue.
01-14-2019 10:20 AM
01-17-2019 03:02 PM
01-21-2019 06:59 AM
Just spoke with Microsoft and they said this is a known bug. Will relay that to the developers. No ETA on fix time.
01-21-2019 08:34 AM
Yes, you are correct! User A can see and respond to the chat via the Smartphone app!
You're lucky; M$ Support is passing me through their troubleshooting steps :\
01-22-2019 12:41 PM
Update, there is a workaround to this issue:
1. In your Contact, click on the person you're trying to message
2. Don't type anything in yet
3. Click on the Add people button on the top right to add a third person to your conversation
4. Start messaging
5. Ask the third person to leave the group
6. From the Recent folder you'll see your conversation with your contact and could continue to use it
I think that is crazy but that's the only way to do this. Thank goodness that I'm the only person in the organization that has this problem and it is only with one contact. Otherwise, we're going to abandon ship. Stay tuned for updates!
02-21-2019 09:57 AM
Had a few users have this issue yesterday/today.
One specific chat between two people. For one user it works perfectly, for the other everything disappears immediately. Doesn't matter if it's the app, online, or mobile app. Had user A search for user B, as soon as he sent her a message the chat disappeared.
Used the workaround where we created a group chat for the three of us, and I left. That chat seems to be working, however their previous chat history is gone on his side.
Did you guys hear back from Microsoft about this yet?
02-25-2019 09:31 PM
Just had a call with MS support. Did some more diagnostics, gave them logs, ran Fiddler, nothing. Then the engineer asked me to send a file across to the user and that seemed to have fixed the problem. Steps below on desktop Teams
1. From contact list, click on a user that you're not having messaging problems
2. Then click on the user you're having messaging problems
3. On the top (below user full name), click on the File options
4. Drag a file to share with user (I used an image)
5. The first time didn't quite work or was delayed in getting it over
6. Tried sending the same image across again and that seemed to work
If the above doesn't work, try on the web app. Good luck!
03-07-2019 07:56 PM - edited 03-07-2019 07:59 PM
Case closed. This was an issue in the backend where the "threadType" is being incorrectly set to "Thread" instead of "chat". MS deployed to a fix to resolve the issue our company.
In my previous message, when diagnosing the problem, we had accidentally stumbled upon a fix, which was to upload an image to share with the user you're having chat problem. I guess following that clue, MS deployed a fix to our company. Support engineer was aware of this issue happening on other companies and applied the similar fix. Hope that was yours as well @JonathanClose @Ryan Clegg !
04-26-2019 07:38 AM
Hi. I just experienced what you described. How did you get it resolved?
06-05-2019 01:09 PM
06-05-2019 01:32 PM
@WillieChiu I read that, but I just experienced this issue with a new user in our organization, so I think the error might be back!