https://supertokens.com/ logo
Join Discord
Powered by
Hello, is there a way to enter a number without a ...
# support-questions-legacy
a
Hello, is there a way to enter a number without a country code and avoid getting this error? Assuming I can define that the default country is US
n
Hi @adigutner
Are you using the pre built UI?
a
Yes
r
You can define the default country in the config
n
When you initialise the recipe you can do something like this
Copy code
ThirdPartyPasswordless.init({
    signInUpFeature: {
        defaultCountry: "..."
    },
})
a
Actually I see it's already defined
Is there a way to avoid getting this error?
r
If the frontend has the default country code, then the user sjouke not face this error
a
Default country is defined but still getting this error
r
Hmmm. Well, is the phone number actually valid?
Like try your phone number
a
I do not have a US phone number But this happens with any valid phone number I took this number from here https://fakenumber.org/
r
I think those might not be actual numbers.
Or might be blacklisted
a
If I press continue again I can continue to the next screen
I want to skip this step
It happens with any US number
r
If you press continue once, it shows the error, and pressing it again works?
a
Yes after the country code selection appears if I press continue again it works
r
Hmm. Can you open an issue about this on our GitHub? We will have a look
a
Sure Any other details you need?
r
Yea. As much as you can. Enough for us to replicate it 🙂
a
r
Thank you! We will see it asap.
If you only want phone as an input, consider just putting the contact method as phone. And not email and phone
a
I want both phone and email
r
I see. Understood
I know what the issue is. We will fix it on Monday / Tuesday.
a
Awesome thank you
a
@adigutner , seems like this is still an issue for you?
a
After updating to the latest SDK version I'm getting this error:
Copy code
JSX element type 'ThirdPartyPasswordlessAuth' does not have any construct or call signatures.
r
@porcellus can you help here?
p
hi
the 
ThirdPartyPasswordlessAuth
has been removed for some time
you should use 
SessionAuth
instead
r
Also, @adigutner please checkout the Changelog in the auth-react repo for steps on migration of code.
Since it seems that you were using a much older version and there have been a few breaking changes since then
a
Ok thanks Seems like the issue is fixed Thank you for handling it quickly
2 Views
PreviousNext
Powered by