Rich Message custom emojis are downgraded to Unicode after editMessageText for inline messages in chats

[ifuckingjoke]

Summary

When editing an inline message with editMessageText, RichInputTextCustomEmoji is rendered correctly in private chats, but is downgraded to plain Unicode emojis in chats such as groups, supergroups, and channels.

The same code and the same payload produce different results depending only on the destination entity type.

Environment

• Bot API: Cloud Bot API
• aiogram
• Inline mode
• editMessageText
• Rich Messages (RichInputTextCustomEmoji)

Steps to reproduce

1. Send an inline query.
2. Insert the inline result into a chat.
3. After receiving the inline_message_id, call editMessageText with a Rich Message containing RichInputTextCustomEmoji.

Expected behavior

Custom emojis should be rendered identically regardless of the destination chat type.

Actual behavior

Private chats (including conversations with bots)

✅ RichInputTextCustomEmoji is rendered correctly as a custom emoji.

Groups, supergroups, and channels

❌ After editMessageText, the same custom emoji is rendered as a regular Unicode emoji instead of a custom emoji.

Notes

• The issue only depends on the destination entity type.
• The same bot, the same API request, and the same RichInputTextCustomEmoji produce different results depending on where the inline message is inserted.
• Private chats work correctly, while chats representing group/channel entities do not.
• This appears to be specific to editing inline messages via editMessageText, as the API request itself is accepted successfully.

If this behavior is intentional, it should be documented. Otherwise, it appears to be a server-side bug in Rich Message rendering for inline messages edited in non-user entities.