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.Deleting and recreating the collection fixes this, I'm guessing when the attributed was deleted it was actually deleted
Recommended threads
- API key without database.read/write
I had some issues with my previous API key and I deleted it then I wanted to create a new one and discovered the database checkbook has no database.read/write j...
- dynamic key missing scopes for database ...
Here are the scopes listed, I get permission errors for reading row and document. Appears to be missing since last time i checked. Database 6 Scopes policies....
- Upgrading selfhost version?
It is okay to upgrade version to higher one, of my current version is 1.7.4 to 1.8.1. Is that safe to do cause my clients already have data on that? Also is a...