Not which location oauth goes in. This is a definite bug in google’s new branding experience for oauth.
I am in new experience and my branding page is all filled in but when I click ‘create client’ in ‘clients’ section of ‘Google Auth Platform’, it says “To create an OAuth client ID, you must first configure your consent screen” so I click button there ‘configure consent screen’ which brings me to the branding section which is ALL FILLED OUT ALREADY!!!. I click ‘Data Access’, it is filled out.
I then click some random GCP service to come back in to the old experience. I click ‘APIs and Services’ → ‘credentials’ and click ‘create credentials’ and select ‘oauth client id’ . It is saying “To create an OAuth client ID, you must first configure your consent screen” so I click button there 'configure consent screen" so I click configure consent screen AGAIN and now it is a blank form that I refill in everything but it errors out with
An error saving your app has occurred
The request failed because one of the field of the resource is invalid.
Request ID: 7314319248615616090
spinning in circles with a bug and no way to report the bug? I am stuck and can’t create oauth here in GCP.
This sounds like a frustrating issue, and unfortunately, it’s not uncommon to encounter problems with complex tools like Google’s OAuth setup. Let’s go through steps to potentially resolve the issue and escalate it if necessary:
Steps to Resolve
Clear Cache and Cookies:
Sometimes, cached data can interfere with Google services.
Clear your browser cache and cookies, then try the process again.
Use a Different Browser or Incognito Mode:
Some browser extensions or settings can interfere. Using a clean browser session can help isolate the issue.
Check Your Permissions:
Ensure your Google Cloud Project has the proper permissions. Double-check that you’re an Owner or have sufficient permissions to manage OAuth credentials.
Double-Check Your Consent Screen Configuration:
Even if it appears filled out, try reviewing all sections under APIs & Services > OAuth consent screen:
Verify that Scopes are added.
Check for required fields in the “App information” section.
Ensure there’s no invalid or mismatched data.
Switch Between New and Old Experiences:
While you’ve already attempted this, toggling between experiences sometimes syncs inconsistencies.
Ensure all fields are identical when you return to the new experience.
Validate App Data:
Review fields for invalid data, especially in required sections (e.g., URLs, emails, or text fields).
Ensure the Authorized domains field under the consent screen matches your app’s URLs.
Test in a New Project:
If feasible, try setting up a new project in the Google Cloud Platform and repeat the steps to isolate whether the issue is specific to your current project.
I have the same issue but have been able to work around it. After clicking Create in Configure Consent Screen. I am returned the Google Auth Platform Branding page; refresh the browser page. Now when I click Clients on the left and then Click +Create Client, I can proceed.
