-
Notifications
You must be signed in to change notification settings - Fork 17
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
Cookie import fails with "validated: undefined" #22
Comments
Impossible to say without logs what's happening. Probably means invalid cookie? Sometimes doing this from a blank browser can help, where there has always only been one google account used. Or you can also use the manual import. |
I have the same issue, have been having it since forever and always just manually added the cookie, very annoying.
It seems to just send bad data, not actually the full cookies file like it needs. |
A cookie is valid, if TA can access your liked videos playlist, e.g. One of these cases of works on my machine. If it doesn't work for you, please provide a fix. |
Please be nice. |
I'm also experiencing this issue for months now. I'm using Edit: I can confirm the observation by grantterra, the cookie extracted by the extension is too short. After exporting the cookie manually, placing it in the |
I'm experiencing this in Chrome, but not in Firefox. |
and
as well as
you'll see in your log output cookie building happens in background.js here: https://github.com/tubearchivist/browser-extension/blob/master/extension/background.js#L209 if anybody wants to investigate further. |
Some investigation on the live stream could point towards that we limit our domain selection too much, and that www.youtube.com will get excluded. notes: https://github.com/Rob--W/cookie-manager/issues/26 some traceback:
|
For me, looks like the extension included a cookie from the subdomain Because the validation is done by yt-dlp, before tubearchivist/tubearchivist#669 which would log the error in the console, you could try capturing the cookie file sent by the extension from the extension developer console, then testing it with downloading any youtube video with a noop arg like
|
Interesting, would make sense that I can't reproduce this, I probably won't have any payment subdomain cookies if I didn't make any payments on YT. Will ignoring all subdomains work? Or does this need some other processing? |
Given yt-dlp is rejecting cookies from the subdomains, I think it's safe to remove all subdomains. |
I do not have any cookies on subdomains but it still fails. Both on firefox and chrome and with different accounts |
I can confirm that removing the payments.youtube.com cookie solved the problem for me. |
Can somebody who can reproduce this check if the linked commit on the https://github.com/tubearchivist/browser-extension/tree/fix-cookie-domain branch fixes that? This still syncs the cookie correctly for me. |
assuming this has been fixed, update to v0.3.0 |
Heya,
I just tried importing my cookies and I'm getting the following error inside the browser extension:
![image](https://private-user-images.githubusercontent.com/8442196/260572053-511f7f72-13db-4345-babd-a6b98ddc38b8.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA2NTYwNzIsIm5iZiI6MTcyMDY1NTc3MiwicGF0aCI6Ii84NDQyMTk2LzI2MDU3MjA1My01MTFmN2Y3Mi0xM2RiLTQzNDUtYmFiZC1hNmI5OGRkYzM4YjgucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcxMCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MTBUMjM1NjEyWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9OGNiMGU5YjRhYzY3ZDg5YjkzNDgyNmQzOGM2MjA4NDM2NDgzODk5ODg4NDYxYmEwZTE5YmU3MWMxZDM2ZWE0ZSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.k59ybVwce03CWAS3Q45Q0RH4mH3IqsJym2hKmb-nSZg)
In the Inspect tab I get the message
{"message":{"cookie_import":"fail","cookie_validated":false}}
, the network tab tells me a400 Bad Request
occured.Not sure if I'm doing something wrong (again) tho :)
Thanks already!
The text was updated successfully, but these errors were encountered: