Auth: Update email account will not update the adress to log in

[Etheonor]

If you update the email adress with supabase.auth.update, it will not replace the old one but create a "new_email" element in your auth.user object.

Therefore, when you try to log in again with the new updated email, it will not work and you'll have to use the old one.

[kiwicopple]

Thanks for the bug report @Etheonor. I'm going to move this over to the GoTrue repo so we can discuss the expected behaviour.

Possibly related, since this PR occured after our fork was created: netlify/gotrue#243

[kiwicopple]

OK I did some testing here and can confirm: supabase/auth-js#57

We need to decide whether to handle this in the client or the server.

We could handle it in the client like this: supabase/auth-js#58. I'm not sure why Netlify chose this strategy to start with

[Etheonor]

Another thing, when we update this new_email element, if you do a supabase.auth.user() right after, you will not have the updated user. You have to logout/login to have the new_mail properly updated.

This is far from ideal

Edit: after further investigation

If you do a auth.refreshSession() and log the result, you'll have the updated user/session. But it seems that the info is not transfered to the context.
Even if I use the onAuthStateChange method, when I perform an email update, this will trigger the User_Updated event, but the session will remain the same...

[icecream78]

@kiwicopple @awalias I've looked though code that implements user change. That code is responsible for email change too, but I am not sure that it has been worked ever. Logic that handles email change placed in handler that requires auth token and has PUT method, not GET. Plus, default variable MAILER_URLPATHS_EMAIL_CHANGE is / and GOTRUE doesn't have handler for that url at all=)
My preposition for fixing that problem is next. In verify handler add new one type - email_change and write corresponding logic for handling changed email.
Or it isn't necessary changes? What do you think about that?

[awalias]

related: #60

[kangmingtay]

Hey @Etheonor, i think this issue has been resolved already. You can update your email with supabase.auth.updateUser which will return a user object with the new_email field. You'll have to verify the email change confirmation link that's sent to your email before you can login with the new_email.

[alexcsloan]

I'm having this exact same issue. I call supabase.auth.updateUser with the new email. I then verify the new email address successfully. I have confirmed that the user now has new_email set and email_change_confirm_status is set to 1. This makes it seem like the new email should be set up properly. However, I am unable to login with the new email address.