-
Notifications
You must be signed in to change notification settings - Fork 113
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
Please pull Wiki update for Google API-key #934
Comments
Thanks for the contribution
I must admit that I have never done this, instead just added any account I use as a test user to the unpublished application. Do you recall what the consent screen activate dialog says? |
Honestly I did it in a little bit other order. When I created the OAuth-Client-ID it automatlicly added the formular of the consent-screen to the OAuth-Client-ID dialog. If you have a consent-screen then google not aks for it and it is not possible to open the creation-formular for the consent screen again. Thats the reason why I have here a lack of information, as well. But honestly it was not a big deal the important information are
|
There is some indication that this may subject the project to automated auditing, which is why I have never done it. Just conjecture, but it may be the reason why sometimes people have their API keys revoked. |
I ran into this trying to understand what the correct values for the Even following the linked guide I still don't know what these values should be. |
There are some visual aids in the pinned issue: #439 (comment) Have a look at step 12 for clarification on where to retrieve the required values. |
What Problem Does This Solve?
If somebody read the current version of the wiki, it is not clear how to setup a the necessary values for api_key, client_id and client_secret. Additonllay it exist no setup for Enable personal API keys in the current version, which can be enabled or disabled.
Suggest a Solution (optional)
Please pull the changes of the fork in Github Kuschranada/plugin.video.youtube/wiki/Personal-API-Keys to make this more clear.
The text was updated successfully, but these errors were encountered: