I have been seeing multiple implementations of auth across tools like Clerk, Supabase and it seemed like they are using async storage or secure storage as some form of storage mechanism to store some jwt token or something (not super fluent with auth stuff).
I see a function call named account.createSession in Appwrite docs. Is this function responsible to storing some token as well locally on device?
Asking since I want to be super sure the auth works well and is handled well by Appwrite itself and there's left for me to be done beyond what Appwrite functions handle. Thanks!
Recommended threads
- Custom domain for Google Auth
Hello! I connected my custom domain to my Appwrite project, but I can't get the Google login/consent screen to show my domain instead of the Appwrite domain. I...
- [SOLVED] Production down - createExecuti...
Hey, Since 1.9.6 rollout in fra (~17:00 UTC, 14 Aug), POST /v1/functions/{functionId}/executions returns a 400 whenever the body includes an empty headers ob...
- Get Profile picture
If I made an app where user need to sign in with Google. Now how do I access the user profile picture?