Closed pylakey closed 1 year ago
@Lonami why this is closed? This bug is not solved.
Can you confirm it doesn't work in the latest released version? This is kind of a very big bug so I'm surprised it's only being complained about now.
yes, you may test it with this. @Lonami
from telethon.tl.types import ChannelParticipantCreator, ChannelParticipantAdmin
from telethon.tl.functions.channels import GetParticipantRequest
#..
@client.on(events.NewMessage)
async def handler(event):
participant = await client(GetParticipantRequest(channel=event.original_update.message.to_id.channel_id, participant=event.original_update.message.from_id))
isadmin = (type(participant.participant) == ChannelParticipantAdmin)
iscreator = (type(participant.participant) == ChannelParticipantCreator)
print(isadmin, iscreator)
Closing since this should be working fine in the v1.25 available from PyPi.
nop, not working..
Please make sure you're up to date and provide a code sample that triggers the issue. As I said before this is a big issue so I'd be surprised if it's only being noticed now.
When a user with 64-bit ID sends a message to Bot (updates for userbot work as expected), there is no peer in incoming update. When "old" user write to bot everything works as expected.
At the start I thought that it's a Telegram server side issue, but their own library works as expected with this kind of updates. So maybe there is error with parsing raw packets from Telegram server?
You could test it by registering new account with one of official Telegram apps and then send /start to bot from that account
UPD: I've also found out that bot receiving update with empty
users
field in this situationChecklist
pip install -U https://github.com/LonamiWebs/Telethon/archive/master.zip
and triggered the bug in the latest version.Code that causes the issue
Traceback