We are adding phone number sign in only to our app, we have noticed some formatting differences between what is stored in supertokens verse what gets passed in by

createCodePOST

override function. We can see in the dashboard a phone number saved as +640223334444 on a user. Which is set by

updateUser

. The issue is when we post a phone number to

/auth/signinup/code

(+640223334444) the phone number provided from the createCodePOST argument input is +64223334444 (missing the zero after the country code). We are using this input phone number to search to see if any users have the phone number attached to their user, if so let them sign in, else require them to sign up via email. Because the input has the 0 stripped off, the listUsersByAccountInfo is retuning no users. Is the stripping of the 0 in the createCodePOST intentionally or a bug? If intentional, how come the

updateUser

doesn't format the phoneNumber the same? Thanks

hey @__jono thanks for reporting this. It's indeed a bug. We will fix it right away.

Hi @__jono ! We've created a [GitHub issue](https://github.com/supertokens/supertokens-core/issues/880) for this and are addressing it as a priority. Feel free to follow the issue for updates.

Great. Thank you

Hey @__jono , we have released a fix for this in core version 7.0.12. If you are using self hosted, please update to that (docker tag is still

7.0

- you have to repull the latest image). If using our managed service, and the core is on version 7, then we will auto update for you.