Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When waking from sleep, messages don't get updated #1524

Open
nfp0 opened this issue Dec 16, 2024 · 2 comments
Open

When waking from sleep, messages don't get updated #1524

nfp0 opened this issue Dec 16, 2024 · 2 comments

Comments

@nfp0
Copy link

nfp0 commented Dec 16, 2024

Describe the bug
When I put my computer to sleep and then someone sends me messages on Teams, sometimes those messages don't show up when I wake the PC up, even after the network connection is re-established.

Further incoming messages do show up though, placing the chat in an inconsistent state (missing messages).

If I press CTRL+R to reload Teams, the missing messages show up and everything goes back to normal.

This is not 100% reproducible every time, which makes me thing it might depend on how fast the PC can restore the network connection after waking up.

To Reproduce
Steps to reproduce the behavior:

  1. Open Teams.
  2. Put PC to sleep.
  3. Ask someone to send you a message while the PC is sleeping.
  4. Wake PC from sleep.
  5. Notice that the message does not show up on the chat.

Expected behavior
The messages should show up as soon as the network connection is re-established.

Desktop (please complete the following information):

  • OS: Arch Linux
  • Installation package AUR
  • Version 1.12.3

If you believe it can help, I can provide logs the next time it happens.

@IsmaelMartinez
Copy link
Owner

Hello @nfp0 , Thanks for reporting

I think this might be a Microsoft thing as I think am seeing a similar behavior in the official MacOS app. For the last few days I have more messages in my mobile than in the desktop app, and old messages only appear (and as seen) after I log out and re-open the app.

Can you try and see if you also see this issue in a browser tab (using a chromium base browser)?

@nfp0
Copy link
Author

nfp0 commented Dec 18, 2024

@IsmaelMartinez Yes, I will keep a browser tab open for a few days to try and see if the same behavior happens there.
I'll report back as soon as I notice anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants