Telegram iOS Talk

#bug reply draft lost after force close reply to any message, type some text but dont send it. then fully close telegram from the app switcher and relaunch. when you go back to the chat the reply draft is completely gone, text and quote. drafts should survive an app restart iPhone 15, iOS 26.5.2, app store 12.9.2

Hi together! I wanted to test the latest beta but just was to late for the test flight registration. Any chance I can join the testing? Thx :)

Read pinned https://t.me/TelegramiOStalk/199521

So I assume its not possible to build it ourself like there is no branch/tag on the https://github.com/TelegramMessenger/Telegram-iOS github right?

correct, the betas arent on github. source only gets pushed once a version goes public, latest tag there is 12.9.2. you can build that one yourself though, the readme in the repo has the build steps. you need your own api id and hash from my.telegram.org and an apple developer account to sign it on your phone

Yeah did that in the past, was quite cool when it finallly build lol :D

Yes

It’s a joke..

same here, its rough. builds go through fine but most of the time the app never actually launches on my test device, xcode just sits there attaching to the process and gives up. what fixed the worst of it for me was disabling enable backtrace recording in the scheme diagnostics. the app was hanging on the splash screen under the debugger but always started fine when i launched it straight from the phone, that was the hint

Which XCode version you're using? For this project I'm on 26.4, maybe should give the 27 beta a try

i dont think its only activity tbh. the bot probably also waits for actual free slots. testflight caps at 10000 testers per app, and with dupes and dead accounts the usable number is lower than that. so even active people might just be sitting in a queue until someone leaves or gets cleaned out

There’s plenty of slots.

ah ok, so slots arent the issue then. now im curious how the bot actually judges people. is it just counting messages, or is there something smarter in the backend, like an llm reading the bug reports? or is a human doing the review

I wouldn’t worry too much about how the bot works. I’d focus instead of bringing a relevant feedback to the group and eventually file reasonable bug reports.

27 beta 4 for the test device stuff. for building this project id stay on 26.4 tbh, the debug pain only starts when the target device runs ios 27. if you ever debug on an ios 27 device, kill the enable backtrace recording option first, saves you the splash screen hangs

Thx! Yes, first time experienced that kind of debug pain for ios 27, guess I need to try building it with xcode 27