In case you still haven't seen it, remember that it is no longer possible to request SMS from Telethon, or even sign up. There will be an update printing a deprecation warning if you try using those methods eventually.
Telegram
lonami in Telethon Chat
Telegram API Update. Hello —,. Thank you for contributing to the open Telegram ecosystem by developing your app, —.
Please note that due to recent updates to Telegram's handling of SMS and the integration of new SMS providers like Firebase, we are changing…
Please note that due to recent updates to Telegram's handling of SMS and the integration of new SMS providers like Firebase, we are changing…
Forwarded from Telegram Info English (DbSergey)
Users of unofficial clients are having trouble logging into their accounts
Earlier we reported that starting from February 18, when authorizing in unofficial applications, users will not be able to request authorization codes in the form of SMS or phone calls, and that such codes will only come in other active sessions.
To date, the editors know that:
1. The first messages from users of unofficial applications that they cannot receive an authorization code in the form of a phone call or SMS began to arrive only on February 20-21.
2. Many of these users do not receive authorization codes even in active sessions: the user logs into the account in the official application, then starts authorization in the unofficial one and ... nothing happens: the code does not come anywhere at all.
We continue to monitor the situation.
Earlier we reported that starting from February 18, when authorizing in unofficial applications, users will not be able to request authorization codes in the form of SMS or phone calls, and that such codes will only come in other active sessions.
To date, the editors know that:
1. The first messages from users of unofficial applications that they cannot receive an authorization code in the form of a phone call or SMS began to arrive only on February 20-21.
2. Many of these users do not receive authorization codes even in active sessions: the user logs into the account in the official application, then starts authorization in the unofficial one and ... nothing happens: the code does not come anywhere at all.
We continue to monitor the situation.
FYI: Telethon's mode with updates disabled relied on
invokeWithoutUpdates, but apparently that's not intended to work. Probably another thing to deprecate.Telegram
Aliaksei Levin in TDLib chat
The only intended use case for invokeWithoutUpdates is Share extension for iOS apps. It has never supposed to work in other circumstances.
Include Telethon version on fatal errors during updates (f9001bc by Lonami)
Update FAQ (3e64ea3 by Lonami)
Remove redundant entity cache (f7e38ee by Lonami)
Remove now-unused EntityCache class (d1e3237 by Lonami)
Fix _get_entity_pair could receive None as input (cb04e26 by Lonami)
Flush in-memory cache to session after a limit is reached (97b0ba6 by Lonami)
Store self user in entity cache (88bc6a4 by Lonami)
Save self user ID in session file (a657ae0 by Lonami)
Update FAQ (fd09284 by Lonami)
Handle PhoneCodeExpiredError during sign_in (af18538 by Lonami)
Update FAQ (3e64ea3 by Lonami)
Remove redundant entity cache (f7e38ee by Lonami)
Remove now-unused EntityCache class (d1e3237 by Lonami)
Fix _get_entity_pair could receive None as input (cb04e26 by Lonami)
Flush in-memory cache to session after a limit is reached (97b0ba6 by Lonami)
Store self user in entity cache (88bc6a4 by Lonami)
Save self user ID in session file (a657ae0 by Lonami)
Update FAQ (fd09284 by Lonami)
Handle PhoneCodeExpiredError during sign_in (af18538 by Lonami)