35

I am trying to register my app for Oauth consent screen, so that I can create a OAuth client ID. I keep getting this validation error at end of the form, even though I have submitted everything correctly.

An error occurred while saving your app

And this error does not state which input in the form is invalid. Also in the network tab of development tools window, everytime I submit the request, I can see a POST request being initiated and it fails with following error.

{"error":{"code":3,"message":"The request failed because one of the field of the resource is invalid.","details":[{"@type":"type.googleapis.com/google.rpc.PreconditionFailure","violations":[{"type":"client_auth_config","subject":"?error_code=9&error_field_name=UpdateBrandWithMaskRequest.brand_id&error_field_value=0"}]}]}}.

Any suggestions on how to fix this is highly appreciated. I have contacted the google support about this issue as well, but as of now they're saying everything works on their end and clear cache and cookies but it doesn't work. I have attached here a capture of consent config wizard I'm using as well.

I have attached here a capture of consent config wizard I'm using as well.

v1shva
  • 1,261
  • 3
  • 13
  • 28
  • Can you verify if your user have the `Oauth Consent Creator` Role and the `Oauth Creator` Role ? – Bruno Sep 18 '20 at 17:18
  • I am using the owner account for the project to create consent screen, so I assume I have the necessary permissions. – v1shva Sep 21 '20 at 08:33
  • Check your emails for any message from Google, especially from `Trust & Safety` team. If the team sent an email requesting more information from you, your validation can be suspended. Verify your spam-box. – Bruno Sep 22 '20 at 17:48
  • I have checked no emails, support case is still ongoing, no resolutions. – v1shva Sep 23 '20 at 04:45
  • HI , Did you get any solution on that? ,I am facing same error that "An error saving your app has occurred". – Priya Sep 23 '20 at 11:22
  • 1
    Hi there, I'm also having the same issue. Did the same process about a week ago and it was fine - before the new layout for the "consent screen". Their error message don't even say what's the field with an error and their docs are out of date! – Carlos Zinato Sep 23 '20 at 16:17

17 Answers17

113

Put the Project ID in App Name

Ahmed Abo 6
  • 1,151
  • 2
  • 9
  • 11
  • 18
    It's weird that it actually works. Thanks. – Iqbal Apr 18 '21 at 05:48
  • 5
    This is worked, it seems a bug on google side. – Zhou Haibo Aug 23 '21 at 14:24
  • 5
    That is the most pathetic bug I've seen in a very long time. Not only that, but it's now Nov '21 (2 and a half years later), and it's still an issue, with absolutely no indication of what the problem is. Thanks for the tip – Avrohom Yisroel Nov 09 '21 at 16:35
  • 1
    Digging into this further, this likely only solves the issue because the name that was used was failing one of the checks for some reason. The project ID is guaranteed to be a valid application name, so this workaround will always fix the issue. I would recommend looking into the response to the request that is sent when you click to "SAVE AND CONTINUE", the response will likely contain a more descriptive error message that will guide you to fix the application name. – zr0gravity7 Dec 23 '21 at 06:44
  • 1
    I have posted an explanation as an answer below. – zr0gravity7 Dec 23 '21 at 06:53
  • 1
    That was weird , but it worked thanks – Aness Nov 13 '22 at 15:32
  • 1
    Worked, but seems weird. – Shahzaib Ayyub Feb 09 '23 at 20:11
  • 1
    as on june-2023, the bug is still not fixed -_- maybe they are busy updating bard AI -_- – Farhan Ibn Wahid Jun 06 '23 at 13:33
11

Try adding your support email to Firebase console. Go to firebase console->settings->General->Support Email->Add Email. Now while creating oAuth consent screen add same email id developer contact information as well as support email. It worked for me.

Kalind
  • 134
  • 1
  • 4
6

To expand on the top answer, there are numerous underlying reasons why this step of the app registration would fail. In the case where the application name is not valid (fails any of the checks that Google Cloud Platform enforces), then setting the application name to the project ID is guaranteed to fix the problem, as the project ID will always happen to be a valid application name.

