Struggling with Google Sign up/log in - redirect

Need help
1

Hi everyone,

I’ve changed my signup/login method for users to sign up/in with Google (I’ve tried using different plugins).

It successfully creates the users (takes the space of my whitelist data type, where I manually input their email as a holding data value). The issue is after signup/login in via Google, my ‘go to page (profile)isn’t sending the user data. The page is set to data type (user), and my data to send it type (user). I’ve tried all variations of changing the pages data type, to changing the send data type to current users Google’s user etc etc..

The test account is redirected and no user is detected or sent through. Even in the URL it says bubble/XXXXXNO_USER

Here’s the current workflow

Capture
Capture760×575 22.8 KB

I’ve followed different Youtube tutorials and it works for everyone else. I just can’t get it to push current user to the profile?

Any help massively appreciated! thanks in advance.

2

That’s strange…

I ran a quick test here, basically following the same workflow as yours, and it worked.

After logging in with Google, when you return, it redirects to that profile page. When it goes there, does the URL include the user’s ID?

Like this:
https://yourapp.bubbleapps.io/version-test/profile/123456… (The user ID)

You can also break this down into a custom event. The actions after signing up/logging in with Google can go into a custom event, and then in step 2 of the workflow, you call that custom event. That makes it easier for you to control and test.

3

The issue is timing!! after a Google OAuth login, Bubble’s Current User isn’t always resolved immediately in the same workflow, so it sends empty.

Fix: don’t send data via the navigation step at all

On your profile page, just set the page’s data source to Current User directly (in the page’s data source field, not passed via navigation). Remove the “Data to send” from your “Go to page profile” step entirely.

This works because by the time the page loads, the user session is fully established and current user is available.

If your profile page must receive a user via URL parameter for other reasons, the workaround is:

  • Add a short pause before the navigate step (you already have one — try bumping it to 1000ms+)

  • Or use a “Navigate to page” with Get data from page URL and pass the user’s unique ID as a parameter instead

The loader steps (4–6) are also unnecessary if you go the Current User route — the redirect happens fast enough without them.

4

Its you app a mobile app? or web app?