messages.getAllChats always retrun INPUT_METHOD_INVALID_2271179966_*

[bigbigsir]

layer: 139

Is there anyone who can help me？

[wind-hx]

I also encounter the same problem

[0xARK]

Hello, I also have this problem

[bigbigsir]

What happened? It didn't change anything, and all of a sudden it didn't work

[bigbigsir]

@alik0211

[0xARK]

I checked the telegram api docs for update or something else, but I saw nothing related to getAllChats...

[destyk]

This error is true for me too

[alexsanderluisdev]

same for me, has anyone found any solution?

[alexsanderluisdev]

Has anyone found any solution?

[destyk]

@alik0211

[0xARK]

It seems that this method has been removed from telegram API, and getDialogs must be used instead.

See gram-js/gramjs#522

[alexsanderluisdev]

It seems that this method has been removed from telegram API, and getDialogs must be used instead.

See gram-js/gramjs#522

however the getDialogs method gets only recent conversations and not all conversations.

[0xARK]

Oh, didn't noticed that, I just saw this answer... It will be a problem for me too, more digging is necessary :(

[alexsanderluisdev]

Oh, didn't noticed that, I just saw this answer... It will be a problem for me too, more digging is necessary :(

I don't understand the Telegram have removed this method without any notice, causing a breaking change.

[alexsanderluisdev]

@0xARK any solution?

[0xARK]

No, I didn't have time to look into it

[0xARK]

See gram-js/gramjs#522 (comment) @alexsanderluisdev

[alexsanderluisdev]

@0xARK this don't work for me. Causes a infinity loop.

[0xARK]

it's working on my side, check the adapted method for mtproto :

const getAllChats = async () => {
            const LIMIT = 100;
            const offsetId = 0;
            const offsetPeer = {
                _: 'inputPeerEmpty'
            };

            let resultCount = LIMIT;
            let offsetDate = 0;
            let chats = [];

            while (resultCount >= LIMIT) {
                const result = await mtproto.call('messages.getDialogs', {
                    offset_id: offsetId,
                    offset_peer: offsetPeer,
                    offset_date: offsetDate,
                    limit: LIMIT
                }).catch(e => {
                    if (e.error_message.includes('FLOOD_WAIT')) {
                        log.warn("Telegram", `API rate limit reached, please wait ${e.error_message.replace('FLOOD_WAIT_', '')} seconds`);
                    } else log.error("Telegram", e.message);
                })

                resultCount = result.dialogs.length;

                if (result.chats && result.chats.length > 0) {
                    chats = [...chats, ...result.chats];
                }

                if (result.messages.length > 0) {
                    offsetDate = result.messages[result.messages.length - 1].date;
                } else {
                    break;
                }
            }

            return chats;
        }

[alexsanderluisdev]

don't work, this lists even fewer chats, and chats that have no interaction are still not listed

[Endytech]

I used messages.getAllChats to get all chats and then filter chats to get only chats that we need.

To get chats according to a pre-known list I used two method. First try to find by @name. If @name do not exists then find by search and filter by chat.title.

static async getChatsByUsername(username) {
     let resolvedPeer = { chats: [] };
     try {
         resolvedPeer = await api.call('contacts.resolveUsername', {
             username,
         });
     } catch (error) {
         console.warn('Error to get chat', username);
     }
     const chat = resolvedPeer.chats.find((chat) => (chat.id === resolvedPeer.peer.channel_id));
     return chat;
 }

static async searchChatsByTitle(title) {
        const searchResult = await api.call('contacts.search', {
            q: title,
        });
        return searchResult.chats.find((chat) => (chat.title === title));
    }

[joeberetta]

Oh, didn't noticed that, I just saw this answer... It will be a problem for me too, more digging is necessary :(

I don't understand the Telegram have removed this method without any notice, causing a breaking change.

U're able to check their changelog here https://core.telegram.org/api/layers

They removed support of this method in 158 layer and yes, looks strange cuz older versions have to work (while it's supported by any of telegram server)