https://supertokens.com/ logo
Join Discord
Powered by
Hello <@292333473786494976> & <@435107855880683521...
# support-questions-legacy
n
Hello @nkshah2 & @porcellus , I don't know if you're already on it, but the algolia search doesn't work anymore in the supertokens docs
n
@jscyo Can check
Thanks for pointing it out!
j
Hey, looking into this
n
Thanks
btw guys you're doing an amazing work
n
Hey we're working on a fix, should start working in an hour or so
In the meantime were you looking for something?
n
No problem
I just wanted to know if I update the email of a user on the backend with the method updateEmailOrPassword, does supertokens automatically sent a verification email to this user or not ?
and if supertokens mark this new mail as unverified in its database
n
It will mark the email as unverified but it wont send an email automatically
You would have to trigger the email after updating the email yourself
n
Nice, thank you !
n
PS: This has been fixed
n
Is there any documentation on what happens internally after 
updateEmailOrPassword
is called? Like, is the password just accepted? No token, no nothing? The documentation is a bit sparse.
n
Hey @NickReese , So there is no documentation for it but I can help with questions if you have them. 
updateEmailOrPassword
does not require a token and yes it does accept the password, but that is only when you call the function directly. The normal flow would be to call the API to generate a token and send the reset password link to the user and then call the password reset API with the token. If you want to mimic the same behaviour by calling the functions directly instead of calling the APIs exposed by SuperTokens you should call: - 
createResetPasswordToken
which will generate ad return a token for the password reset - 
resetPasswordUsingToken
which can be used to reset the user's password with the generated token. This function will validate that the token is valid etc
updateEmailOrPassword
should be used for internal operations that reset the password and not for user facing operations
n
@nkshah2 Thank you for this. I hadn't realized that it was only in the server side package lol. I've been writing a cross platform wrapper using react native / web hitting a 
next
backend. Reimplementing has been interesting as I've never seen a codebase structured in the way this one is. While I have you, any way to drop support for async-storage in RN? Would love that it was pluggable to use mmkv (sync instead of async). So far so good. Got my package working well.
Happy to share my implementation with you / the team as there is a huge community looking for this over at https://github.com/t3-oss/create-t3-turbo and https://github.com/chen-rn/CUA as they try and escape the pricing of Clerk... Seems like a nobrainer business wise for Supertokens to offer an implementation given your pricing.
Also, your product is quite robust and I'm really digging that I can toss Supertokens into a schema 
auth
and it just works.
Biggest complain is char(36) over uuid on the tables.
Finally just realized I'm hijacking someone's welcome thread lol.
n
Haha yeah the #907932061669654548 or #757927552999227393 channels are best for this. As far as making storage pluggable in the react native SDK goes, its a good idea for sure and we'll add it to our roadmap for sure just cant speak for how soon it will get picked up. If you were interested in contributing to the SDK to make it plug and play we'd be happy to get it reviewed on priority and get it rolled out that way
2 Views
PreviousNext
Powered by