Hi team, I think you should check the Android SDK implementation once, as it seems to have an issue handling Kotlin null values.
For example:
When I send:
backgroundType=SOLID_COLOR, solidColorIndex=3
Appwrite correctly stores and returns:
backgroundType=SOLID_COLOR, solidColorIndex=3
So this works fine.
But when I update the same value to null and send:
backgroundType=SOLID_COLOR, solidColorIndex=null
Appwrite still returns:
backgroundType=SOLID_COLOR, solidColorIndex=3
So it looks like the SDK is not properly handling Kotlin null when updating an existing value.
Interestingly, if I send the string "null" instead of the actual null value, it updates correctly.
Could you please check how the Android SDK handles null values during updates?
Mainly I am doing this with upsert function. But I believe update function will also behave the same.
Yaa one more thing to tell you.. That "null" don't work for integers because in that I get error invalid structure.
For integers I haven't found any solution how to update it to null.
But "null" correctly updates to null for string values and relationship, but null don't work for both string and relationship.
<@743532656767270934> might be simple bug, wanna run an agent on this? π
yes will take a look when back, had some other updates for kotlin sdk
Recommended threads
- Can't connect GitHub β 500 error at the ...
Appwrite Cloud, Pro plan, SFO region. All my Git connections vanished today β Sites and all 15 Functions now show no repository connected. When I try to add a ...
- vorafy.studio domain already exists erro...
My domain vorafy.studio is stuck/locked from a previously deleted project. I created a new project but can't add the domain β getting 'already exists' error. Pl...
- GB Hours IS NOT resetting
Hi, I was checking my usage and noticed that all of my usage quotas were reset on August 20, 2026, when my billing cycle renewed. Everything else appears to ha...