Reaction menu isn't disabled for self-destructing media

[SandaruKasa]

I don't think I can provide any screenshots, because Telegram X seems to be blocking the screenshots whenever any self-destructing media is present on the screen, even if not in the opened state. So sorry for that.

Actual behavior

The context menu (that appears after tapping on the message) has the row with reaction buttons even if the message in question is a self-destruct photo/video. Pressing on any of the reactions cause the reaction to not go through and a small bubble saying #400: MESSAGE_ID_INVALID appear at the top part of the screen.

Expected behavior

The context menu for self-destruct media doesn't have any reaction buttons.

Report deatils

Telegram X 0.24.10.1539-arm64-v8a (73c3eef)
PRs: #185 (81bd52c)
TDLib: 1.8.4 (tdlib/td@98bfbc9)
Android: Pie (28)
Device: asus ZB602KL (PKQ1.WW_Phone-16.2017.2009.087-20200826)

[EDINAM233]

Well with Telegram x you need to got to setting menu from there you will know where to tick the allow screenshot Sent from my T-Mobile 4G LTE Device Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: SandaruKasa ***@***.***> Sent: Sunday, August 7, 2022 8:00:31 PM To: TGX-Android/Telegram-X ***@***.***> Cc: Subscribed ***@***.***> Subject: [TGX-Android/Telegram-X] Reaction menu isn't disabled for self-destructing media (Issue #201) I don't think I can provide any screenshots, because Telegram X seems to be blocking the screenshots whenever any self-destructing media is present on the screen, even if not in the opened state. So sorry for that. Actual behavior The context menu (that appears after tapping on the message) has the row with reaction buttons even if the message in question is a self-destruct photo/video. Pressing on any of the reactions cause the reaction to not go through and a small bubble saying #400: MESSAGE_ID_INVALID appear at the top part of the screen. Expected behavior The context menu for self-destruct media doesn't have any reaction buttons. Report deatils Telegram X 0.24.10.1539-arm64-v8a (73c3eef<73c3eef>) PRs: #185<#185> (81bd52c<81bd52c>) TDLib: 1.8.4 ***@***.***<tdlib/td@98bfbc9>) Android: Pie (28) Device: asus ZB602KL (PKQ1.WW_Phone-16.2017.2009.087-20200826) — Reply to this email directly, view it on GitHub<#201>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASCOZDBXS5BDB5G4ZHPVTBLVYAIV7ANCNFSM5527MT6A>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[vkryl]

@SandaruKasa thank you for the well-described report. Will be fixed soon on TDLib side.

[vkryl]

Should be fixed since 88b5a9c, you can check in the last beta available on Google Play or https://t.me/tgx_log.