On sign-up, I send users an email confirmation link → Take them to a view where they need to wait until they have confirmed their email.
When the current user’s email confirmed is yes → redirects them to the ‘Home’ tab.
My issue is this:
Even after opening the confirmation email link, the user is not redirected to the ‘Home’ tab, and I don’t think the user’s email confirmed is set to yes either, as I can’t see the ‘emailConfirmed field’ in ‘App data.’
From what I read in the Bubble doc, email confirmed should be set to yes automatically when email confirmation link is opened. Even if that is not the case, I can’t find a way to set emailConfirmed manually (I’m guessing it’s not possible).
Hey @luqmankm12! Bubble does set the email confirmed field automatically when the user clicks the confirmation link, but it can be a bit confusing to see in the database. A few things to check:
- Make sure you’re looking at the right user in the App Data tab, sometimes the search doesn’t return the correct record.
- Redirect timing: After clicking the link, the user is usually logged in automatically, but you might need to refresh the page or check
Current User's email confirmed in a workflow before sending them to Home.
- Quick test: Add a temporary text element showing
Current User's email confirmed so you can see when it updates in real time.
- Manual update isn’t possible, Bubble handles this internally for security, so you can’t set it yourself.
Most of the time, this is just a timing or workflow issue. A simple page refresh or a conditional redirect based on Current User's email confirmed usually fixes it. Hope this helps.
Tried adding Current User's email confirmed and Current User’s first_name on the web page to see if it was actually identifying the user.
As you can see, it No for Current User's email confirmed but no value at all Current User’s first_name.
I’m guessing this means Bubble isn’t identifying this token with any user. I don’t know why, though.
Ah, if Current User’s first_name is blank, Bubble doesn’t see anyone as logged in, which is why email confirmed is also No.
A few things you can check:
- Same browser/session: The confirmation link only works if you open it in the same browser/session where you signed up. If you open it in a different browser or incognito, Bubble won’t know who the current user is.
- Redirect URL: Make sure the link in the email points to a page in your app, so Bubble can log the user in automatically after clicking.
- Testing: Try signing up and confirming in the same session, you should see
Current User’s first_name populate.
Basically, Bubble can only match the token to a user if it knows which session it belongs to. If it can’t, the Current User fields stay empty.
Same browser/session: The confirmation link only works if you open it in the same browser/session where you signed up. If you open it in a different browser or incognito, Bubble won’t know who the current user is.
I think you missed the part that the user is signing up from mobile. This is for a mobile app. The user clicks sign up from the mobile app and is sent a confirmation email. It’s not going to be the same browser because there is no browser page other than the email confirmation page.
Does Bubble not support email confirmation for mobile native?
Thanks, appreciate the help.
