telegramdesktop / tdesktop

Telegram Desktop messaging app
https://desktop.telegram.org/
Other
26.23k stars 5.2k forks source link

Issue with switch_pm_parameter #26736

Closed DO97 closed 1 month ago

DO97 commented 1 year ago

Steps to reproduce

  1. Open an inline result with a switch_inline_parameter at the top.
  2. When you click it the first time, you get redirected to the bot.
  3. The bot now shows the command connected to it.
  4. If the command reply has a keyboard that redirects you to a group, you'll have the username of the bot already inserted in your message box (when switching from bot to group).
  5. At this point, clicking again on the switch_pm_parameter will only generate the default "/start" command, instead of the connected one.
  6. You're now forced to leave and re-enter the group to update the switch_pm_parameter and make it work. You can't use the commands continuosly as before.

Contact https://t.me/Argus_Apocraphex for more infos and a working example.

Expected behaviour

Read above.

Actual behaviour

https://github.com/telegramdesktop/tdesktop/assets/17525578/25da85fd-49ee-41ee-82cf-2bf531da87cb

Operating system

Windows 10

Version of Telegram Desktop

4.9.4

Installation source

Static binary from official website

Crash ID

No response

Logs

No response

github-actions[bot] commented 8 months ago

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!

DO97 commented 8 months ago

Still present.

github-actions[bot] commented 2 months ago

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!