Red
I get this warning even though the key doesn't actually exist
If I use a different key it works fine, but I don't know why this key won't work
TL;DR
Developers are experiencing a warning for an attribute key that doesn't exist. Deleting and recreating the collection seems to solve the issue. It's possible that when the attribute was deleted, it wasn't completely removed. Using a different key works fine, but the reason for the specific key not working is unclear. Red
Deleting and recreating the collection fixes this, I'm guessing when the attributed was deleted it was actually deleted
Recommended threads
- Our Appwrite organization is suspended
Please give support regarding this , no app is working now , please solve my issue and give support , no one is replying in message section or email.
- How to Avoid Double Requests in function...
I'm currently using Appwrite's `functions.createExecution` in my project. I want to avoid double requests when multiple actions (like searching or pagination) a...
- Project in AppWrite Cloud doesn't allow ...
I have a collection where the data can't be opened. When I check the functions, there are three instances of a function still running that can't be deleted. The...