Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

phoneNumber is stored into email field in PasswordLess strategy (python SDK only) #416

Closed
flaancs opened this issue Apr 6, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@flaancs
Copy link

flaancs commented Apr 6, 2022

🐛 Bug Report

I'm using the PasswordLess strategy with only OTP and phoneNumber.

When I completed the flow, I saw that the phoneNumber is stored in the email field in the consume endpoint.

I exported a CSV of my users to confirm it, and it it's true, is stored in the email field.

Useful informations

@rishabhpoddar
Copy link
Contributor

rishabhpoddar commented Apr 7, 2022

This has been fixed in python SDK version >= 0.6.2 which has now been released.

To fix existing user's email / phone mismatch, you could loop through all users, then fetch their info, associate their email (which is actually their phone number) with the phone number field (using the update_user function), and finally delete their associated email by calling this API and passing the email input as a JSON null.

@rishabhpoddar rishabhpoddar changed the title phoneNumber is stored into email field in PasswordLess strategy phoneNumber is stored into email field in PasswordLess strategy (python SDK only) Apr 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants