You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was sending identical messages to different people
Expected behaviour
I expect to be able to send messages reliably without any issues. In the event of an error, I should receive an error message rather than being logged out and having my messages deleted.
Actual behaviour
Yesterday, I was sending identical messages to clients using Telegram Lite version 5.5.5 on macOS. At some point, I was automatically logged out from all sessions. After logging back in, I noticed that all the messages I had previously sent were missing. This is highly unsatisfactory as clients did not receive important information on time. Please address this issue and suggest possible solutions to prevent such occurrences in the future.
Operating system
macOS 14
Version of Telegram Desktop
5.5.5
Installation source
Static binary from official website
Crash ID
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
Steps to reproduce
I was sending identical messages to different people
Expected behaviour
I expect to be able to send messages reliably without any issues. In the event of an error, I should receive an error message rather than being logged out and having my messages deleted.
Actual behaviour
Yesterday, I was sending identical messages to clients using Telegram Lite version 5.5.5 on macOS. At some point, I was automatically logged out from all sessions. After logging back in, I noticed that all the messages I had previously sent were missing. This is highly unsatisfactory as clients did not receive important information on time. Please address this issue and suggest possible solutions to prevent such occurrences in the future.
Operating system
macOS 14
Version of Telegram Desktop
5.5.5
Installation source
Static binary from official website
Crash ID
No response
Logs
No response
The text was updated successfully, but these errors were encountered: