-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
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
🐛 [BUG]: Upon using Bard-ai for a few minutes or so, it will invalidate the cookie or return NULL #61
Comments
Are you using the __Secure-1PSIDTS cookie as well? See docs here: https://bard-ai.js.org/faq/#cant-use-bard |
yes. it still returns a invalidation. |
I have same error here, also tried using __Secure-3PSID and __Secure-3PSIDTS, and few minutes after it returns same error above. |
Is there a way to auto fetch cookies using gmail and passwords? It invalidates mine after minutes |
After some research I saw that in this line where all the login is in charge, it looks for variable 1, and then when the cookie does not work it will return Error: TypeError: Cannot read properties of null (reading '1') const SNlM0e = ResponseText.match(/SNlM0e":"(.*?)"/)[1]; |
The problem is that the cookies mentioned change constantly and since it is not a good idea to automate that, since, if the process of obtaining cookies could be automated, a captcha will always appear on the bard website so it is not possible to work in obtaining automatic cookies. |
Yes, please migrate to the PaLM API. The simulated Bard API interface is no longer stable (it's only working for some people) |
Prerequisites
bard-ai
Bug Description
As said in the title, when you are using it for more than 5 minutes, it will start returning null responses or have a invalidated cookie.
and I use a new cookie every time, it would work, but after 5 minutes, it gets invalidated.
Im not sure if this is a issue with the library itself, or bard.
Reproduction Steps
Other information
No response
Occurance Rate
I can reproduce this bug 100% of the time.
The text was updated successfully, but these errors were encountered: