-
Notifications
You must be signed in to change notification settings - Fork 119
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
New version 7.1.1.4 causing me issues #1013
Labels
bug
Something isn't working
Comments
Same here, differences: OS: LibreElec (x86 Generic Build) |
Same issues on macOS Big Sur v 11.7.10 |
Can someone provide a log? |
Never mind, I can see where the problem is. You just need to sign-in for the moment, rather than only using the API key. |
MoojMidge
added a commit
to MoojMidge/plugin.video.youtube
that referenced
this issue
Dec 5, 2024
Merged
MoojMidge
added a commit
to MoojMidge/plugin.video.youtube
that referenced
this issue
Dec 6, 2024
MoojMidge
added a commit
to MoojMidge/plugin.video.youtube
that referenced
this issue
Dec 7, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
Please provide any relevant information about your setup
For some reason after getting this update, the add-on doesn't read my api keys. It keeps asking for them when they are clearly installed into the settings.
I tried a fresh install of Kodi, then installed 7.1.1.4, then entered my keys but still get the same issue.
If I go back to 7.1.1.3 it works perfectly. If I try updating that again to 7.1.1.4, it breaks and constantly tells me I need api keys. The keys are displayed correctly in the settings.xml file and in the api_keys.json file, but the add-on doesn't see them.
The log simply shows: warning : [plugin.video.youtube] API request: aborted
I tested 7.1.1.4 on an Android box, and my keys worked perfectly which really confused me as I wouldn't expect an OS to make a difference for something like this.
Sorry I don't have time to help troubleshoot, I just wanted to leave a report in case others have this issue.
The text was updated successfully, but these errors were encountered: