tdesktop icon indicating copy to clipboard operation
tdesktop copied to clipboard

Randomly fails to show error message when attempting and failing to add member to chat

Open php4fan opened this issue 2 years ago • 3 comments

Steps to reproduce

I think this should reproduce the issue:

  1. go to a group where you are not an admin, where users are allowed to add new members
  2. add a bot as member
  3. don't go away, don't do anything with the UI of Telegram Desktop, but meanwhile, make sure an admin bans the newly added bot from the group
  4. try to add the bot again

What I actually did was that there was a bot admin in the chat that would immediately automatically ban any bot that would be added to the group, so that was what happened at step 3. I suspect the issue will reproduce regardless of whether the bot is banned by a human admin or by a bot admin. It's possible that the issue will only reproduce if the ban is done very quickly (just speculating).

Expected behaviour

Either it should succeed, or it should show an error message.

Actual behaviour

The member is not added, but no error message is shown. It does absolutely nothing, as if you had clicked Cancel.

I tried several times, and it was just silently failing silently with no error message whatsoever.

Then I went to another chat and came back, and retried, and this time I got the expected error message "Sorry, only admins can ad this member".

Operating system

Manjaro Linux

Version of Telegram Desktop

4.9.7

Installation source

Other (unofficial) source

Crash ID

No response

Logs

No response

php4fan avatar Oct 13 '23 16:10 php4fan

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Apr 11 '24 01:04 github-actions[bot]

This issue was inactive for a long time and will be automatically closed

Again, this is stupid. It's either fixed or it isn't. If it isn't, no progress having been done is not a reason for closing it.

php4fan avatar Apr 11 '24 06:04 php4fan

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Oct 09 '24 01:10 github-actions[bot]