Aliaksei Levin
Aliaksei Levin
TDLib always returns the newest possible data. There is no need to do anything.
If the account is frozen, then you send an appeal from the account. You can use test DC to test the app during development phase.
> test accounts, warmed-up accounts, and purchased accounts None of these is allowed by Telegram API ToS.
> Add automated build validation - run builds locally or remotely This is generally good, but there are dozens different popular versions of C++ compilers, many ways to build TDLib...
You can check TDLib logs to see the exact cause of the error. For example, deleted profile photos can't be downloaded, but if this is the cause, then you will...
It is up to the server how and when authorization codes are sent. Application can't affect this behavior.
I can't give any relevant recommendations.
Could you try to build with `-fno-objc-msgsend-selector-stubs`?
It is simpler to specify additional build options as environment variables: `CFLAGS="-fno-objc-msgsend-selector-stubs" CXXFLAGS="-fno-objc-msgsend-selector-stubs" cmake $td_path $options ...`
Then the issue in some other non-deterministic behavior of Apple-clang or of Xcode's linker. The flags previously helped Telegram iOS app to fix non-deterministic builds, but if they don't help,...