Render newer bot rich messages as readable fallback - #1416
Open
ohld wants to merge 2 commits into
Open
Conversation
|
|
ohld
marked this pull request as ready for review
June 26, 2026 08:52
aplinxy9plin
approved these changes
Jun 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Updates the Telegram-iOS submodule to include newer TL compatibility parsing for rich bot messages, and adds a small macOS-side refresh hook for cached unsupported cloud messages.
This makes old cached unsupported rich bot messages request
messages.getRichMessageagain when they appear in chat history, so the fallback text can replace the unsupported placeholder.Bug
Bot messages using recent rich formatting can show as:
This message is not supported in your version of Telegram. Please update to the latest version.Repro message used for testing:
https://t.me/ohld_chat/35423
Build
The script builds the macOS app as a separate dev bundle:
ru.keepcoder.TelegramDevRichTestTelegram Dev RichTestartifacts/Telegram-Dev-RichTest.dmgTest Artifact
Local DMG:
/Users/ohld/Documents/GitHub/TelegramSwift/artifacts/Telegram-Dev-RichTest.dmgSHA256:
a4a572cbd789f140555753ffc436c686ba7fa7255b720c8e435dfca132af05a3Verification
swift buildinsubmodules/telegram-ios/submodules/TelegramApi: passed../artifacts/build-dev-rich-test-dmg.sh: passed.artifacts/Telegram Dev RichTest.app, then openedhttps://t.me/ohld_chat/35423./Users/ohld/Library/Application Support/Telegram Dev RichTest/stable/logs/critlog-2026-6-26_02-28-24.883.txtFresh-log counters:
This message is not supported: 0messageMediaUnsupported: 0d64c522b: 049e91f2a: 07600b9d3,baf39d8b,773f4e66,966e2dbf,ba7bb15e: 0Screenshot automation was attempted locally, but macOS returned a black capture in this environment, so the reliable verification here is build + fresh client logs.
Related
Submodule PR: overtake/Telegram-iOS#4