Skip to content
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

Installer instructions mismatched with Google's Oauth/API UI #401

Open
PhilHudson opened this issue Oct 10, 2022 · 7 comments
Open

Installer instructions mismatched with Google's Oauth/API UI #401

PhilHudson opened this issue Oct 10, 2022 · 7 comments

Comments

@PhilHudson
Copy link

The issue tracker is for reporting product deficiencies. How do I questions should be posted to the discussion forum at https://groups.google.com/group/got-your-back. When in doubt, start at the discussion forum and return here only when instructed to do so.

Please confirm the following:

Full steps to reproduce the issue:

  1. Run the installer
  2. Go to the second Google URL presented by the script
  3. Stare in bafflement at the page you reach. Look for the widgets described and find only "Name". Fill it in then click "Save" as instructed and get an error saying required fields are blank.

Expected outcome (what are you trying to do?):

Obtain an ID and a key

Actual outcome (what errors or bad behavior do you see instead?):

Can't complete the process as described, no clue what to do instead.

Using current Manjaro, Chromium

@mylesofsmiles
Copy link

I second this. Something must have changed on the backend recently. I can't get around needing a "Service Account" even after following the wiki line for line.

@kalebzettl
Copy link

@PhilHudson @mylesofsmiles
Hello, I wanted to give you a hand if you hadn't resolved your setup. I do agree it doesn't follow as @gmail.com accounts require the consent screen setup prior to setting up Oauth credentials.

Please try the following instructions, if they are clear enough I'll fix them up a bit and open a pull request to check for consumer gmail accounts and give these instructions instead.

These are steps from after you just run the installer.

Enter Email Address, enter your email address.

https://gyb-shortn.jaylee.us/XXXXX

Open Link Above, You'll be presented with "GAM Project Creation wants to access your Google Account"

Allow This.

Next After GYB creates your project, you'll get a URL starting with:

https://console.cloud.google.com/apis/credentials/oauthclient?project=gyb-project-XXX-XXX-XXX

Open this link.

You should already be on the 'Credentials' Tab.

Click 'Configure Consent Screen' on the right. (Blue Button)

User Type : External (Internal Only Applicable to GSuite)

Click 'Create' (Blue Button)

Enter 'GYB' for App Name.

Enter your email for 'User support email'

Scroll to bottom.

Enter your email for 'Developer contact information'

Click 'Save and Continue'

Ignore the Scopes Section

Click 'Save and Continue'

Ignore the Test Users

Click 'Save and Continue'

You should now be on the 'Summary' screen.

Scroll to the bottom and click 'Back to Dashboard'

Next, Go Back to 'Credentials' Tab you'll now notice it's different.

Click '+ Create Credentials' at the top.

Click 'OAuth client ID'

For 'Application Type' Choose 'Desktop App'

For its 'Name' set to 'GYB'

You will now have a window titled 'OAuth client created'

Enter Client ID and Client Secret into GYB Setup.

@stebansaa
Copy link

Im seeing this message: GYB has not completed the Google verification process. The app is currently being tested, and can only be accessed by developer-approved testers. If you think you should have access, contact the developer.

@windowshopr
Copy link

windowshopr commented Jan 23, 2023

Same:

image

This could be because this app setup needs some time to figure stuff out before GYB works, or that we had to set the
"External" app type instead of Internal (which isn't available), or something else. Not sure yet.

@davidromerot
Copy link

Any solution to this?

I get the same error, just tried (Feb 16 2023)

@Onthrax
Copy link

Onthrax commented May 29, 2023

Had the same issue. In my case I fixed it by adding the e-mailaddress as a test user. After that it worked fine.

@gene1wood
Copy link

@kalebzettl Would you be open to updating your comment above to insert the step that @Onthrax discovered where setting a "Test user" is actually necessary?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants