-
Notifications
You must be signed in to change notification settings - Fork 48
Workaround for expired cookies of CoolQ
Although many functions implemented are based on the APIs provided by CoolQ, there're still many crucial APIs that aren't supported natively, for example get_friend_list and get_group_info. So CoolQ HTTP API plugin uses alternative ways to deal with the problem, which requires the user cookie provided by CoolQ.
The question is that the cookie may gets expired after some time, which makes the API mentioned above stop working. But CoolQ itself doesn't realize the expiration for it can still use this cookie as credentials to send/receive messages. So we have to manually delete the cookies and 'force' CoolQ to relogin and obtain the new cookies.
When you receives a message from the Telegram bot telling you to reset the cookie, please follow the steps to complete the procedure.
- Stop CoolQ
- For Docker user, press Ctrl+C in the terminal which runs the docker image.
- For Windows user, click on the CoolQ icon in the taskbar and select 'Exit'
- Go to CoolQ folder and find the file located in data/<qq_uid>/session.dat
- Delete the session.dat
- Relaunch CoolQ and enter your password
Your cookie has been refreshed and everything should come back to the right track.