Sign Up / In (with google + email) does not show up

After configurin Google auth (fine) and creating Sign Up / In with google + email, they does not show up when clicking Sign Up / In in the Header. The page just flicker and shows an empty space (between Header and Footer) of the same size of the missing Sign Up / In page.

Can some one help please?

Hi @lgs, can you please, check whether there is an update on the block or not? we previously had such issue but on new blocks it should be fixed. If it is updated, could you please, send a published page link?

Hi @Maria the pubblic link (it’s still a draft work in prog. really) is https://mei8927.softr.app/

Also, it looks now they shows up (both SIGN UP/IN) but google complains like the following:

`Access blocked: This app’s request is invalid xxxxxxxxxxxxxxx@gmail.com

You can’t sign in because this app sent an invalid request. You can try again later, or contact the developer about this issue. Learn more about this error
If you are a developer of this app, see error details.

Error 400: redirect_uri_mismatch`

1 Like

Ok. In that case may I please, ask you to check your redirect url and javascript origins url in Google Cloud, make sure that you add www in front

You mean https://www.mei8927.softr.app or really https://www.softr.app ?
(because at the moment I didn’t set my custom domain yet)

https://www.mei8927.softr.app

Done but same error. I also waited 5 min as suggested by google and re-deployed the site as well.

Current config looks like this:

One only doubt @Maria, the current “Publishing status” actually is “Testing” on google console. Does it need to be “published/promoted/pushed” to “production” to work correctly ?

See here:

Yes you need to definitely push to production

1 Like

Done but to make it working that was not enough. What I did was:

  1. adding both https://www.mei8927.softr.app and https://mei8927.softr.app to google Authorized JS and redirect URIs

  2. publish the app several times after small modifications (just to enabling re-publishing function)

  3. Only after more then half an hour of pushing & publishing the authentication magically start working

Not sure which of the previous try really enabled the app working, may be it’s just google setup propagation? I don’t know but now is working, thanks for your support @Maria

1 Like

Hi @lgs yes actually I didn’t mention that you need to always click on publish updates after making any changes and in case of Google it might take some time for Google sign in to get activated.(sometimes it happens instantly)
So to answer your question, all 3 steps helped