TelegramMessenger / TelegramMessenger/Telegram-iOS
Preview content before sending in inline mode
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 9k
- Forks
- 2.9k
- PR merge metrics
- No merged PRs in 30d
Description
Checklist
- I am reporting an issue in existing functionality that does not work as intended
- I've searched for existing GitHub issues
Description
Inline results work differently then in android or windows client. I am developing an inline bot. I currently have over 10000 users and ios users say that they cant preview content of my bot (images and voice messages)
Expected Behavior
Image inline result: should open in full screen mode before beeng sent
Voice cached inline result: should have a play button
Actual Behavior
Image: The picture is sent without preview. Only the thumbnail is shown.
Voice: There is an empty square with the first letter of the name
Steps to Reproduce
- Create an inline bot with voices and images
- Try to use it
- Understand, that this is very difficult without beeng able to preview the content
- You can also try it in @vosticksbot (voices) or @pic (images)
Screenshots and Videos
Voice:

Voice expected (screenshot from android):

Environment
Device: iPhone/iPad X
iOS version: 13.X
App version: 7.X
I don't have an ios device, only screenshots and complains from my users.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with @vosticksbot and @pic, comparing the iOS behavior with the supplied Android screenshots. Trace the inline-result handling in the iOS app; done means image results can be previewed full-screen and cached voice results show a playable control before sending.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100