🐛 [BUG]: Upon using Bard-ai for a few minutes or so, it will invalidate the cookie or return NULL

[malice-cli]

Prerequisites

• [X] I have searched the issues and believe that it has not already been reported
• [X] It occurs on the latest version of bard-ai
• [X] I have read the FAQ and there are no solutions there

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

1. Getting a new cookie
2. Using bard for 5 minutes or so
3. It gets invalidated and returns null

Other information

No response

Occurance Rate

I can reproduce this bug 100% of the time.

[EvanZhouDev]

Are you using the __Secure-1PSIDTS cookie as well? See docs here: https://bard-ai.js.org/faq/#cant-use-bard

[malice-cli]

yes. it still returns a invalidation.

[ziuss76]

I have same error here, also tried using Secure-3PSID and Secure-3PSIDTS, and few minutes after it returns same error above. I think google constantly changes the cookie to shut down 3rd party apis, just like you mentioned in github readme.

[jonvicbarcenas]

Is there a way to auto fetch cookies using gmail and passwords? It invalidates mine after minutes

[Goldp-js]

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];

[Goldp-js]

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.

[EvanZhouDev]

Yes, please migrate to the PaLM API. The simulated Bard API interface is no longer stable (it's only working for some people)