Failed posting of comments in chat from personal account

[TurboPlanner]

Describe the bug Unigram failed to post comment in chat from personal account but allow from chat or channel account

To Reproduce

1. Create chat
2. Create channel
3. Assign chat to channel
4. Switch to personal account in chat
5. Try to post - FAILED
6. You can call retry and message will posted

Expected behavior Personal account should works in chat comments

Screenshots

Version Info Version of Unigram - 8.7 (7352) I have auto update to new version

OS Edition Windows 10 Enterprise Version 21H1 OS build 19043.1586 Experience Windows Feature Experience Pack 120.2212.4170.0 Updated to last cumulative fixes

[FrayxRulez]

Most likely a backend issue. Would be great if you could reproduce the issue with logs turned on (instructions here). You can then send the logs file (logs have to be disabled to be able to send them through the app) to tdlib_bot on Telegram.

[TurboPlanner]

I cannot send td_lib log (see another bug about outdated version in Unigram)

Also I cannot see log file in described folder C:\Users\Admin\AppData\Local\Packages\38833FF26BA1D.UnigramPreview_g9c9v27vpyspw\LocalState

However before debug mode I can open small Td_lib log by sending to another account

IMHO, documented directory of log is incorrect

[FrayxRulez]

As I mentioned in the other ticket, I mentioned here again, and I mentioned in the TDLib logs documentation you must disable the logs to be able to send them:

To send logs through the app you must disable them first: Navigate to the Diagnostics settings, select Verbosity level and set it to Assert.
You can now click on the item below (marked as tdlib_log.txt): a dialog will open and you will be able to pick a chat where to send the file.

[TurboPlanner]

Ok, I sent log file to @tdlib_bot

What's next?

[Aquathing]

Wait until the source of the issue is identified and a fix is released.

[makisukurisu]

Can someone confirm if the problem was fixed or not?

It looks like it is to me. (8.9 7605 x64) Please, reopen the issue if the problem is still there