Closed DogLi closed 3 years ago
user_id
in UpdateUserFullInfo
is i64, but in telegram it gives a string
also the optionValueInteger
user_id
inUpdateUserFullInfo
is i64, but in telegram it gives a string also theoptionValueInteger
I don't think so, this question already solved. Related: https://github.com/fewensa/telegram-client/issues/16 https://github.com/fewensa/fantasy/issues/1
Usual this question is use different version of rtdlib and td. what's version do you use of td?
I'll test as soon. any news can talk with this issue.
Hi, I did some tests, this problem does not exist in version 1.7.0
2021-08-21 15:14:52,425 DEBUG [telegram_client::api::api] <=== {"@type":"updateChatLastMessage","chat_id":6***2,"last_message":{"@type":"message","id":7***4,"sender":{"@type":"messageSenderUser","user_id":6***2},"chat_id":6***2,"is_outgoing":false,"is_pinned":false,"can_be_edited":false,"can_be_forwarded":true,"can_be_deleted_only_for_self":true,"can_be_deleted_for_all_users":true,"can_get_statistics":false,"can_get_message_thread":false,"is_channel_post":false,"contains_unread_mention":false,"date":1629530092,"edit_date":0,"reply_in_chat_id":0,"reply_to_message_id":0,"message_thread_id":0,"ttl":0,"ttl_expires_in":0.000000,"via_bot_user_id":0,"author_signature":"","media_album_id":"0","restriction_reason":"","content":{"@type":"messageText","text":{"@type":"formattedText","text":"b","entities":[]}}},"positions":[]}
2021-08-21 15:14:52,426 DEBUG [full_client] Chat last message: 6***2, data: {"@type":"message","@extra":null,"id":7***4,"sender":{"@type":"messageSenderUser","@extra":null,"user_id":6***2},"chat_id":6***2,"sending_state":null,"scheduling_state":null,"is_outgoing":false,"is_pinned":false,"can_be_edited":false,"can_be_forwarded":true,"can_be_deleted_only_for_self":true,"can_be_deleted_for_all_users":true,"can_get_statistics":false,"can_get_message_thread":false,"is_channel_post":false,"contains_unread_mention":false,"date":1629530092,"edit_date":0,"forward_info":null,"interaction_info":null,"reply_in_chat_id":0,"reply_to_message_id":0,"message_thread_id":0,"ttl":0,"ttl_expires_in":0.0,"via_bot_user_id":0,"author_signature":"","media_album_id":0,"restriction_reason":"","content":{"@type":"messageText","@extra":null,"text":{"@type":"formattedText","@extra":null,"text":"b","entities":[]},"web_page":null},"reply_markup":null}
[ 3][t10][1629530253.014801502][Td.cpp:4588][#2][!Td][&td_requests] Sending update: updateOption {
name = "version"
value = optionValueString {
value = "1.7.0"
}
}
telegram-client: =1.7.0 rtdlib: =1.7.0
This issue will close, If there are still problems, you can reopen this issue.
This is indeed a bug and will be fixed in the next version, follow this issue https://github.com/fewensa/telegram-client/issues/25 also same as https://github.com/fewensa/telegram-client/issues/20
The new version released https://crates.io/crates/telegram-client
I use the telegram-client version 1.7.0, compiled tdlibjson.so based on td tag
v1.7.0
, and get error:maybe same as #20