With the latest update to Telegram Desktop, the parsing process was affected. I'm actively working on potential solutions to address this issue. Thank you for your patience!
Some control checks on the TL have been temporarily disabled due to issues originating from Telegram itself. As soon as conditions allow, proper solutions will be implemented.
This change does not affect the reliability of the bot, the disabled checks were primarily used to identify potentially outdated TLs, and are not critical for the bot’s functionality. Everything else continues to work as expected.
The bot is now back online, and all functionalities have been restored. Thank you for your support!
Please open Telegram to view this post
VIEW IN TELEGRAM
❤5
In the latest Telegram Android update, a curious new method popped up: messages.updateStarGiftCollection. Interestingly, it currently returns nothing, which is quite unusual, the standard MTProto Protocol doesn’t typically include methods with no response. This could suggest that the developer is still working on this upcoming feature, or it might just be another placeholder (or leftover) method in the TLRPC class.
The missing result was just an oversight, it's now been fixed and the method behaves as expected.
Please open Telegram to view this post
VIEW IN TELEGRAM
👀3🔥2
Please open Telegram to view this post
VIEW IN TELEGRAM
2😁9❤5👌2
With the latest update to Telegram Android, the decompilation process was affected. I'm actively working on potential solutions to address this issue. Thank you for your patience!
The bot is now back online, and all functionalities have been restored. Thank you for your support!
Please open Telegram to view this post
VIEW IN TELEGRAM
❤5👍2🔥2
Telegram recently updated their Android app, but the file currently hosted on their servers appears to be corrupted or incomplete. As a result, decompilation is not possible at the moment.
I'm keeping an eye on the situation, but we'll need to wait for Telegram to fix the issue on their end.
Thanks for your understanding and patience!
Telegram still hasn't fixed the issue. Somehow, they broke either the file itself or the response headers tools like curl report that the file is corrupted or incomplete.
curl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)
Until Telegram resolves this on their side, there's unfortunately nothing I can do to proceed.
Thanks again for your continued patience!
The bot is now back online, and all functionalities have been restored. Thank you for your support!
Please open Telegram to view this post
VIEW IN TELEGRAM
1❤9👍1🔥1
In the latest Telegram Android update, something rather disruptive happened for MTProto clients. The developer introduced a new constructor for the type Channel, but on Layer 213 this constructor hasn’t actually been enabled in the schema.
Essentially, deserialization of updates is now broken for all clients relying on the official TgScheme schema. Only Telegram Android continues to work correctly, since it uses its own backwards compatibility layer, allowing support for the old constructor (supported up to Layer 212) while simultaneously handling the new one.
Until the new constructor is officially adopted in the schema, one temporary solution is to manually re-add the old constructor for Channel into your local copy of the schema, ensuring compatibility with incoming updates.
The issue is still present in Layer 214. Despite the version bump, the new Channel constructor hasn’t been enabled in the official schema, so deserialization problems remain exactly the same as in Layer 213.
One of the Telegram developers confirmed that the issue was simply caused by an oversight. A fix is already planned and should be shipped in next week’s update.
The issue has now been fixed by reverting the changes made to the Channel constructor.
Please open Telegram to view this post
VIEW IN TELEGRAM
👀6🐳3🦄2💊2❤1🤡1