It may be worth digging into the underlying validation error, which can be achieved by inspecting the network request that is sent upon submitting the form. In the "Network" tab of the Developer Tools, select the POST request that is captured after clicking the "SAVE AND CONTINUE" button. The "Response" tab (shown below for my case) should display an error object with a more descriptive message.

In my case, it seems that the application name was deemed abusive:

The request has been classified as abusive and was not allowed to proceed.

which I suspect is because it contains the word "Google".

enter image description here

zr0gravity7
  • 2,917
  • 1
  • 12
  • 33
4

I had the same problem, indeed your App name must be identical to your Project ID that you chose when creating the project

Oreol Noumodong
  • 141
  • 1
  • 1
  • 9
3

I was facing the same issue , it was because I was using "Google" in the App name.I removed it and it works for me.

Muhammad Muneeb Waqas
  • 69
  • 4
2

What @Kalind said helped me to resolve the problem. So login to firebase console, chose the project you are trying to create an OAuth Consent too. And then click settings-> General-> Support Email-> Add Email from dropdown. Now when I go back to google cloud console under the Oauth consent screen, I can see that I have one registered to that project.

Kasper Johansen
  • 41
  • 4
0

Thanks for reporting this everyone. I've also had the same problem for different apps and @Kalind suggestion fixes the problem. On Firebase project's settings there's a new field now called "Support email" where you can select your support email address. This will fix your issue like @Kalind and @Kasper said. I'm just adding a screenshot to make it more clear for those with the same problem. Thanks!

firebase support email field

Carlos Zinato
  • 591
  • 7
  • 19
0

For me there was an email in there already (owner of account email). I had to invite another email > accept invite > change email > save > then change back > then I could proceed with the OAuth Consent Screen.

To change the support email on the Firebase Console you go to: https://console.firebase.google.com/ > select Cog > Project Settings > General tab > Support Email

CWSupport
  • 1
0

I reached this page is because of testing Google Login.
I faced this issue creating "OAuth consent screen".
But I didn't need this to create.
Just go to "Domain verification" page and "Add Domain".
There you may need to add 'txt record' in DNS Setting to prove you owned the domain.
After adding domain, go to "Credentials" page.
It is ready to choose the "Application type" like google guide
!!! pls enjoy !!!

WHY
  • 258
  • 1
  • 8
0

I used the app Id as my App Name in the OAuth consent screen setup page.

Micheal Adisa
  • 11
  • 5
0

If you are trying to use group email from gsuite in App consent/Firebase support, you must be the group owner, and do not need that group email address on any IAM role.

Jijo John
  • 1,368
  • 2
  • 17
  • 31
0

I believe the name of the application requesting access simply needs to be different from the name of the Google project.

MilletSoftware
  • 3,521
  • 2
  • 12
  • 15
0

This Error was come due to the project name is the same as the app name. So your app name and project name must be differnet

Shakeel Riaz
  • 1
0

to expand on the helpful post of @zr0gravity7 I checked the 'response' in the developer con{"error":

{"code":3,"message":"com.google.apps.framework.request.BadRequestException: At least one field must be updated."}}

I simply changed one field, and the save now succeeded.

(This is a very disappointing design of the form error checking)

Stephen Shaw
  • 31
  • 4
0

The app name must be unique across Google. Modify the app name a bit.

Solomon Botchway
  • 353
  • 3
  • 9
0

I was facing the same error. I was creating a project to check Google identity service. So, I named my project googleIdentityService, Then, I got the error "An error saving your app has occurred" when saving. But when I removed the word google from my project name it's surprisingly worked.

Minhaz
  • 114
  • 2
  • 8
0

I think I just had another tab open with the OAuth consent screen creation in progress :see_no_evil:

Continuing in the original tab fixed the issue for me.

I did NOT need Firebase and I did NOT need to use my project id in the app name

Clemens
  • 653
  • 6
  • 8