-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Bug Report: Appwrite console bug #5975
Comments
The issue with not being able to update the value of any attribute in a document was fixed in appwrite/console#495 As for the collection/document not loading properly, it could be that the cloud database was undergoing routine backups when you were trying to perform operations. Could you try to do this again and see if the issue still exists? |
Another thing to mention is that version |
Hi @Srinivasan-Akash , checking in to see if this still exists for you? |
Do you still have a problem? If so, please provide exact reproducible steps as what's provided isn't detailed enough for us to reproduce the problem. Please be advised we'll have to close this soon due to inactivity. |
👟 Reproduction steps
When we create a database, collection and have some documents.
& we change some attributes and open any document to add an attribute value it does not even load that document or some times loads but we cannot update the new value.
12.08.2023_16.13.34_REC.mp4
👍 Expected behavior
Expected behaviour is to not produce the above bug and let user add value to the attribute
👎 Actual Behavior
It does not even load the document sometimes and if loaded we are not able to update the attribute.
🎲 Appwrite version
Appwrite Cloud
💻 Operating system
Windows
🧱 Your Environment
I am using the web SDK with next.js and below are the libraries
"dependencies": {
"@next/font": "13.4.13",
"appwrite": "^11.0.0",
"eslint": "8.46.0",
"eslint-config-next": "13.4.13",
"next": "13.4.13",
"react": "18.2.0",
"react-dom": "18.2.0",
"react-icons": "^4.10.1",
"react-toastify": "^9.1.3",
"uuid": "^9.0.0"
}
👀 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: