# 不符合 Google 登录品牌要求 **URL:** \ **Category:** UX\ **Created:** [2018年十月10日 11:37 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177 "2018-10-10T11:37:33Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![dobbo](https://avatars.discourse-cdn.com/v4/letter/d/f08c70/32.png) [@dobbo](https://meta.discourse.org/u/dobbo)\ **Post date:** [2018年十月10日 11:37 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/1 "2018-10-10T11:37:33Z")
Setting up OAUTH for google, and they have advised that they cannot allow the request because the sign in image is not compliant with their branding requirements: > The Google sign-in button on your project’s homepage URL is not compliant with the Google sign-in branding guidelines. Please update the Google sign-in button on your website according to Google sign-in branding guidelines. > > Thank you for your patience. Please reply back to this email after your project is in compliance with the requirements above. > > [Sign in with Google Branding Guidelines  |  Google Identity  |  Google for Developers](https://developers.google.com/identity/branding-guidelines#top_of_page) Looks like the signin image on the sign up page isn’t up to date: ![image](https://global.discourse-cdn.com/meta/original/3X/1/2/12df39360dff817bc24e03b5c39db42f1c37b317.png) Can I update the image manually or does this need to be raised as a bug? ---
**Author:** ![dax](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dax/32/244677_2.png) [@dax](https://meta.discourse.org/u/dax)\ **Post date:** [2018年十月10日 12:12 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/2 "2018-10-10T12:12:58Z")
Hi Ben, thanks for the notice, we will have to modify the fontawesome icon that we currently use following the specifications indicated by Google [Sign in with Google Branding Guidelines  |  Google Identity  |  Google for Developers](https://developers.google.com/identity/branding-guidelines). ---
**Author:** ![dobbo](https://avatars.discourse-cdn.com/v4/letter/d/f08c70/32.png) [@dobbo](https://meta.discourse.org/u/dobbo)\ **Post date:** [2018年十月10日 12:16 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/3 "2018-10-10T12:16:03Z")
If I’m reading it right, it also needs to say “signin with Google” rather than just “with Google”. Thanks though! Look forward to the change. ---
**Author:** ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)\ **Post date:** [2018年十月10日 12:17 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/4 "2018-10-10T12:17:08Z")
Looks like we can change the 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. However, we do need to use the colored Google icon (on a white background), not the white Font Awesome icon: > Regardless of the text, you can’t change the size or color of the Google “G” logo. It must be the standard color version and appear on a white background. If you need to create your own custom size Google logo, start with any of the logo sizes included in the download bundle. ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [2018年十月10日 12:26 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/5 "2018-10-10T12:26:04Z")
I suspect you got an overzealous enforcement agent in this case, or else the policy must have changed very recently. Because this is the first we’ve ever heard of it in years of things working just fine. Multicolor is impossible with fonts (mostly — there are technical ways it can work in some rare cases, but this is highly dependent on the operating system) so this will take quite some time to work out. ---
**Author:** ![dobbo](https://avatars.discourse-cdn.com/v4/letter/d/f08c70/32.png) [@dobbo](https://meta.discourse.org/u/dobbo)\ **Post date:** [2018年十月10日 12:28 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/6 "2018-10-10T12:28:38Z")
I think google are in ultra paranoid mode after the Google+ nightmare they’ve been having. You won’t believe the hoops we are having to jump through to get this approved, they even wanted a video of the signup process uploaded to youtube. ---
**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\ **Post date:** [2018年十月10日 23:53 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/11 "2018-10-10T23:53:30Z")
其他正在尝试启用 Google 登录的用户能否在此告知是否存在某种规律？ 我们确实需要弄清楚，这究竟是“Google 因 Google+ 事件而失控”，还是 @dobbo 只是运气不佳（这在五年中尚属首次）。 如果我们能确认这里存在新政策执行的规律，就能决定如何优先处理此事。 Ben，短期内我建议你创建一个主题组件来替换该功能，并将其发布在 #Customization > Theme 分类下。 ---
**Author:** ![tshenry](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tshenry/32/119495_2.png) [@tshenry](https://meta.discourse.org/u/tshenry)\ **Post date:** [2018年十月11日 02:21 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/12 "2018-10-11T02:21:58Z")
I think this checks _most_ of the boxes for being acceptable by their [standards](https://developers.google.com/identity/branding-guidelines). It doesn’t fit their padding specifications, but I wonder if the padding might be somewhat flexible under the “Matching your own app’s style” wiggle room they talk about. If you think this looks good, I can post the theme component for it. ![google](https://global.discourse-cdn.com/meta/original/3X/4/d/4df0962cf72bda486ccfcd2153a67259e6402a2f.png) ---
**Author:** ![dobbo](https://avatars.discourse-cdn.com/v4/letter/d/f08c70/32.png) [@dobbo](https://meta.discourse.org/u/dobbo)\ **Post date:** [2018年十月11日 09:15 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/13 "2018-10-11T09:15:31Z")
I’m very new to this so theme components are something I hadn’t looked at. I wrote some javascript to dynamically replace the button with a “correctly” formatted button but neglected to check how the page is rendered in the first place, so this doesn’t work. Yay me! @tshenry would be happy to try with the theme component you made to see if google accept it! ---
**Author:** ![tshenry](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tshenry/32/119495_2.png) [@tshenry](https://meta.discourse.org/u/tshenry)\ **Post date:** [2018年十月11日 10:04 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/14 "2018-10-11T10:04:36Z")
Ok, I’ll try to get it online shortly. We can adjust it accordingly if Google continues to give you grief. ---
**Author:** ![MiG](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mig/32/119486_2.png) [@MiG](https://meta.discourse.org/u/MiG)\ **Post date:** [2018年十月14日 16:27 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/15 "2018-10-14T16:27:10Z")
I’ve gotten the same e-mail today on my self-hosted forum. I use Facebook, GitHub, Twitter, and Google logins. Today I received the “Action needed” e-mail telling me to be sure the sign-in button is compliant with the branding guidelines, and to reply to the e-mail when it is. Is there something I can do locally, or is it best to wait for an update? Edit: Sorry, missed @tshenry’s link. If anybody else missed it because they scroll too fast 🙂 here it is: > [@Compliant Google Login Button](https://meta.discourse.org/t/compliant-google-login-button/99276): > > This is very a small theme component that will modify the Google login button to use a compliant image instead of the default Font Awesome Google Icon. Before After Purpose More details on why you may need this component can be found in the following topic: Installation [Repository Link](https://github.com/tshenry/discourse-compliant-google-login-button) https://github.com/tshenry/discourse-compliant-google-login-button.git If you are new to installing theme components, check out this [excellent guide](https://meta.discourse.org/t/beginners-guide-to-using-discourse-themes/91966) on theme components, particularly [how…](https://meta.discourse.org/t/beginners-guide-to-using-discourse-themes/91966#heading--2-4) I’ve added it to my default theme and hopefully it’s fine. ---
**Author:** ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)\ **Post date:** [2018年十月14日 17:29 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/16 "2018-10-14T17:29:00Z")
I think that instead of “hoping” it’s OK, it would be nice to know that it _is_ OK. Does anyone know if there’s a way to get an official approval, or is this a “we’ll let you know if there’s a problem” only thing? ---
**Author:** ![dobbo](https://avatars.discourse-cdn.com/v4/letter/d/f08c70/32.png) [@dobbo](https://meta.discourse.org/u/dobbo)\ **Post date:** [2018年十月14日 20:13 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/17 "2018-10-14T20:13:02Z")
Google approved us thanks to @tshenry ‘s component, so anyone in a fix should deploy that! Thanks so much @tshenry for sorting that out you are a legend ---
**Author:** ![MiG](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mig/32/119486_2.png) [@MiG](https://meta.discourse.org/u/MiG)\ **Post date:** [2018年十月14日 23:39 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/18 "2018-10-14T23:39:09Z")
I haven’t heard back from mine yet. Will post an update when I do. Update: They approved it. Thanks @tshenry ! But I have another Discourse install that’s been running for a few years with Google login and it’s never been an issue. Perhaps this is only for new installs? They would have reviewed my older forum years ago, but my latest one is brand new from a couple of weeks ago. ---
**Author:** ![nickray](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nickray/32/114171_2.png) [@nickray](https://meta.discourse.org/u/nickray)\ **Post date:** [2018年十月16日 00:24 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/20 "2018-10-16T00:24:18Z")
Trying to set this up, Google is requiring a “review”. The review then complains that the sign-in button is “not compliant with the Google sign-in branding guidelines. Please update the Google sign-in button on your website according to [Google sign-in branding guidelines](https://developers.google.com/identity/branding-guidelines#top_of_page).” In typical Google manner, they don’t explain what exactly the issue is - I think it’s the “wrong” Google logo. Is this known? Easily fixed? ---
**Author:** ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)\ **Post date:** [2018年十月16日 00:31 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/21 "2018-10-16T00:31:41Z")
> [@Configure Google login for Discourse](https://meta.discourse.org/t/configure-google-login-for-discourse/15858/147): > > Trying to set this up, Google is requiring a “review”. The review then complains that the sign-in button is “not compliant with the Google sign-in branding guidelines. > [@Configure Google login for Discourse](https://meta.discourse.org/t/configure-google-login-for-discourse/15858/147): > > Is this known? Easily fixed? Thanks for the report! Yes we have received a few reports about this over the last week. See: [Not compliant with google signin branding requirements](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177). A quick fix would be to install the [Compliant Google Login Button](https://meta.discourse.org/t/compliant-google-login-button/99276) theme component. Based on the frequency of reports about this, it looks like we’ll have to come up with a permanent fix that doesn’t rely on a theme component. ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [2018年十月25日 00:08 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/23 "2018-10-25T00:08:46Z")
Yes, I have escalated this internally so we’ll get it fixed in this release. ---
**Author:** ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)\ **Post date:** [2018年十月25日 08:17 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/24 "2018-10-25T08:17:37Z")
@awesomerobot fixed it yesterday. [https://github.com/discourse/discourse/commit/1d7720ef9976a24653762160f4feac99bc85e6b7](https://github.com/discourse/discourse/commit/1d7720ef9976a24653762160f4feac99bc85e6b7) ---
**Author:** ![newoscar](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/newoscar/32/255274_2.png) [@newoscar](https://meta.discourse.org/u/newoscar)\ **Post date:** [2022年四月1日 12:33 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/25 "2022-04-01T12:33:49Z")
此问题似乎仍然存在。 我在申请 Google 的 OAuth 服务时收到了与 @dobbo 相同的电子邮件。 当前不可接受的版本： ![login-panel-remote-sensei](https://global.discourse-cdn.com/meta/original/3X/b/9/b97c1e4bed294434ea49d458facb7554a1feed45.png) Google 的期望： > **[Sign in with Google Branding Guidelines  |  Google Identity...](https://developers.google.com/identity/branding-guidelines)** 此组件已不存在：[符合规定的 Google 登录按钮](https://meta.discourse.org/t/compliant-google-login-button/99276) 我们能尽快修复此错误吗？ ---
**Author:** ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)\ **Post date:** [2022年四月1日 17:30 UTC](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177/27 "2022-04-01T17:30:53Z")
他们给了你更具体的信息吗？问题似乎是我们写的是“with Google”，而不是“Sign in with Google”？我们可以为所有 Discourse 站点更新这些，但在此期间，你也可以在管理员设置中立即添加文本： 1. 前往 admin \> customize \> text 2. 搜索 `js.login.google_oauth2.title` 3. 将文本更新为“Sign in with Google” 由于该文本较长，你还想添加一些自定义 CSS 来调整间距……（在 admin \> customize \> themes 下） ```css .login-modal #login-buttons:not(.hidden), .create-account #login-buttons:not(.hidden) { min-width: 180px; } ``` [下一頁](https://meta.discourse.org/t/not-compliant-with-google-signin-branding-requirements/99177.md?page=2)