API Key Input Mangling, Client Secret #108
Comments
|
Can confirm this is an issue and should affect everyone soon. All was working fine until one day last week I got a "key expired" error. Got sick of fiddling with things so started out fresh - fresh install, new key/api etc. I can setup the app without API and it works fine for a while before the "Daily Quota" BS kicks in. But when I input my API creds and sign in again I get a 401 error inputing the first /activate code. It would appear something has changed on Google's side of things.... |
|
Are you using the latest version of 5.4.2.
Jeff
… On Aug 14, 2017, at 12:12 AM, MicNor ***@***.***> wrote:
Can confirm this is an issue and should affect everyone soon, All was working fine until one day last week I got a "key expired" error. Got sick of fiddling with things so started out fresh - fresh install, new key/api etc. I can setup the app without API and it works fine for a while before the "Daily Quota" BS kicks in. But when I input my API creds and sign in again I get a 401 error after the first /activate code.
It would appear something has changed on Google's side of things....
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#108 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALozLRfTXugveOoRhfHhUhI9-PTC3C4jks5sX8kYgaJpZM4OuZYK>.
|
|
@jdf76 Confirmed 5.4.1 last week and 5.4.2 today. I'll try a full reset once more to eliminate anything else. One thing I've noticed is the API Client ID is something like: In relation to what OP was saying about the API Secret having a special/odd character: EDIT: Just did a fresh install of the app, input API creds verbatim, and reproduced the same issue. It's clear the app is running into an error with google's API. Here's some pics if you think I'm crazy: http://imgur.com/a/O0Heh |
|
Logfile is here: http://paste.ubuntu.com/25310399/ The juicy part is here: ------ Window Init (DialogBusy.xml) ------ |
|
I've been unable to reproduce this and the logs don't really have much information in that area. The PR is #113 , the specific changes are in commit 7a41126 |
|
I can confirm this is happening to me. I recently decided I needed to use my own API keys. Went thru the setup, and when I try to log back in I get this exception. Search appears to work fine, so I know my keys are good. Currently running v5.4.5 of the add-on with Kodi Krypton (LibreElec) |
|
Still unable to reproduce, added extra checks to try to catch any mangling that may be happening. |
|
Getting same login issue. Personal API seems to be working when searching, and when it is set to that I cannot login. Using youtube.com/activate . 'Youtube LoginExeption Error Code: 401'. The code is accepted on youtube/activate and the issue only occurs when trying to login. On a side note, how do you login with settings.xml? I havent quite worked out where to put my credentials there yet. |
|
[Bingo:] (https://stackoverflow.com/questions/27483674/youtube-api-v3-shows-access-not-configured) You need to delete the current client key, disable the YT data API, re-enable it, then create a new client key. Confirmed working meow. Not sure what made it stop one day - methinks YT stopped/started my API and that invalidated my key. Confirmed is working fine. Meow. |
|
Key stripping methods have been changed, error messages in this area are improved, and api keys can be edited from web browser in coming v6 if when signing in you get -- invalid_client : oauth client not found -- the client id is incorrect. Please re-open if still having this issue. |
Steps to reproduce the problem:
What should happen:
What happens
Sign In does work when manually inputting the details into the file, the problem seems to be when inputting it via the Kodi itself.
This happened to me twice in a row, but I sadly didn't take photographs. If you are unable to reproduce yourself, I can do this again, showing the first few characters of each key on-screen and in the xml file.
If you would like any further info, please don't hesitate to let me know.
The text was updated successfully, but these errors were encountered: