You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
🐛 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 theemail
field in theconsume
endpoint.I exported a CSV of my users to confirm it, and it it's true, is stored in the email field.
Useful informations
The text was updated successfully, but these errors were encountered: