-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Sign in with Google temporarily disabled for this app" #19
Comments
Yeah, the issue here is that Google is very protective of Gmail access, and they want to review any apps before they have a chance to cause too much public damage. The middle-ground they've found is that you can have N people sign into your app before it's shut down for anyone except for you (the author of the Google app). The reason you can use the OneGraph app is that it's be reviewed as a developer tool, and doesn't ask for "write" (send, really) permissions, so the review is softer. We've seen some pretty intense requests for redesigns/more informative verbiage, and fewer permissions on some of the apps using Gmail. If you end up publishing a real GatsbyMail for others to use, you'd want to create an OAuth client in Google, add the client id/secret in the OneGraph app dashboard, and they have your app reviewed well before launching publicly. |
Thanks for weighing in @sgrove! Since this is more of less for demo purposes (see the "Don't use this for anything real" in the live app, ha) I'm going to close this out! If you're interested in using any of this for a real app @papascott definitely check out some of the advice above to move past some of these technical hurdles/challenges. |
I'm going to re-open this... been pinged a few times that it's not working, so it'd be nice to just fix it. |
Hi @DSchau, Will this issue resove if the developer created a new account in onegraph and used his/her appId in .env file ('GATSBY_OG_APP_ID')? |
@dnafication sorry for the delay--but yes that should work! |
Just to make peoples lives a bit easier I updated the readme to avoid this issue. In my case, I needed to create a onegraph account since my Google account requires permission which can only be accepted by a self-created account. |
Added a missing crucial step that makes setting up the project must easier. This commit references issue #19
Even for onegraph account it gave the same message, "Sign in with google is disabled". I also tried t connect oneGraph account with google, same message. |
As installed, Google won't let you authenticate to gatsby-mail. Unlike in the webinar, there is no link to get around the scary warning.
My workaround was to sign up for my own OneGraph account, create an app, and use that App Id for GATSBY_OG_APP_ID in .env.development. In the OneGraph App dashboard I added http://localhost:8000 to CORS Origins, and then I was able to use run and use gatsby-mail locally.
The text was updated successfully, but these errors were encountered: