-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃悰 Bug Report: Appwrite Rest endpoint expects 'passwordAgain' param when calling account.updateRecovery #92
Comments
@clnmcgrw Faced same issue, looks like there is a mismatch between actual implementation and the latest package code. Had to downgrade the version to 13 for the time being where the |
In case anyone else runs into this or a similar api/sdk mismatch - you can always just use the
|
@clnmcgrw, you were probably using an SDK meant for Appwrite version 1.5 while Appwrite Cloud was on version 1.4. It's important to make sure you use a version of the SDK that is compatible with Appwrite. The readme will mention. For example: Version 15.0.0 of the web SDK: Line 9 in eab8856
Version 13.0.2 of the web SDK Line 9 in bf13f87
|
馃憻 Reproduction steps
Install appwrite web sdk, configure w/ v1 endpoint (https://cloud.appwrite.io/v1), and attempt to call
account.updateRecovery
. The method accepts 3 args (userId, secret, and password), but the endpoint is expecting a separate "passwordAgain" param.Also, docs still show that the method accepts a 4th "paswordAgain" arg, but in v14.0.0 of sdk it does not support that argument.
馃憤 Expected behavior
I'm able to use the
updateRecovery
method to confirm password reset by passing 3 arguments - userId, secret, and password.馃憥 Actual Behavior
I get an error saying that "passwordAgain" param is required, but
updateRecovery
method does not support it.馃幉 Appwrite version
Different version (specify in environment)
馃捇 Operating system
MacOS
馃П Your Environment
Local environment, node 20.5.1, appwrite 14.0.0 configured with v1 endpoint
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: