How come the input.email is undefined when I'm sig...
# support-questions
c
How come the input.email is undefined when I'm signing in with an email?
this is the input arg for the
sendEmail
function
r
huh.. thats weird
c
yeah 😄
I'll try going into the login flow again
and yeah a passwordless user with this email exists
r
yea.. if it's still undefined, it may be a bug. You could open an issue about this
c
yeah will do!
r
thanks
c
Now it's defined. Probably a session timeout? I had left it at the code screen for some time while having a snack, then logged the input during the "resend email" request
I'll make sure to check for the email being undefined
r
hmm. That's really strange. It should not happen
c
yeah
r
so if you resend the code now, the email is defined?
c
I went into the login flow from the beginning
oh yeah, resending does not work
the email is only defined for the first email sending try
r
oh damn.. ok im seeing what's wrong
c
great 😄
r
found the bug! thanks.. Will release a new version tomorrow
for now, you can continue using the older way of sending the email - it should make no difference in terms of functionality.
c
eh, already committed 😄 it's fine, I'll just update
this is not live yet
r
it'll be released in a breaking change
so you will also have to update the frontend SDKs.
c
okay, that's fine
r
but well.. should not be too much effort either way
c
cool! thanks
the Twilio integration works perfectly! 👌
r
awesome :))
@CaptainPhoton this has been fixed in v10.0.0
you can upgrade to it now
c
Great, thanks!
r
i'll also release a patch fix for this for the previous non breaking change version sometime today
c
Okay, I’ll try to keep it updated to the latest version as far as I can
r
fair enough
c
@rp so, the breaking changes in v10 is about the "status" field of responses? No other changes needed?
r
yea pretty much.
c
ok cool!
2 Views