Hi @dfrost
Do you have the same problem if you rename the button to “Sign in with Google” as their branding suggests?
https://developers.google.com/identity/branding-guidelines
This is the only difference I’m able to see between your button and the one on their site.
Thread Starter
dfrost
(@dfrost)
thanks for your quick response. i have now changed it and resubmitted it. i will update this thread if that was the solution
the text that google recommends reads…
“Text
To encourage users to click the button, we recommend the call-to-action text “Sign in with Google” or “Sign up with Google”. It should be clear to the user that they are signing in to your app or signing up for your app with their Google credentials, not signing up or registering for a Google account on your app.”
they may feel “continue with google” is misleading i guess but that was the text you have saved in your icon section.
thanks again for your quick response!
Thread Starter
dfrost
(@dfrost)
Well i changed the wording for the icon and now they again denied it saying this….
i am not sure where they are getting that url from and there isn’t even an option to change an icon url from the auth consent screen so i am confused right now
Thank you for your response!
Consistent Branding
Unfortunately, we cannot proceed with the verification process unless you provide the below issue.
To fix this issue, update the icon url on the OAuth Consent Screen as it doesn’t matches with the Homepage Icon , making sure that your project accurately represents its true identity to Google users.
We detected the following issue(s):
Icon URL on the consent screen does not match the icon on your homepage
icon_url: https://lh3.googleusercontent.com/bgfudSvTKutNCpLb3-ufx5noroI3zGAkC0w8zIDv-6ieeCPmuAQD9h5ecxBYXyXz5S4
Hi @dfrost
To fix this issue, update the icon url on the OAuth Consent Screen as it doesn’t matches with the Homepage Icon , making sure that your project accurately represents its true identity to Google users.
This seems to suggest that you’re using a different logo on your website, and at the Google app you made.
The logo you upload to your app shows up on the OAuth Consent Screen, which appears when the “Sign up with Google” button is pressed:
https://docs.arris.com/bundle/cloudpath-52-setting-up-google-guide/page/GUID-A103C239-778E-4C95-B0D3-2D41D7ECA4FB.html
Can you check the logo you uploaded to your app? E.g. if the logo you use on your site is a green leaf icon, then that exact logo should be used in the app as well.
Thread Starter
dfrost
(@dfrost)
as i said before, on my auth consent screen, there is no option to change a url. there was only an option to upload the icon so i cut and pasted it from paint and uploaded it.
but this isn’t what they are talking about. they are talking about a url and the one they mention is https://lh3.googleusercontent.com/bgfudSvTKutNCpLb3-ufx5noroI3zGAkC0w8zIDv-6ieeCPmuAQD9h5ecxBYXyXz5S4. i don’t see that url ANYWHERE in my credentials OR auth screen
the only thing i deviated from in the nextend instruction is the logo. it skipped that part in the instruction for some reason and now i am having a problem with it. in the app itself, i don’t believe it gives us a url for the logo. when i change the text for the logo as originally suggested, where is that saved?
Plugin Support
Laszlo
(@laszloszalvak)
Hi @dfrost
I assume under “icon url on the OAuth Consent Screen” they exactly meant the “Application logo” where you can upload the logo of your site.
Anyways selecting an “Application logo” is optional when you create a Google App. If you would like to set a Logo for your App, that users see when they connect with social login then Google will need to review your App as it is stated in the OAuth consent screen page of Google:
OAuth verification
To protect you and your users, your consent screen and application may need to be verified by Google. Verification is required if your app is marked as Public and at least one of the following is true:
- Your app uses a sensitive and/or restricted scope
- Your app displays an icon on its OAuth consent screen
- Your app has a large number of authorized domains
- You have made changes to a previously-verified OAuth consent screen
The verification process may take up to several weeks, and you will receive email updates as it progresses. Learn more about verification.
Before your consent screen and application are verified by Google, you can still test your application with limitations. Learn more about how your app will behave before it’s verified.
So as my colleague mentioned, if you use an Application logon you need to make sure the logo is exactly the same as the one appearing on your Homepage.
According to the Icon URL Google sent you:
https://lh3.googleusercontent.com/bgfudSvTKutNCpLb3-ufx5noroI3zGAkC0w8zIDv-6ieeCPmuAQD9h5ecxBYXyXz5S4
it seems you probably uploaded an image about the Google social button itself, but not the logo of your Website.
So could could you get in touch with use over the ticket system, please: https://nextendweb.com/contact-us/nextend-social-login-support/?ref=https://ww.wp.xz.cn/support/topic/request-denied-3/#post-13145286
and send us:
-a link to the page where you are trying to use the Google social button.
-and a screenshot about your “Google – OAuth consent screen” where I see your current “Application logo” and the “Authorized domains”.
Best regards,
Laszlo.
