(2025-01-27, 07:53)ozarks Wrote: None of the discussion seems to address this particular error.
Please take the time to read through the recent posts, or at least perform a search:
https://forum.kodi.tv/search.php?action=...d+code+401.
It has been discussed numerous times already. See
https://github.com/anxdpanic/plugin.vide...2613975245 - you haven't completed step 8.2
(2025-01-27, 12:10)rev691 Wrote: Hi, sorry I could not find the answer in this long thread.
...
How do I get the second request to login?
Please take the time to read through the recent posts. Three posts before yours is this:
(2025-01-27, 01:48)MoojMidge Wrote: The two device code prompts are in the current beta version. The first one is not actually used for anything, but if you are only seeing one then that means you are still using v7.1.1.6
(2025-01-27, 13:03)kaminix Wrote: Now that the Youtube app is signed in and working on the Android does the Google/Chrome app outside of Kodi on the Android need to remain signed in?
No, you do not need to remain signed in on the web browser once the sign in process has been completed in Kodi.
(2025-01-27, 17:08)Patkino Wrote: It didnt happen on stable versions, but happens on every beta.
How i can manually restrict a certain amount of recommendations loaded by the addon?
The same thing has occurred since the recommendations were re-enabled around a year ago. The only difference now is that there is a background progress dialog because it can take a long time to populate. There is currently no pagination of recommendations.
(2025-01-27, 19:48)jbrid Wrote: Meaning, would Google suspend an account without warning for violating community guidelines? Also, is using an API key to access YT through a third-party app such as this one a violation?
It is unrelated to community guidelines, but you will need to do your own research as to whether usage in this manner meets the required of the YouTube Data API ToS
https://developers.google.com/youtube/te...of-service
Note that the account that you use to create API access for the addon, use of which is goverened by the ToS, does not need to be the same account that is used to login i.e. your YouTube account
Do not take this as a definitive statement, recommendation, or advise (legal or otherwise) regarding the applicability of the ToS to your usage of the addon. The addon code is offerred under the terms of the
GPL-2.0 license.
Can't comment any further on this matter either.
(Yesterday, 02:28)Luterin Wrote: I know I have an unusual account since my YouTube account is on my Google Account, but not the default account. So my Gmail is one thing and my YouTube is another thing. This is since my YouTube account is really old and it became like this when they merged YouTube and Google accounts.
Yes, this is the problem, as mentioned before. You are trying to login or using OAuth credentials for a Google account that does not have a YouTube account associated with it, so you cannot access anything associated with your YouTube account such as your Watch Later playlist.
You can create the API keys and OAuth details using your Google account, but the user account that you authorise as a test user and/or use to login with needs to be your YouTube account. I think - there are definitely issues with this but you will need to test it out for yourself.
@
DjDiabolik - there are various blocks that have been implemented. The higher CPU usage during playback is actually unrelated to the bot verification error that occurs before playback. They are two different things, and one or both can apply.
To everyone providing help and guidance to others in this thread - you have my thanks for the assistance.