Commit Graph
398 Commits
Author SHA1 Message Date
Lonami Exo 9aad453e1a Update to layer 158 2023-04-21 17:11:59 +02:00
Lonami Exo 177386e755 Update to layer 155 2023-03-12 17:15:28 +01:00
Lonami Exo b87a8d0c1f Remove mentions to methods in generated TL ref
Instead, consistently use the term request, to avoid confusion.
2023-03-11 12:26:17 +01:00
Lonami Exo 373601500f Update to layer 154 2023-03-09 21:34:48 +01:00
Lonami Exo 07a7a8b404 Deprecate force_sms and sign_up
On the 10th of February, Telegram sent the following message to
those with an application registered on https://my.telegram.org.

--

Telegram API Update. Hello [REDACTED]. Thank you for contributing to the
open Telegram ecosystem by developing your app, [REDACTED].

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 the
way login codes are handled in third-party apps based on the Telegram API.

Starting on 18.02.2023, users logging into third-party apps will only be
able to receive login codes via Telegram. It will no longer be possible
to request an SMS to log into your app - just like when logging into
Telegram's own desktop and web clients.

Exactly like with the Telegram Desktop and Web apps, if a user doesn't
have a Telegram account yet, they will need to create one first using
an official mobile Telegram app.

We kindly ask you to update your app's login and signup interfaces to
reflect these changes before they go live on 18.02.2023 at 13:00 UTC.

This change will not significantly affect users since, according to our
research, the vast majority of third-party app users also use official
Telegram apps. In the coming months, we expect to offer new tools for
third-party developers that will help streamline the login process.
2023-02-26 10:40:53 +01:00
Lonami Exo 0563430314 Slightly improve documentation 2023-02-26 10:10:19 +01:00
Lonami Exo 6dece6e8a1 Update to layer 152 2023-02-05 15:05:05 +01:00
Lonami Exo c932d79ab3 Ignore improperly formatted errors from Telegram's JSON 2023-01-11 20:28:29 +01:00
Lonami Exo 94cc897019 Sync list of known errors with Telegram's JSON 2023-01-11 19:53:35 +01:00
Lonami Exo 7a74dedc48 Add script to sync errors with Telegram's JSON 2023-01-11 19:53:20 +01:00
Lonami Exo 6332690a51 Sort RPC error data 2023-01-11 19:36:30 +01:00
Lonami Exo 2007c83c9e Update to layer 151 2022-12-31 18:38:53 +01:00
Lonami Exo 7288c9933c Update to layer 150 2022-12-22 20:30:38 +01:00
Lonami Exo b2925f8279 Update documentation and list of known errors 2022-12-14 20:00:55 +01:00
Lonami Exo bd1ba3bf1e Bump to v1.26 and update layer to 149 2022-11-25 18:23:28 +01:00
Shrimadhav U K fb43f638ff Update to layer 148 and document new more errors (#3970) 2022-11-05 20:09:08 +01:00
Devesh Pal f819593cbf Update to layer 146 (#3933) 2022-10-14 18:50:27 +02:00
Lonami Exo 7f472ee72c Add CHAT_FORWARDS_RESTRICTED to known errors 2022-10-02 16:25:52 +02:00
Lonami Exo fd70b5a428 Update list of known errors 2022-09-27 10:49:12 +02:00
Lonami Exo 299eceb6eb Document new known RPC errors 2022-09-20 10:56:57 +02:00
Lonami Exo 6e8bc0d5b9 Fix raw API docs generation 2022-08-30 13:21:17 +02:00
Lonami Exo 8b1bfcdf9c Bump to v1.25 2022-08-30 12:57:34 +02:00
Tulir Asokan d5c864597c Update to layer 144 2022-08-30 12:11:38 +02:00
Rongrong db3faedbfc Add ENTITY_BOUNDS_INVALID and POSTPONED_TIMEOUT to known errors (#3887) 2022-07-25 11:52:48 +02:00
Eugene Lam 066820900d Update to layer 143 (#3862) 2022-07-02 09:27:35 +02:00
Tulir Asokan dda696cce4 Add INVITE_REQUEST_SENT to known errors 2022-05-12 10:40:04 +02:00
Lonami Exo 43f629f665 Update to layer 140 2022-05-12 10:21:03 +02:00
Lonami Exo 5feb210442 Add support for flags2 in the TL 2022-05-12 10:20:42 +02:00
Shrimadhav U K 9c796e8d73 Fix typo, add errors, and update to 133 again (#3157) 2021-12-01 19:00:29 +01:00
Lonami Exo 3f5f5dbe48 Update documentation and list of known errors
Closes #3151.
2021-09-11 11:02:10 +02:00
Shrimadhav U K 28d3d4b122 Update to layer 133 (#3155) 2021-09-11 10:54:11 +02:00
Shrimadhav U K 2182e7f6f1 Update to layer 132 (#3142) 2021-08-31 15:22:56 +02:00
Shrimadhav U K 0a4b827d8e Document new known RPC errors (#3137) 2021-08-28 00:18:37 +02:00
Shrimadhav U K 6a1f29d953 Add new known RPC errors (#3134) 2021-08-20 11:49:12 +02:00
Devesh Pal 79866750d2 Add new known RPCErrors (#3114) 2021-07-20 23:04:09 +02:00
Shrimadhav U K 3570953d14 Update to layer 131 (#3112) 2021-07-16 21:01:08 +02:00
Lonami Exo 1e09e133e3 Document new known RPC errors
Courtesy of #3097.
2021-07-09 20:11:21 +02:00
Shrimadhav U K ecfc6ae87d Add pm_oneside parameter in pin_message (#3095) 2021-07-09 19:50:47 +02:00
Shrimadhav U K 7763939e7d Update to layer 130 (#3098) 2021-07-09 19:47:13 +02:00
Devesh Pal 42bfc7bb3f Fix inline force_document and new known RPC errors (#3084)
This should fix inline video notes.
2021-06-24 14:19:01 +02:00
Lonami Exo 2052b502c8 Update to v1.22 2021-06-19 19:08:02 +02:00
Anonymous 7c5efee1de Update to layer 129 and other additions/enhancements (#3074)
* Apply code corrections for the new layer types.
* Support not passing `user` to `get_permissions`.
* `download_profile_photo` now supports `MessageService`.
* `thumb` in send and edit message.
* Document new known errors.
2021-06-15 22:57:32 +02:00
Lonami Exo 63f24d2282 Add new known RPC errors and update docs 2021-05-30 18:00:27 +02:00
Anonymous 85381713b2 Document new known RPC errors (#3057) 2021-05-15 10:49:55 +02:00
Alisa Sireneva b2c26a53ef Document new known RPC errors (#3044) 2021-05-05 20:38:43 +02:00
Lonami Exo 319b6283a9 Update install/test server docs and add new known RPC error 2021-04-21 19:56:57 +02:00
Lonami Exo 5b91adf62d Update documentation
Closes #1733.
2021-03-31 10:54:18 +02:00
Lonami Exo 2fbf850841 Update to layer 126
May help with #3010
2021-03-31 10:52:35 +02:00
Lonami Exo b06f496a27 Don't treat False field as flag omission
8724949b54 was only half the story.
2021-03-16 08:21:04 +01:00
Lonami Exo 3d6a2bb945 Update to version 1.21 2021-03-14 11:31:03 +01:00