Status Update
Comments
kn...@google.com <kn...@google.com>
le...@fjuul.com <le...@fjuul.com> #2
This is frustrating without end.
kn...@google.com <kn...@google.com> #3
kn...@google.com <kn...@google.com> #4
ka...@gmail.com <ka...@gmail.com> #5
Because there is no verification at that day, I uploaded the logo.
Recently, I add a redirect URI, the verification process was started.
Not removing the logo stops me from updating my app.
ve...@gmail.com <ve...@gmail.com> #6
ti...@gmail.com <ti...@gmail.com> #7
lu...@gmail.com <lu...@gmail.com> #8
ak...@gmail.com <ak...@gmail.com> #9
an...@gmail.com <an...@gmail.com> #10
st...@psp-webtech.co.uk <st...@psp-webtech.co.uk> #11
I uploaded a logo without realizing this will trigger a verification in January 2020. The app is still being verified and it's pretty much useless. Terrible!
kn...@google.com <kn...@google.com> #12
ju...@google.com <ju...@google.com> #13
(EDIT: Confirmed that the below no longer works.)
If anybody is in an immediate need to remove the logo before the feature arrives, there is a workaround available in the following Stackoverflow answer:
ni...@peakmetrics.com <ni...@peakmetrics.com> #14
al...@gmail.com <al...@gmail.com> #15
s....@computime4it.com <s....@computime4it.com> #16
en...@gmail.com <en...@gmail.com> #17
Stuck for ~2 weeks on same status.
er...@gmail.com <er...@gmail.com> #18
ne...@gmail.com <ne...@gmail.com> #19
no...@gmail.com <no...@gmail.com> #20
[Deleted User] <[Deleted User]> #21
This is something you can do even when you are stuck in this state: Credentials => "+ CREATE CREDENTIALS" in the top bar.
It took me a while to figure this out, since the most prominent thing on the Credentials page is a banner asking me to configure the consent screen (which would have made this a catch-22, but luckily it's only "suggested", not required).
sa...@gmail.com <sa...@gmail.com> #22
mi...@mentorworks.com <mi...@mentorworks.com> #23
This is the most recent hack that folks have claimed works:
Apparently issuing a properly constructed DELETE request to the brand endpoint at
Thank you in advance.
[Deleted User] <[Deleted User]> #24
ra...@yahoo.com <ra...@yahoo.com> #25
al...@gmail.com <al...@gmail.com> #26
lc...@gmail.com <lc...@gmail.com> #27
jo...@gmail.com <jo...@gmail.com> #28
la...@gmail.com <la...@gmail.com> #29
om...@gmail.com <om...@gmail.com> #30
al...@gmail.com <al...@gmail.com> #31
omg we still couldn't find out how to delete just a f* logo?
ja...@gmail.com <ja...@gmail.com> #32
[Deleted User] <[Deleted User]> #33
ko...@ilio.pl <ko...@ilio.pl> #34
wa...@gmail.com <wa...@gmail.com> #35
Can't remove logo uploaded.
I am working on a project to learn .Net Core and wanted to integrate Google+ Api to implement Security Token Service (STS) for my application. On following the process, I uploaded an image just to give an image to my app and than the verification than prompted to me.
Here I want to remove logo so I can continue working on instead of waiting 4-6 weeks for verification.
A 'Remove Logo' button is much more needed.
te...@gmail.com <te...@gmail.com> #36
fa...@gmail.com <fa...@gmail.com> #37
ge...@gmail.com <ge...@gmail.com> #38
2)
It says Create an OAuth 2.0 client ID Set the application type to Other.
There is no type other in my list. I am not sure if it has to do with verification ..But help is missing info
se...@gmail.com <se...@gmail.com> #39
la...@gmail.com <la...@gmail.com> #40
[Deleted User] <[Deleted User]> #41
th...@gmail.com <th...@gmail.com> #42
te...@gmail.com <te...@gmail.com> #43
di...@gmail.com <di...@gmail.com> #44
cs...@umich.edu <cs...@umich.edu> #45
as...@gmail.com <as...@gmail.com> #46
ni...@gmail.com <ni...@gmail.com> #47
ra...@gmail.com <ra...@gmail.com> #48
tz...@gmail.com <tz...@gmail.com> #49
ma...@gmail.com <ma...@gmail.com> #50
tz...@gmail.com <tz...@gmail.com> #51
ma...@gmail.com <ma...@gmail.com> #52
(404 or 400 errors)
I'm asking no sensitive nor restricted scope for the OAuth consent screen.
Submitted for verification 3 days ago but still got no validation nor message from Google.
Creating a new app would mean losing all public reviews / usage stats :-(
Very frustrating & time wasting.
Please :
- Indicate clearly that uploading / updating the app icon requires app validation (next to upload field?)
- Allow to remove the app icon to skip validation process (if not required by other settings such as sensitive scopes)
ad...@chardaeconsult.com <ad...@chardaeconsult.com> #53
al...@gmail.com <al...@gmail.com> #54
ma...@gmail.com <ma...@gmail.com> #55
Wow. This beats the other recent f-up by Google: Google Play pre-launch-reports that report crashes from unrelated mobile apps installed on Googles devices. Lucky I just created my project and can still delete and create a new one.
du...@gmail.com <du...@gmail.com> #56
bu...@gmail.com <bu...@gmail.com> #57
ja...@general-scripting.com <ja...@general-scripting.com> #58
de...@yahoo.com.br <de...@yahoo.com.br> #59
he...@gmail.com <he...@gmail.com> #60
ya...@gmail.com <ya...@gmail.com> #61
vi...@gmail.com <vi...@gmail.com> #62
kt...@gmail.com <kt...@gmail.com> #63
ra...@gmail.com <ra...@gmail.com> #64
mo...@gmail.com <mo...@gmail.com> #65
su...@feedoptimise.com <su...@feedoptimise.com> #66
ad...@gmail.com <ad...@gmail.com> #67
ad...@feedoptimise.com <ad...@feedoptimise.com> #68
ch...@gmail.com <ch...@gmail.com> #69
jn...@gmail.com <jn...@gmail.com> #70
ol...@gmail.com <ol...@gmail.com> #71
gu...@tabextend.com <gu...@tabextend.com> #72
ly...@gmail.com <ly...@gmail.com> #73
st...@gmail.com <st...@gmail.com> #74
ed...@gmail.com <ed...@gmail.com> #75
da...@gmail.com <da...@gmail.com> #76
I am still experiencing this and there is no any workaround. Please someone from google give response or a fix !!!
cl...@gmail.com <cl...@gmail.com> #77
sa...@codigames.com <sa...@codigames.com> #78
ra...@gmail.com <ra...@gmail.com> #79
The SO solutions didn't work for me.
Had to recreate the project to get rid of the logo
br...@pappin.ca <br...@pappin.ca> #80
je...@gmail.com <je...@gmail.com> #81
ga...@gmail.com <ga...@gmail.com> #82
ry...@gmail.com <ry...@gmail.com> #83
bi...@gmail.com <bi...@gmail.com> #84
zu...@gmail.com <zu...@gmail.com> #85
cr...@gmail.com <cr...@gmail.com> #86
we...@gmail.com <we...@gmail.com> #87
+1
na...@clearcapital.com <na...@clearcapital.com> #88
[Deleted User] <[Deleted User]> #89
ho...@ixon.cloud <ho...@ixon.cloud> #90
sa...@gmail.com <sa...@gmail.com> #91
le...@gmail.com <le...@gmail.com> #92
ko...@gmail.com <ko...@gmail.com> #93
ic...@gmail.com <ic...@gmail.com> #94
dm...@gmail.com <dm...@gmail.com> #95
da...@gmail.com <da...@gmail.com> #96
ph...@gmail.com <ph...@gmail.com> #97
gu...@gmail.com <gu...@gmail.com> #98
hu...@wisebits.com <hu...@wisebits.com> #99
sm...@student.uni-lj.si <sm...@student.uni-lj.si> #100
k....@robotiq.com <k....@robotiq.com> #101
k5...@gmail.com <k5...@gmail.com> #102
mi...@gmail.com <mi...@gmail.com> #103
pi...@gmail.com <pi...@gmail.com> #104
am...@gmail.com <am...@gmail.com> #105
go...@gmail.com <go...@gmail.com> #106
ss...@neowiz.com <ss...@neowiz.com> #107
rn...@gmail.com <rn...@gmail.com> #108
ch...@gmail.com <ch...@gmail.com> #109
le...@populationgenomics.org.au <le...@populationgenomics.org.au> #110
ni...@gmail.com <ni...@gmail.com> #111
te...@gmail.com <te...@gmail.com> #112
I would appreciate it if Google made this specific action easier. The UI for OAuth verification is fairly non-intuitive, and thus it was not obvious that I had indeed uploaded some kind of icon a while ago during development. I'm about to start trying stack overflow suggestions to try and fix my app before launch!
te...@gmail.com <te...@gmail.com> #113
sh...@gmail.com <sh...@gmail.com> #114
wi...@gmail.com <wi...@gmail.com> #115
ch...@secondnature.io <ch...@secondnature.io> #116
[Deleted User] <[Deleted User]> #117
[Deleted User] <[Deleted User]> #118
ko...@gmail.com <ko...@gmail.com> #119
te...@gmail.com <te...@gmail.com> #120
It's shocking how many developers this currently impacts, and how it has had no update?
ti...@gmail.com <ti...@gmail.com> #121
te...@gmail.com <te...@gmail.com> #122
If you're following this issue, please consider following and upvoting the issue where I re-filed this as a bug and not a feature request:
[Deleted User] <[Deleted User]> #123
ty...@gmail.com <ty...@gmail.com> #124
go...@getontop.at <go...@getontop.at> #125
my...@gmail.com <my...@gmail.com> #126
gg...@aztech.us <gg...@aztech.us> #127
ro...@gmail.com <ro...@gmail.com> #128
il...@sevenapps.co <il...@sevenapps.co> #129
th...@gmail.com <th...@gmail.com> #130
[Deleted User] <[Deleted User]> #131
dm...@gmail.com <dm...@gmail.com> #132
or...@gmail.com <or...@gmail.com> #133
ti...@gmail.com <ti...@gmail.com> #134
lu...@abenergie.it <lu...@abenergie.it> #135
ma...@skylig.ht <ma...@skylig.ht> #136
hi...@gmail.com <hi...@gmail.com> #137
gu...@gmail.com <gu...@gmail.com> #138
[Deleted User] <[Deleted User]> #139
te...@gmail.com <te...@gmail.com> #140
Update: they marked the bug I filed as won't fix, intended behavior:
(🤔🤦♂️)
de...@outintech.com <de...@outintech.com> #141
fa...@gmail.com <fa...@gmail.com> #142
d0...@gmail.com <d0...@gmail.com> #143
qu...@gmail.com <qu...@gmail.com> #144
my...@webartics.com <my...@webartics.com> #145
gu...@gmail.com <gu...@gmail.com> #146
ja...@paradigm.co <ja...@paradigm.co> #147
ru...@pcnllc.net <ru...@pcnllc.net> #148
It doesn't make any sense to have this logo be stuck without at least submission verification and acceptance:
"Is this the logo you would like to submit? Verification will be required and could take 4-6 weeks. Choose YES to continue, or choose NO to cancel this step."
I'll try deleting the project and recreating it.... What a pain to set all that up again.
de...@meetgradient.com <de...@meetgradient.com> #149
hy...@gmail.com <hy...@gmail.com> #150
ni...@hackruiter.com <ni...@hackruiter.com> #151
yo...@gmail.com <yo...@gmail.com> #152
ts...@gmail.com <ts...@gmail.com> #153
ip...@gmail.com <ip...@gmail.com> #154
am...@gmail.com <am...@gmail.com> #155
I didn't expect that I can't remove my logo when I add it. It's totally a WRONG DESIGN. Can't imagine such design is made by Google :(
Please fix it, if you truly listen to users' voice.
sa...@kuurahealth.com <sa...@kuurahealth.com> #156
Method described in
bg...@cast.org <bg...@cast.org> #157
is...@robotistan.com <is...@robotistan.com> #158
su...@userfront.com <su...@userfront.com> #159
fr...@startsole.org <fr...@startsole.org> #160
[Deleted User] <[Deleted User]> #161
ra...@gmail.com <ra...@gmail.com> #162
mo...@gmail.com <mo...@gmail.com> #163
[Deleted User] <[Deleted User]> #164
ha...@gmail.com <ha...@gmail.com> #165
do...@gmail.com <do...@gmail.com> #166
te...@gmail.com <te...@gmail.com> #167
jeopardy theme plays
st...@antiochfc.org <st...@antiochfc.org> #168
The email I get from GCP says "If your app doesn't need to display an icon, you can skip the verification process." as if there's a way to remove it, but alas, there is not.
pd...@gmail.com <pd...@gmail.com> #169
ja...@mgenio.com <ja...@mgenio.com> #170
tr...@gmail.com <tr...@gmail.com> #171
we...@iconicnewspapers.ie <we...@iconicnewspapers.ie> #172
th...@gmail.com <th...@gmail.com> #173
ty...@gmail.com <ty...@gmail.com> #174
Even more frustrating is that you can't even get in touch with Google to remove the icon / skip the verification without buying their technical support plan on Google Cloud.
Such a convoluted process with too much trust in their own system.
ma...@uchile.cl <ma...@uchile.cl> #175
to...@gmail.com <to...@gmail.com> #176
ch...@gmail.com <ch...@gmail.com> #177
> Even more frustrating is that you can't even get in touch with Google to remove the icon / skip the verification without buying their technical support plan on Google Cloud.
We pay many thousands for technical support and even that doesn't help in this case: they still can't remove the icon manually :)
ba...@gmail.com <ba...@gmail.com> #178
m4...@gmail.com <m4...@gmail.com> #179
li...@gmail.com <li...@gmail.com> #180
_p...@portable.io <_p...@portable.io> #181
yo...@gmail.com <yo...@gmail.com> #182
ce...@consultsystems.ru <ce...@consultsystems.ru> #183
to...@bookfocal.com <to...@bookfocal.com> #184
le...@wisestamp.com <le...@wisestamp.com> #185
+1
se...@gmail.com <se...@gmail.com> #186
ef...@gmail.com <ef...@gmail.com> #187
One stupid solution is to create a new project with a new oauth.
tu...@gmail.com <tu...@gmail.com> #188
This is an unacceptable mistake from a huge corporation like Google
lj...@gmail.com <lj...@gmail.com> #189
SHIT!!!
ma...@gmail.com <ma...@gmail.com> #190
mf...@gmail.com <mf...@gmail.com> #191
yh...@gmail.com <yh...@gmail.com> #192
[Deleted User] <[Deleted User]> #193
[Deleted User] <[Deleted User]> #194
ma...@gmail.com <ma...@gmail.com> #195
so...@gmail.com <so...@gmail.com> #196
se...@movio.co <se...@movio.co> #197
ki...@gmail.com <ki...@gmail.com> #198
de...@gmail.com <de...@gmail.com> #199
ni...@gmail.com <ni...@gmail.com> #200
nh...@gmail.com <nh...@gmail.com> #201
[Deleted User] <[Deleted User]> #202
al...@worldiety.de <al...@worldiety.de> #203
yu...@gmail.com <yu...@gmail.com> #204
jo...@gmail.com <jo...@gmail.com> #205
br...@gmail.com <br...@gmail.com> #206
de...@gmail.com <de...@gmail.com> #207
ce...@gmail.com <ce...@gmail.com> #208
me...@erwinlengkeek.nl <me...@erwinlengkeek.nl> #209
re...@gmail.com <re...@gmail.com> #210
I try to create the brand with this line:
gcloud alpha iap oauth-brands create --application_title --support_email
but I get the error mesage:
INVALID_ARGUMENT: Request contains an invalid argument.
Anyone who found a solution?
ar...@gmail.com <ar...@gmail.com> #211
ch...@gmail.com <ch...@gmail.com> #212
They don't. At the initial setup, you was told that uploading a logo requires verification. Now that's your problem, not their :)
[Deleted User] <[Deleted User]> #213
ni...@teachertapp.co.uk <ni...@teachertapp.co.uk> #214
ni...@teachertapp.co.uk <ni...@teachertapp.co.uk> #215
em...@foxiko.com <em...@foxiko.com> #216
wi...@gmail.com <wi...@gmail.com> #217
[Deleted User] <[Deleted User]> #218
Pretty please with sugar on top Google, Sir.
to...@gmail.com <to...@gmail.com> #219
[Deleted User] <[Deleted User]> #220
dz...@gmail.com <dz...@gmail.com> #221
no...@gmail.com <no...@gmail.com> #222
tr...@exwe.de <tr...@exwe.de> #223
yo...@gmail.com <yo...@gmail.com> #224
ju...@gmail.com <ju...@gmail.com> #225
mu...@gmail.com <mu...@gmail.com> #226
Ma...@concishare.com <Ma...@concishare.com> #227
pa...@gmail.com <pa...@gmail.com> #228
sk...@gmail.com <sk...@gmail.com> #229
ma...@mediaonmars.com.au <ma...@mediaonmars.com.au> #230
ni...@gmail.com <ni...@gmail.com> #231
wi...@gmail.com <wi...@gmail.com> #232
sh...@gmail.com <sh...@gmail.com> #233
kr...@gmail.com <kr...@gmail.com> #234
al...@hotkey.no <al...@hotkey.no> #235
ar...@gmail.com <ar...@gmail.com> #236
[Deleted User] <[Deleted User]> #237
Could we please get an update on this issue?
Best regards,
go...@gmail.com <go...@gmail.com> #238
ab...@gmail.com <ab...@gmail.com> #239
ja...@google.com <ja...@google.com> #240
+1
he...@shmoodyapp.com <he...@shmoodyapp.com> #241
[Deleted User] <[Deleted User]> #242
wo...@gmail.com <wo...@gmail.com> #243
wa...@gmail.com <wa...@gmail.com> #244
ag...@gmail.com <ag...@gmail.com> #245
de...@twentyies.com <de...@twentyies.com> #246
sh...@gmail.com <sh...@gmail.com> #247
pr...@topcorretores.com.br <pr...@topcorretores.com.br> #248
sh...@gmail.com <sh...@gmail.com> #249
lo...@gmail.com <lo...@gmail.com> #250
le...@gmail.com <le...@gmail.com> #251
I am very disappointed by google right now. Waste of time and frustration. This must be fixed yesterday!
uc...@gmail.com <uc...@gmail.com> #252
da...@gmail.com <da...@gmail.com> #253
ge...@gmail.com <ge...@gmail.com> #254
zh...@highlight.mobi <zh...@highlight.mobi> #255
al...@fornuto.com <al...@fornuto.com> #256
[Deleted User] <[Deleted User]> #257
an...@privatix.io <an...@privatix.io> #258
yo...@gmail.com <yo...@gmail.com> #259
ib...@gmail.com <ib...@gmail.com> #260
te...@gmail.com <te...@gmail.com> #261
As an update, mine was verified about a week after my comment. So, for all of those out there waiting on theirs, have hope :)
dy...@gmail.com <dy...@gmail.com> #262
ke...@gmail.com <ke...@gmail.com> #263
+1
+1
+1
+1
+1
+1
aw...@gmail.com <aw...@gmail.com> #264
How the hell is this still a thing, with zero justification from Google.
ja...@koer.co.za <ja...@koer.co.za> #265
[Deleted User] <[Deleted User]> #266
as...@gmail.com <as...@gmail.com> #267
je...@frenchfrysoftware.com <je...@frenchfrysoftware.com> #268
pu...@gmail.com <pu...@gmail.com> #269
jo...@gmail.com <jo...@gmail.com> #270
da...@gmail.com <da...@gmail.com> #271
+1
ym...@gmail.com <ym...@gmail.com> #272
mi...@gmail.com <mi...@gmail.com> #273
ky...@wintaur.com <ky...@wintaur.com> #274
ja...@xwp.co <ja...@xwp.co> #275
al...@gmail.com <al...@gmail.com> #276
ja...@bainet.com <ja...@bainet.com> #277
fr...@gmail.com <fr...@gmail.com> #278
je...@gmail.com <je...@gmail.com> #279
fo...@gmail.com <fo...@gmail.com> #280
zu...@divdash.com <zu...@divdash.com> #281
in...@indavelopers.com <in...@indavelopers.com> #282
ra...@gmail.com <ra...@gmail.com> #283
jp...@gmail.com <jp...@gmail.com> #284
r....@gmail.com <r....@gmail.com> #285
da...@gmail.com <da...@gmail.com> #286
ge...@gmail.com <ge...@gmail.com> #287
vi...@gmail.com <vi...@gmail.com> #288
ri...@gmail.com <ri...@gmail.com> #289
jb...@gmail.com <jb...@gmail.com> #290
in...@canozbay.com <in...@canozbay.com> #291
ce...@tryton.org <ce...@tryton.org> #292
ta...@gmail.com <ta...@gmail.com> #293
da...@carevalidate.com <da...@carevalidate.com> #294
"Upload an image, not larger than 1MB on the consent screen that will help users recognize your app. Allowed image formats are JPG, PNG, and BMP. Logos should be square and 120px by 120px for the best results."
ch...@gmail.com <ch...@gmail.com> #295
ad...@miltonfs.com <ad...@miltonfs.com> #296
ad...@miltonfs.com <ad...@miltonfs.com> #297
>kn...@google.com<kn...@google.com> #3 Jun 12, 2020 09:27AM
>This feature request is already forward to the Cloud UI product team and they are working on it. However, there is no ETA atthis time. All further updates on this feature request >should occur on this thread.
Then a month later:
>kn...@google.com<kn...@google.com> #12 Jul 16, 2020 11:33AM
>I am trying to get an update from the product team about this feature request and will get back to you soon. In the meantime your patience is highly appreciated.
The next day, a googler replied with the workaround (which was already posted in
We even had a googler who is affected by this!
> ja...@google.com<ja...@google.com> #240 Dec 9, 2021 02:47PM
> +1
This issue is approaching 2 years old. The last update we received from google was to give us a workaround which was updated that day to confirm it doesn't work anymore. Now, there is no choice but rebuilding the project for those of us affected, but can you please update us on this issue or LEAST make the wording in on the API set up screens MUCH clearer that setting an icon means the app will need verification and we will not be able to remove the icon (only replace it), and that using an icon will force us to go through verification?
Thank you.
ih...@gmail.com <ih...@gmail.com> #298
It is super strange that such a company can not automate the process and I need to follow some conversation with a bot, it is a shame.
Sorry, but I am frustrated
ta...@gmail.com <ta...@gmail.com> #299
ri...@gmail.com <ri...@gmail.com> #300
[Deleted User] <[Deleted User]> #301
oa...@gmail.com <oa...@gmail.com> #302
May we please have an update? The last update was 22 months ago in July 2020. Since then, this issue has even affected googlers, (December 2021).
We have been directed to workarounds on stack overflow that don't work. Google is relying on stackoverflow to support its products and find workarounds for google's own poor design.
This is not helping my opinion of your company, or your products.
Please provide an update on when this will be fixed. This is software, any action that is taken, must be reversible.
ad...@gmail.com <ad...@gmail.com> #303
co...@jamesbrill.co.uk <co...@jamesbrill.co.uk> #304
nu...@gmail.com <nu...@gmail.com> #305
al...@fictiondex.com <al...@fictiondex.com> #306
nu...@gmail.com <nu...@gmail.com> #307
ch...@superglue.io <ch...@superglue.io> #308
be...@gmail.com <be...@gmail.com> #309
bo...@aticastays.com <bo...@aticastays.com> #310
[Deleted User] <[Deleted User]> #311
ni...@gmail.com <ni...@gmail.com> #312
ji...@gmail.com <ji...@gmail.com> #313
h2...@gmail.com <h2...@gmail.com> #314
ar...@vungle.com <ar...@vungle.com> #315
ha...@ybmit.com.au <ha...@ybmit.com.au> #316
om...@gmail.com <om...@gmail.com> #317
ch...@evenup.ai <ch...@evenup.ai> #318
tr...@gmail.com <tr...@gmail.com> #319
ow...@steamshift.net <ow...@steamshift.net> #320
la...@gmail.com <la...@gmail.com> #321
+1
+1
pc...@gmail.com <pc...@gmail.com> #322
al...@gmail.com <al...@gmail.com> #323
wi...@windfallapps.com <wi...@windfallapps.com> #324
ta...@swc.co.il <ta...@swc.co.il> #325
de...@gmail.com <de...@gmail.com> #326
gi...@neuraldigital.com.au <gi...@neuraldigital.com.au> #327
aw...@gmail.com <aw...@gmail.com> #328
so...@gmail.com <so...@gmail.com> #329
va...@kalungi.com <va...@kalungi.com> #330
[Deleted User] <[Deleted User]> #331
da...@gmail.com <da...@gmail.com> #332
ra...@gmail.com <ra...@gmail.com> #333
lu...@gmail.com <lu...@gmail.com> #334
fi...@gmail.com <fi...@gmail.com> #335
ne...@gmail.com <ne...@gmail.com> #336
th...@gmail.com <th...@gmail.com> #337
dv...@gmail.com <dv...@gmail.com> #338
to...@gmail.com <to...@gmail.com> #339
da...@gmail.com <da...@gmail.com> #340
[Deleted User] <[Deleted User]> #341
fe...@pineapple-lab.com <fe...@pineapple-lab.com> #342
cl...@gmail.com <cl...@gmail.com> #343
je...@gmail.com <je...@gmail.com> #344
ad...@dosattack.me <ad...@dosattack.me> #345
qq...@gmail.com <qq...@gmail.com> #346
de...@koshiqa.com <de...@koshiqa.com> #347
pa...@gmail.com <pa...@gmail.com> #348
s....@gmail.com <s....@gmail.com> #349
ri...@gmail.com <ri...@gmail.com> #350
ri...@gmail.com <ri...@gmail.com> #351
pe...@gmail.com <pe...@gmail.com> #352
de...@gmail.com <de...@gmail.com> #353
wa...@gmail.com <wa...@gmail.com> #354
i....@chillgaming.net <i....@chillgaming.net> #355
la...@gmail.com <la...@gmail.com> #356
ma...@minke.app <ma...@minke.app> #357
wj...@gmail.com <wj...@gmail.com> #358
[Deleted User] <[Deleted User]> #359
sz...@gmail.com <sz...@gmail.com> #360
si...@gmail.com <si...@gmail.com> #361
I just want to complete my nearly due project for school, but considering that this has been unsolved for years now, I can't say I'm gonna get a good grade.
co...@alcanzatucima.com <co...@alcanzatucima.com> #362
pa...@tallyup.com <pa...@tallyup.com> #363
in...@garnetcontrol.app <in...@garnetcontrol.app> #364
ne...@dataverz.net <ne...@dataverz.net> #365
co...@gmail.com <co...@gmail.com> #366
I just want to use in integration with home assistant and nest thermostat and I didn't know about the logo issue so i used nest logo and now i want to remove it and i cant
ro...@gmail.com <ro...@gmail.com> #367
de...@gmail.com <de...@gmail.com> #368
+10^100
ma...@matchstiq.io <ma...@matchstiq.io> #369
af...@emirateshospitality.ae <af...@emirateshospitality.ae> #370
[Deleted User] <[Deleted User]> #371
co...@gmail.com <co...@gmail.com> #372
[Deleted User] <[Deleted User]> #373
ch...@otbc.se <ch...@otbc.se> #374
dr...@gmail.com <dr...@gmail.com> #375
df...@gmail.com <df...@gmail.com> #376
ce...@bewe.io <ce...@bewe.io> #377
cl...@gmail.com <cl...@gmail.com> #378
Google engineers are complete garbage.
dr...@gmail.com <dr...@gmail.com> #379
ni...@pfrgroup.com <ni...@pfrgroup.com> #380
je...@gmail.com <je...@gmail.com> #381
az...@kaigangames.com <az...@kaigangames.com> #382
All this just to show achievements in android games.
eu...@vivaco.com <eu...@vivaco.com> #383
sa...@lifetab.co <sa...@lifetab.co> #384
cr...@gmail.com <cr...@gmail.com> #385
v....@gmail.com <v....@gmail.com> #386
Imagine making people use a security hole in your API to workaround an issue you created by omission of a basic logical feature. From a company like Google.
gr...@arkmetrica.com <gr...@arkmetrica.com> #387
ji...@gmail.com <ji...@gmail.com> #388
st...@gmail.com <st...@gmail.com> #389
gr...@gmail.com <gr...@gmail.com> #390
[Deleted User] <[Deleted User]> #391
any comment??? why we can not remove this LOGO
It just blocking everything!
any help here???
mi...@gmail.com <mi...@gmail.com> #392
ce...@turkcell.com.tr <ce...@turkcell.com.tr> #393
ch...@gmail.com <ch...@gmail.com> #394
az...@gmail.com <az...@gmail.com> #395
jo...@greenchadigital.com <jo...@greenchadigital.com> #396
ev...@gmail.com <ev...@gmail.com> #397
na...@google.com <na...@google.com> #398
I'm happy to share that you are now able to remove your app logo from the OAuth consent screen configuration in Google Cloud Console. We know that this has been very frustrating for our developer community, and apologize for how long it has taken to give you this basic capability.
Some details about the feature:
- if your OAuth consent screen hasn't been verified, removing a logo takes effect instantly
- if you have completed verification, you cannot immediately remove your existing logo, but you can replace it and submit for re-verification (this seems counterintuitive, but it's part of our efforts to protect your developer account from abuse)
- if you are stuck in verification and want to back out, you can change the Publishing Status back to "testing" (but beware that you should only do this if your app is not live with users, otherwise it may affect their ability to sign in)
This is one of many features that we are now actively working on to improve the OAuth experience, so you spend less time on configuration and can focus on building apps that delight our shared users. Thanks for your patience, and for being part of the Google Developers community.
[Deleted User] <[Deleted User]> #399
na...@google.com <na...@google.com>
si...@gmail.com <si...@gmail.com> #400
I still failed my project
Description
Problem you have encountered: The only available workaround to delete the logo from the consent screen is this and is REALLY sketchy.
I would like to see both a button to just remove the logo and another one to cancel the verification process. At the moment there is no integrated method in the console to do this. If you mistakenly add a logo you must follow the verification process. By adding this button I expect to return to the default no image/ no verification notice situation.