ЧТО ТАКОЕ ОТЛАДКА WEBVIEW В ТЕЛЕГРАММЕ
Отладка WebView в Telegram Messenger позволяет разработчикам и тестировщикам устранять проблемы, связанные с использованием WebView в приложении. WebView — это компонент, который может использоваться для отображения веб-страниц непосредственно внутри приложения, и для устранения проблем в этой части приложения используется отладка.
В процессе отладки WebView в Telegram Messenger можно использовать различные инструменты и методы. Например, можно выводить отладочную информацию в консоль браузера, использовать инструменты разработчика Chrome или Firefox, а также использовать сторонние инструменты.
Отладка WebView может помочь в выявлении и устранении ошибок в приложении, таких как неправильное отображение веб-страниц, проблемы с доступом к контенту и многое другое. Для использования отладки WebView в Telegram Messenger необходимо иметь навыки веб-разработки и знание соответствующих инструментов и методов.
При отладке WebView в Telegram Messenger следует учитывать также различные ограничения и особенности платформы. Например, некоторые функции WebView могут быть заблокированы на определенных устройствах или версиях Android, что может затруднить процесс отладки и тестирования.
В целом, отладка WebView является важной частью процесса разработки приложений для Telegram Messenger, и может помочь в улучшении качества и функциональности приложения.
СЕКРЕТНЫЕ ФИШКИ TELEGRAM 2022 �� ТЫ О НИХ НЕ ЗНАЛ �� Удобные Функции, Секреты и Лайфхаки Телеграма
Топ скрытых фишек Telegram 2022
Настрой ПРАВИЛЬНО Телеграм перед запуском. Не пользуйся пока ЭТО не сделаешь. Секреты Телеграм ����
��Как Google Убили Android: Опасное обновление Android WebView. Вылетают приложения. Как исправить?
ИНТЕРНЕТ ПОЛЕТЕЛ на Xiaomi �� телефон ЛОВИТ везде, после SIM настройки MIUI 12.5 ��
Зачем разработчики засекретили эти функции в Телеграм. Как попасть в секретное меню Телеграм? ��
Web Apps for Bots
Telegram bots can completely replace any website. They support seamless authorization, integrated payments via 20 payment providers (with Google Pay and Apple Pay out of the box), delivering tailored push notifications to users, and much more.
With Web Apps, bots get a whole new dimension. Bot developers can create infinitely flexible interfaces with JavaScript, the most widely used programming language in the world.
To see a Web App in action, try our sample @DurgerKingBot.
Recent changes
April 21, 2023
Bot API 6.7
- Added support for launching Web Apps from inline query results and from a direct link.
- Added the method switchInlineQuery to the class WebApp.
December 30, 2022
Bot API 6.4
- Added the field platform, the optional parameter options to the method openLink and the methods showScanQrPopup, closeScanQrPopup, readTextFromClipboard to the class WebApp.
- Added the events qrTextReceived, clipboardTextReceived.
August 12, 2022
Bot API 6.2
- Added the field isClosingConfirmationEnabled and the methods enableClosingConfirmation, disableClosingConfirmation, showPopup, showAlert, showConfirm to the class WebApp.
- Added the field is_premium to the class WebAppUser.
- Added the event popupClosed.
June 20, 2022
Bot API 6.1
- Added the ability to use bots added to the attachment menu in group, supergroup and channel chats.
- Added support for t.me links that can be used to select the chat in which the attachment menu with the bot will be opened.
- Added the fields version, headerColor, backgroundColor, BackButton, HapticFeedback and the methods isVersionAtLeast, setHeaderColor, setBackgroundColor, openLink, openTelegramLink, openInvoice to the class WebApp.
- Added the field secondary_bg_color to the class ThemeParams.
- Added the method offClick to the class MainButton.
- Added the fields chat, can_send_after to the class WebAppInitData.
- Added the eventsbackButtonClicked, settingsButtonClicked, invoiceClosed.
Designing Web Apps
Color Schemes
Web Apps always receive data about the user's current color theme in real time, so you can adjust the appearance of your interfaces to match it. For example, when users switch between Day and Night modes or use various custom themes.
Design Guidelines
Telegram apps are known for being snappy, smooth and following a consistent cross-platform design. Your Web App should ideally reflect these principles.
- All elements should be responsive and designed with a mobile-first approach.
- Interactive elements should mimic the style, behavior and intent of UI components that already exist.
- All included animations should be smooth, ideally 60fps.
- All inputs and images should contain labels for accessibility purposes.
- The app should deliver a seamless experience by monitoring the dynamic theme-based colors provided by the API and using them accordingly.
Implementing Web Apps
Telegram currently supports six different ways of launching Web Apps: from a keyboard button, from an inline button, from the bot menu button, via inline mode, from a direct link – and even from the attachment menu.
Keyboard Button Web Apps
TL;DR: Web Apps launched from a web_app type keyboard button can send data back to the bot in a service message using Telegram.WebApp.sendData. This makes it possible for the bot to produce a response without communicating with any external servers.
Users can interact with bots using custom keyboards, buttons under bot messages, as well as by sending freeform text messages or any of the attachment types supported by Telegram: photos and videos, files, locations, contacts and polls. For even more flexibility, bots can utilize the full power of HTML5 to create user-friendly input interfaces.
You can send a web_app type KeyboardButton that opens a Web App from the specified URL.
To transmit data from the user back to the bot, the Web App can call the Telegram.WebApp.sendData method. Data will be transmitted to the bot as a String in a service message. The bot can continue communicating with the user after receiving it.
Good for:
- Сustom data input interfaces (a personalized calendar for selecting dates; selecting data from a list with advanced search options; a randomizer that lets the user “spin a wheel” and chooses one of the available options, etc.)
- Reusable components that do not depend on a particular bot.
Inline Button Web Apps
TL;DR: For more interactive Web Apps like @DurgerKingBot, use a web_app type Inline KeyboardButton, which gets basic user information and can be used to send a message on behalf of the user to the chat with the bot.
If receiving text data alone is insufficient or you need a more advanced and personalized interface, you can open a Web App using a web_app type Inline KeyboardButton.
From the button, a Web App will open with the URL specified in the button. In addition to the user's theme settings, it will receive basic user information ( ID , name , username , language_code ) and a unique identifier for the session, query_id, which allows messages on behalf of the user to be sent back to the bot.
The bot can call the Bot API method answerWebAppQuery to send an inline message from the user back to the bot and close the Web App. After receiving the message, the bot can continue communicating with the user.
Good for:
- Fully-fledged web services and integrations of any kind.
- The use cases are effectively unlimited.
Launching Web Apps from the Menu Button
TL;DR: Web Apps can be launched from a customized menu button. This simply offers a quicker way to access the app and is otherwise identical to launching a Web App from an inline button.
By default, chats with bots always show a convenient menu button that provides quick access to all listed commands. With Bot API 6.0, this button can be used to launch a Web App instead.
To configure the menu button, you must specify the text it should show and the Web App URL. There are two ways to set these parameters:
- To customize the button for all users, use @BotFather (the /setmenubutton command or Bot Settings > Menu Button).
- To customize the button for both all users and specific users, use the setChatMenuButton method in the Bot API. For example, change the button text according to the user's language, or show links to different Web Apps based on a user's settings in your bot.
Apart from this, Web Apps opened via the menu button work in the exact same way as when using inline buttons.
@DurgerKingBot allows launching its Web App both from an inline button and from the menu button.
Inline Mode Web Apps
TL;DR: Web Apps launched via web_app type InlineQueryResultsButton can be used anywhere in inline mode. Users can create content in a web interface and then seamlessly send it to the current chat via inline mode.
NEW You can use the button parameter in the answerInlineQuery method to display a special 'Switch to Web App' button either above or in place of the inline results. This button will open a Web App from the specified URL. Once done, you can call the Telegram.WebApp.switchInlineQuery method to send the user back to inline mode.
Inline Web Apps have no access to the chat – they can't read messages or send new ones on behalf of the user. To send messages, the user must be redirected to inline mode and actively pick a result.
Good for:
- Fully-fledged web services and integrations in inline mode.
Direct Link Web Apps
TL;DR: Web App Bots can be launched from a direct link in any chat. They support a startapp parameter and are aware of the current chat context.
NEW You can use direct links to open a Web App directly in the current chat. If a non-empty startapp parameter is included in the link, it will be passed to the Web App in the start_param field and in the GET parameter tgWebAppStartParam.
In this mode, Web Apps can use the chat_type and chat_instance parameters to keep track of the current chat context. This introduces support for concurrent and shared usage by multiple chat members – to create live whiteboards, group orders, multiplayer games and similar apps.
Web Apps opened from a direct link have no access to the chat – they can't read messages or send new ones on behalf of the user. To send messages, the user must be redirected to inline mode and actively pick a result.
Examples
Good for:
- Fully-fledged web services and integrations that any user can open in one tap.
- Cooperative, multiplayer or teamwork-oriented services within a chat context.
- The use cases are effectively unlimited.
Launching Web Apps from the Attachment Menu
TL;DR: Web App Bots can request to be added directly to a user's attachment menu, allowing them to be quickly launched from any chat. To try this mode, open this attachment menu link for @DurgerKingBot, then use the menu in any type of chat.
Web App Bots can request to be added directly to a user's attachment menu, allowing them to be quickly launched from any type of chat. You can configure in which types of chats your web app can be started from the attachment menu (private, groups, supergroups or channels).
Attachment menu integration is currently only available for major advertisers on the Telegram Ad Platform. However, all bots can use it in the test server environment.
To enable this feature for your bot, open @BotFather from an account on the test server and send the /setattach command – or go to Bot Settings > Configure Attachment Menu. Then specify the URL that will be opened to launch the bot's Web App via its icon in the attachment menu.
You can add a 'Settings' item to the context menu of your Web App using @BotFather. When users select this option from the menu, your bot will receive a settingsButtonClicked event.
In addition to the user's theme settings, the bot will receive basic user information ( ID , name , username , language_code , photo ), as well as public info about the chat partner ( ID , name , username , photo ) or the chat info ( ID , type , title , username , photo ) and a unique identifier for the web view session query_id, which allows messages of any type to be sent to the chat on behalf of the user that opened the bot.
The bot can call the Bot API method answerWebAppQuery, which sends an inline message from the user via the bot to the chat where it was launched and closes the Web App.
You can read more about adding bots to the attachment menu here.
Initializing Web Apps
To connect your Web App to the Telegram client, place the script telegram-web-app.js in the <head> tag before any other scripts, using this code:
Once the script is connected, a window.Telegram.WebApp object will become available with the following fields:
The application can display just the top part of the Web App, with its lower part remaining outside the screen area. From this position, the user can “pull” the Web App to its maximum height, while the bot can do the same by calling the expand() method. As the position of the Web App changes, the current height value of the visible area will be updated in real time.
The application can display just the top part of the Web App, with its lower part remaining outside the screen area. From this position, the user can “pull” the Web App to its maximum height, while the bot can do the same by calling the expand() method. Unlike the value of viewportHeight , the value of viewportStableHeight does not change as the position of the Web App changes with user gestures or during animations. The value of viewportStableHeight will be updated after all gestures and animations are completed and the Web App reaches its final size.
ThemeParams
Web Apps can adjust the appearance of the interface to match the Telegram user's app in real time. This object contains the user's current theme settings:
| Field | Type | Description |
|---|---|---|
| bg_color | String | Optional. Background color in the #RRGGBB format. Also available as the CSS variable var(—tg-theme-bg-color) . |
| text_color | String | Optional. Main text color in the #RRGGBB format. Also available as the CSS variable var(—tg-theme-text-color) . |
| hint_color | String | Optional. Hint text color in the #RRGGBB format. Also available as the CSS variable var(—tg-theme-hint-color) . |
| link_color | String | Optional. Link color in the #RRGGBB format. Also available as the CSS variable var(—tg-theme-link-color) . |
| button_color | String | Optional. Button color in the #RRGGBB format. Also available as the CSS variable var(—tg-theme-button-color) . |
| button_text_color | String | Optional. Button text color in the #RRGGBB format. Also available as the CSS variable var(—tg-theme-button-text-color) . |
| secondary_bg_color | String | Optional. Bot API 6.1+ Secondary background color in the #RRGGBB format. Also available as the CSS variable var(—tg-theme-secondary-bg-color) . |
PopupParams
This object describes the native popup.
| Field | Type | Description |
|---|---|---|
| title | String | Optional. The text to be displayed in the popup title, 0-64 characters. |
| message | String | The message to be displayed in the body of the popup, 1-256 characters. |
| buttons | Array of PopupButton | Optional. List of buttons to be displayed in the popup, 1-3 buttons. Set to [<“type”:“close”>] by default. |
ScanQrPopupParams
This object describes the native popup for scanning QR codes.
| Field | Type | Description |
|---|---|---|
| text | String | Optional. The text to be displayed under the 'Scan QR' heading, 0-64 characters. |
PopupButton
This object describes the native popup button.
| Field | Type | Description |
|---|---|---|
| id | String | Optional. Identifier of the button, 0-64 characters. Set to empty string by default. If the button is pressed, its id is returned in the callback and the popupClosed event. |
| type | String | Optional. Type of the button. Set to default by default. Can be one of these values: — default, a button with the default style, — ok, a button with the localized text “OK”, — close, a button with the localized text “Close”, — cancel, a button with the localized text “Cancel”, — destructive, a button with a style that indicates a destructive action (e.g. “Remove”, “Delete”, etc.). |
| text | String | Optional. The text to be displayed on the button, 0-64 characters. Required if type is default or destructive. Irrelevant for other types. |
BackButton
This object controls the back button, which can be displayed in the header of the Web App in the Telegram interface.
| Field | Type | Description |
|---|---|---|
| isVisible | Boolean | Shows whether the button is visible. Set to false by default. |
| onClick(callback) | Function | Bot API 6.1+ A method that sets the button press event handler. An alias for Telegram.WebApp.onEvent('backButtonClicked', callback) |
| offClick(callback) | Function | Bot API 6.1+ A method that removes the button press event handler. An alias for Telegram.WebApp.offEvent('backButtonClicked', callback) |
| show() | Function | Bot API 6.1+ A method to make the button active and visible. |
| hide() | Function | Bot API 6.1+ A method to hide the button. |
All these methods return the BackButton object so they can be chained.
MainButton
This object controls the main button, which is displayed at the bottom of the Web App in the Telegram interface.
| Field | Type | Description |
|---|---|---|
| text | String | Current button text. Set to CONTINUE by default. |
| color | String | Current button color. Set to themeParams.button_color by default. |
| textColor | String | Current button text color. Set to themeParams.button_text_color by default. |
| isVisible | Boolean | Shows whether the button is visible. Set to false by default. |
| isActive | Boolean | Shows whether the button is active. Set to true by default. |
| isProgressVisible | Boolean | Readonly. Shows whether the button is displaying a loading indicator. |
| setText(text) | Function | A method to set the button text. |
| onClick(callback) | Function | A method that sets the button press event handler. An alias for Telegram.WebApp.onEvent('mainButtonClicked', callback) |
| offClick(callback) | Function | A method that removes the button press event handler. An alias for Telegram.WebApp.offEvent('mainButtonClicked', callback) |
| show() | Function | A method to make the button visible. Note that opening the Web App from the attachment menu hides the main button until the user interacts with the Web App interface. |
| hide() | Function | A method to hide the button. |
| enable() | Function | A method to enable the button. |
| disable() | Function | A method to disable the button. |
| showProgress(leaveActive) | Function | A method to show a loading indicator on the button. It is recommended to display loading progress if the action tied to the button may take a long time. By default, the button is disabled while the action is in progress. If the parameter leaveActive=true is passed, the button remains enabled. |
| hideProgress() | Function | A method to hide the loading indicator. |
| setParams(params) | Function | A method to set the button parameters. The params parameter is an object containing one or several fields that need to be changed: text — button text; color — button color; text_color — button text color; is_active — enable the button; is_visible — show the button. |
All these methods return the MainButton object so they can be chained.
HapticFeedback
This object controls haptic feedback.
All these methods return the HapticFeedback object so they can be chained.
WebAppInitData
This object contains data that is transferred to the Web App when it is opened. It is empty if the Web App was launched from a keyboard button or from inline mode.
WebAppUser
This object contains the data of the Web App user.
| Field | Type | Description |
|---|---|---|
| id | Integer | A unique identifier for the user or bot. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. It has at most 52 significant bits, so a 64-bit integer or a double-precision float type is safe for storing this identifier. |
| is_bot | Boolean | Optional. True, if this user is a bot. Returns in the receiver field only. |
| first_name | String | First name of the user or bot. |
| last_name | String | Optional. Last name of the user or bot. |
| username | String | Optional. Username of the user or bot. |
| language_code | String | Optional. IETF language tag of the user's language. Returns in user field only. |
| is_premium | True | Optional. True, if this user is a Telegram Premium user |
| photo_url | String | Optional. URL of the user’s profile photo. The photo can be in .jpeg or .svg formats. Only returned for Web Apps launched from the attachment menu. |
WebAppChat
This object represents a chat.
| Field | Type | Description |
|---|---|---|
| id | Integer | Unique identifier for this chat. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier. |
| type | String | Type of chat, can be either “group”, “supergroup” or “channel” |
| title | String | Title of the chat |
| username | String | Optional. Username of the chat |
| photo_url | String | Optional. URL of the chat’s photo. The photo can be in .jpeg or .svg formats. Only returned for Web Apps launched from the attachment menu. |
Validating data received via the Web App
To validate data received via the Web App, one should send the data from the Telegram.WebApp.initData field to the bot's backend. The data is a query string, which is composed of a series of field-value pairs.
You can verify the integrity of the data received by comparing the received hash parameter with the hexadecimal representation of the HMAC-SHA-256 signature of the data-check-string with the secret key, which is the HMAC-SHA-256 signature of the bot's token with the constant string WebAppData used as a key.
Data-check-string is a chain of all received fields, sorted alphabetically, in the format key=<value> with a line feed character ('\n', 0x0A) used as separator – e.g., 'auth_date=<auth_date>\nquery_id=<query_id>\nuser=<user>' .
The full check might look like:
To prevent the use of outdated data, you can additionally check the auth_date field, which contains a Unix timestamp of when it was received by the Web App.
Once validated, the data may be used on your server. Complex data types are represented as JSON-serialized objects.
Events Available for Web Apps
The Web App can receive events from the Telegram app, onto which a handler can be attached using the Telegram.WebApp.onEvent(eventType, eventHandler) method. Inside eventHandler the this object refers to Telegram.WebApp, the set of parameters sent to the handler depends on the event type. Below is a list of possible events:
| eventType | Description |
|---|---|
| themeChanged | Occurs whenever theme settings are changed in the user's Telegram app (including switching to night mode). eventHandler receives no parameters, new theme settings and color scheme can be received via this.themeParams and this.colorScheme respectively. |
| viewportChanged | Occurs when the visible section of the Web App is changed. eventHandler receives an object with the single field isStateStable. If isStateStable is true, the resizing of the Web App is finished. If it is false, the resizing is ongoing (the user is expanding or collapsing the Web App or an animated object is playing). The current value of the visible section’s height is available in this.viewportHeight. |
| mainButtonClicked | Occurs when the main button is pressed. eventHandler receives no parameters. |
| backButtonClicked | Bot API 6.1+ Occurrs when the back button is pressed. eventHandler receives no parameters. |
| settingsButtonClicked | Bot API 6.1+ Occurrs when the Settings item in context menu is pressed. eventHandler receives no parameters. |
| invoiceClosed | Bot API 6.1+ Occurrs when the opened invoice is closed. eventHandler receives an object with the two fields: url – invoice link provided and status – one of the invoice statuses: — paid – invoice was paid successfully, — cancelled – user closed this invoice without paying, — failed – user tried to pay, but the payment was failed, — pending – the payment is still processing. The bot will receive a service message about a successful payment when the payment is successfully paid. |
| popupClosed | Bot API 6.2+ Occurrs when the opened popup is closed. eventHandler receives an object with the single field button_id – the value of the field id of the pressed button. If no buttons were pressed, the field button_id will be null. |
| qrTextReceived | Bot API 6.4+ Occurs when the QR code scanner catches a code with text data. eventHandler receives an object with the single field data containing text data from the QR code. |
| clipboardTextReceived | Bot API 6.4+ Occurrs when the readTextFromClipboard method is called. eventHandler receives an object with the single field data containing text data from the clipboard. If the clipboard contains non-text data, the field data will be an empty string. If the Web App has no access to the clipboard, the field data will be null. |
Adding Bots to the Attachment Menu
Attachment menu integration is currently only available for major advertisers on the Telegram Ad Platform. However, all bots can use it in the test server environment. Talk to Botfather on the test server to set up the integration.
A special link is used to add bots to the attachment menu:
https://t.me/botusername?startattach
or
https://t.me/botusername?startattach=command
For example, open this attachment menu link for @DurgerKingBot, then use the menu in any private chat.
Opening the link prompts the user to add the bot to their attachment menu. If the bot has already been added, the attachment menu will open in the current chat and redirect to the bot there (if the link is opened from a 1-on-1 chat). If a non-empty startattach parameter was included in the link, it will be passed to the Web App in the start_param field and in the GET parameter tgWebAppStartParam.
The following link formats are also supported:
https://t.me/username?attach=botusername
https://t.me/username?attach=botusername&startattach=command
https://t.me/+1234567890?attach=botusername
https://t.me/+1234567890?attach=botusername&startattach=command
These links open the Web App in the attachment menu in the chat with a specific user. If the bot wasn't already added to the attachment menu, the user will be prompted to do so. If a non-empty startattach parameter was included in the link, it will be passed to the Web App in the start_param field and in the GET parameter tgWebAppStartParam.
Bot API 6.1+ supports a new link format:
Opening such a link prompts the user to choose a specific chat and opens the attachment menu in that chat. If the bot wasn't already added to the attachment menu, the user will be prompted to do so. You can specify which types of chats the user will be able to choose from. It can be one or more of the following types: users, bots, groups, channels separated by a + sign. If a non-empty startattach parameter was included in the link, it will be passed to the Web App in the start_param field and in the GET parameter tgWebAppStartParam.
Testing Web Apps
Using bots in the test environment
To log in to the test environment, use either of the following:
- iOS: tap 10 times on the Settings icon > Accounts > Login to another account > Test.
- Telegram Desktop: open ☰ Settings > Shift + Alt + Right click ‘Add Account’ and select ‘Test Server’.
- macOS: click the Settings icon 10 times to open the Debug Menu, ⌘ + click ‘Add Account’ and log in via phone number.
The test environment is completely separate from the main environment, so you will need to create a new user account and a new bot with @BotFather.
After receiving your bot token, you can send requests to the Bot API in this format:
Note: When working with the test environment, you may use HTTP links without TLS to test your Web App.
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Отладки в Телеграмм
А вы знали про то, что в Telegram есть секретное меню – отладки в Телеграмм? — Секретное меню в Телеграмм еще называют скрытым меню в телеграмме, но, а правильно оно называется меню отладки в Телеграмм.
Узнайте, как из Telegram можно сохранить фотографии, если вам это надо конечно.
Как открыть меню отладки в Телеграмм
Смотрите, как вы можете зайти в такое секретное меню, как отладки в Telegram:
- Зайдите в Telegram и нажмите на три полоски в левой верхней части телефона.
- Заходим в «Настройки».
- Опускаемся в самый низ на строчку «Telegram для Android» и делаем частые нажатия (тапы) по этой строчке.
- После частых нажатий оставьте палец на паузе в строчке «Telegram для Android», после чего у вас появится такой вот «человечек».
- Вы просто нажмите долгим нажатием пальца на знакомую вам строку «Telegram для Android», после чего у вас в телеграмме откроется меню отладки.
Вот такие шаги вам придется проделать для того чтобы открыть секретное меню отладки в телеграмм.
А вы знаете, как пользоваться календарем Телеграмма, и что он там вообще есть?
Что может меню отладки в Telegram
Давайте лучше разберем отладки в Telegram и их возможности для пользователей этого крутого мессенджера. И каждому пользователю советую ознакомиться с очисткой Telegram от мусора, засоряющего устройство.
И так, смотрим из каких возможностей и функций состоит секретное меню отладок в телеграмме:
- Импорт контактов. Дает возможность импортировать ваши контакты, например, из google аккаунта и т.д.
- Перезагрузить контакты. Это возможность обновления контактов, которые появились у вас.
- Сбросить контакты. Это функция к которой рекомендую относиться с осторожностью. Ведь применив ее вы можете потерять все контакты, которые сохранены в вашем Telegram.
- Сбросить кэш чатов. Эта фишка позволит очистить кэш из ваших чатов в телеграмме и удалить файлы. Если вы сохранили из телеги что-то в свою галерею, то те файлы в ней так и останутся. Их эта функция не затронет. А вам поможет освободить место.
- Включить логирование. Нажав на нее у вас появится меню, в котором вы сможете выбрать: 1) Отправить лог; 2) отправить свежие логи; 3) Очистить лог. Выбираете один из вариантов, например, «Отправить лог», и отправляете его разработчикам. А они уже решают ваши проблемы.
- Выключить встроенную камеру. Этот пункт позволит выключить камеру самого приложения Telegram, которая в него встроена. Советую ее выключить и пользоваться камерой телефона.
- Очистить кэш отправки файлов. Функция полезная, поэтому периодически используйте ее.
- Настройки звонков. Если не знаете, что это значит, то не советую нажимать на эти настройки.
- Прочесть все чаты. Нажав на эту ссылку все ваши чаты будут показаны как прочитанные без цифр, которые показывают вам сколько сообщений вы не прочитали.
- Останавливать музыку при записи. Если у вас в телефоне играет музыка и вы отправляете голосовое сообщение, то применив эту фишку, музыка у вас не запишется, а будет слышен только ваш голос.
- Show Status bar background.
- Включить откладку Применяется для браузерной версии телеграмма.
- Вкл. альтернативную навигацию
Вот в принципе и все вкладки в секретном меню телеграмма отладки, которые активны на сегодняшний день. И вы ими можете теперь воспользоваться.
А вы знали про секретное меню в телеграмме «Отладки в Телеграмм», и приходилось ли вам пользоваться этим меню?