
In my Flutter app, I used the appwrite account.createRecovery method.
As I've earlier implemented same logic using firebase Auth, the recovery email is to be sent to user registered email address with the reset link that when tapped/opened will direct the user to a page provided by firebase and then when new password is set, it's then redirect the user back to my app.
Now, when I used the account createRecovery method, I supplied the user email and an empty string for the url.
Now email is sent to my user email inbox. I tried this more than twice.
Also, I want to ask, do you expect all appwrite user who use appwrite as BaaS to also create a website whose they use as the url in the createRecovery method and implement all the logics to fetch the codes from the url paths and then redirect the user back into the app after password change?
This is kinda urgent.
Thanks.

@Steven @D5

Please do not tag people as it can be disruptive

Oh! OK. Thanks for the info

I would appreciate your support

Yes, it's on you to handle the password recovery

Wow!

It's OK.

However, why is the recovery email not sent to the user account?

If the code is correct, i think it will be sent?

Also, if you don't want to handle it yourself, you can use: https://www.authui.site/

I checked this but can't find info on whether it handles password reset as that's what I want to settle.

I only saw the login and signup feature there
Recommended threads
- Console not loading and APIs returning 5...
We use Appwrite storage for static files The APIs either take a long time to load or respond or sometimes return 524 status code. Same with the web console for...
- 1.7.x Style issue in the migration page
I am not able to select what to migrate because of the styling... the checkboxes are not showing on any of the appwrite versions 1.7.x. I tried other browsers, ...
- Can't reach Frankfurt server
I have been developing an IoT device that senses an event, takes a picture and pushes the jpg to an appwrite project. I'm using a Sixfab Pico LTE board that cou...
