Is OAuth Consent Screen broken with the side by side rollout of the new interface?

[bstinson]

I don't have a support plan that allows me to contact GCP support so posting this here in the hopes that they will see it.

A new OAuth Consent Screen configuration flow has been rolled out side by side with the old one before the old one is deprecated. If you try to use the old one you get an error indicating a field is not filled in. The field doesn't exist on the old screen to fill in though.
The error:
```json
{ "error": { "code": 3, "message": "The request failed because one of the field of the resource is invalid.", "details": [ { "@type": "type.googleapis.com/google.rpc.ErrorInfo", "reason": "FIELD_INVALID", "domain": "clientauthconfig.googleapis.com", "metadata": { "error_field_name": "[\"UpdateBrandWithMaskRequest.brand_id\"]", "error_field_value": "[\"0\"]" } } ] } }
```
If you switch to the new flow you get a message saying "Branding changes saved!" that pops up at the bottom. This same message occurs if you make any updates and save the Branding page, however when you go to Clients to create an OAuth Client ID you are met with a message and button stating that you have to configure your OAuth Consent Screen to make a Client ID so both the old and the new flows appear to be broken at this time. 

[reinc]

Hi @bstinson,

Welcome to Google Cloud Community! 

A relevant discussion on StackOverflow suggests that the issue is likely related, with many users, as mentioned by @Ahmed, it is recommended by replacing the AppName for the Project ID.

For more information, you may refer to these documentations:

• Developer Console Direct Link - Try using the direct link to the consent screen configuration within the Google Developer Console (rather than navigating through the GCP console) might help.
• OAuth 2.0 for Mobile & Web Applications - This is the core documentation for Google's OAuth implementation.
• Setting up the OAuth 2.0 Consent Screen -  This should guide you through the new consent screen setup.

If you have questions, clarification and need further help while you mentioned you don't have a support plan, please feel free to reach out to our support team.

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.

[bstinson · Accepted solution]

I had previously tried updating all fields to different values and had no success. Google Engineers appear to have fixed this issue now though as I can get to the client id creation screen in the updated flow today and can no longer use the old flow.

[tgarg01]

Facing the same issue on 2/3/2025. Whatever fix they made seems to have regressed.

[rai__bread]

I am also facing this issue on Feb 6, 2025