Google Sign-in fails for new users — “Could not find block with id”

Bug Reports
1

Hi Softr team & community,

I’m having an issue with Google Sign-in on my app: Log in

What happens:
• For existing users, Google Sign-in works fine.
• For new users (email not yet in the user table), trying to sign in with Google fails.
• Instead of routing them to the signup flow, I get:

Error 400: Something went wrong. Please try again or pass the following error message to the application owner:
Could not find block with id: f8e9c071-0e54-4fbd-9dce-d56a8802cec7

What I’ve checked so far:
• My Google OAuth Client ID/Secret are set in Softr.
• Authorized domains and redirect URIs in Google Cloud Console match my Softr domain (https://wispel.softr.app).
• Both Sign-in and Sign-up pages exist and are published.
• The issue only appears for first-time Google users, so it seems to be a flow/routing issue rather than a Google config problem.

What I suspect:
When a new Google user tries to sign in, Softr’s auth flow is attempting to send them to a signup block that no longer exists (or has a different block ID). I can’t find a setting in the UI to re-link the Sign-in and Sign-up pages.

Has anyone run into this before? How did you resolve it?
Thanks for any pointers!

2

FYI @Jjenglert

It doesn’t seem to be a common issue for most users. However, I think I’ve found the cause — and it also explains why most Softr users won’t run into the same problem.

It looks like Google authentication during sign-up fails if the user already has an account in one of my other Softr apps using the same Google account. In that case, the sign-up flow doesn’t seem to handle the existing Google identity properly, which leads to the “Could not find block with id…” error.

3

+1

4

Interesting. I haven’t heard of this yet. Thanks for checking back in and letting us know!