We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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.
Already on GitHub? Sign in to your account
昨天碰到 webwxsync BaseResponse Ret 为代码 3 的问题,一直死循环,直到本次会话有效期截止(11:43:46 -- 13:39:38)。
原因未知,代码含义也未知。
2016-12-28 11:43:46.421 [信息] net_maclife_wechat_http_BotApp WebWeChatGetMessagePackage: -------------------------------------------------- 2016-12-28 11:43:46.421 [较详细] net_maclife_wechat_http_BotApp WebWeChatGetMessagePackage: 获取 WebWeChatGetMessagePackage 中 webwxsync 的 http 响应消息体: 2016-12-28 11:43:46.422 [较详细] net_maclife_wechat_http_BotApp WebWeChatGetMessagePackage: {"BaseResponse":{"Ret":3,"ErrMsg":""},"AddMsgCount":0,"AddMsgList":[],"ModContactCount":0,"ModContactList":[],"DelContactCount":0,"DelContactList":[],"ModChatRoomMemberCount":0,"ModChatRoomMemberList":[],"Profile":{"BitFlag":0,"UserName":{"Buff":""},"NickName":{"Buff":""},"BindUin":0,"BindEmail":{"Buff":""},"BindMobile":{"Buff":""},"Status":0,"Sex":0,"PersonalCard":0,"Alias":"","HeadImgUpdateFlag":0,"HeadImgUrl":"","Signature":""},"ContinueFlag":0,"SyncKey":{"Count":0,"List":[]},"SKey":"","SyncCheckKey":{"Count":0,"List":[]}} 2016-12-28 11:43:46.422 [警告] net_maclife_wechat_http_BotApp ProcessBaseResponse: WebWeChatGetMessagePackage 中 webwxsync 失败,代码: 3 , 错误信息:
The text was updated successfully, but these errors were encountered:
请问这个问题解决了吗,我也遇到了
Sorry, something went wrong.
原因未知。以前抓微信网页版通信协议的时候(Web 页面不关闭,连续几天几夜,就碰到了),微信网页版自己也出现过这种情况。
一旦出现这种情况,可以在手机端打开任何一个对话窗口、或者在手机端发一条消息,该情况就会立刻停止。
我也遇到了这种情况,跑着跑着webwxsync接口就突然出现ret=3了,目前还没找到解决办法,只能重新登陆,synccheck接口是正常的,有人知道是什么问题吗?
No branches or pull requests
昨天碰到 webwxsync BaseResponse Ret 为代码 3 的问题,一直死循环,直到本次会话有效期截止(11:43:46 -- 13:39:38)。
原因未知,代码含义也未知。
The text was updated successfully, but these errors were encountered: