The name, creator, logo, etc part doesn't looks correct
Nevermind, the variable is correct
Oh, wait, what's it. Could you please send it?
Or an example?
.
name contains just name?
It should be like a JSON. Something like this:
{
"name": "D5"
}
name is a string and is getting parsed correctly, my issue lies with a specific collection which throws error mentioned before
Something I tried is I created a new user and this allowed me to upload/save a document(sound) but the secodn time its throws an error
is the ID caching in the backend or someting
In the log doesn't looks correct
Looks like this:
{
name: "D5"
}
Not sure if it's due to browser interpretation or similar 😅
Are you using Appwrite cloud or self-hosting?
should be that cause in DB it is correct
cloud
It's not in DB but in your variable
What's the part of the code where you set the variable?
what variable?
This issue got my head scratching, but finally I realised what was wrong, the error message was right but it should've been more verbose My Sounds collection has one to one relation with user, this caused the error to occur, idk how this didn't happen before when I was testing . Anyways thanks. Hwo can I close this thread
I'm closing it. Makes sense, didn't have thought about the relationship 😅
[SOLVED] ID.unique() doesn't work
Thanks for the feedback. I will relay this to the team. We can try and have a better error message in this case 👍
Do you mind sharing the structures of the collections in question? The songs and users collection and how they are related?
Thanks
@Diversified
Recommended threads
- change role of a team member in Appwrite
It's not possible to add/change roles of a team meber in Appwrite Frontend. When you click on a member of a team you get forwarded to the configuration page of ...
- Session not found. Please run appwrite l...
I have encounter an issue with appwrite CLI They asking for a login session but in the doc, it’s mention that only setup client with endpoint / api key is enou...
- ACTIVATE DEPLOYMENT PROBLEM...
It's not giving me the option to activate a deployment that says it's ready..