Android SDK: Kotlin null Value Not Updating Correctly

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.

@Chirag Aggarwal might be simple bug, wanna run an agent on this? 👀

yes will take a look when back, had some other updates for kotlin sdk

https://github.com/appwrite/sdk-generator/pull/1844

How can I use this release in my code? As far I know you need to release a new version, or is there any other way also?

will be releasing soon - https://github.com/appwrite/sdk-for-kotlin/pull/84

https://klipy.com/gifs/mr-bean-mrbean

released

Did you changed the implementation? Earlier it was easy to pass data class, but now the argument takes Map<String,Any?>? which is not a data class..
Now we have to manually convert data class to Map.

As far I know the fix was simple by just proper initializing Gson to not filter out null values.
Why did you changed data argument from Any to Map?

yeah i completely agree a type change was not strictly needed. mapOf() already worked as Any.

the issue i wanted to fix is what serializeNulls() did to data classes. we had to send explicit nulls so you can clear a field. once we do that, every default-null property on a data class would also be sent as JSON null and get cleared.

lets take an example -

data class Background(
    val backgroundType: String,
    val title: String? = null,
    val solidColorIndex: Int? = null,
    val imageUrl: String? = null,
)

stored as

Background(
    backgroundType = "SOLID_COLOR",
    title = "hello",
    solidColorIndex = 3,
    imageUrl = "xyz",
)

you only want to change title to "hello world". this looks right, but it is not:

tablesDB.updateRow(
    databaseId = "db",
    tableId = "tbl",
    rowId = "row",
    data = Background(
        backgroundType = "SOLID_COLOR",
        title = "hello world",
    ),
)

solidColorIndex and imageUrl default to null, so they would be cleared too. to keep them you'd have to refetch and pass them back:

tablesDB.updateRow(
    databaseId = "db",
    tableId = "tbl",
    rowId = "row",
    data = Background(
        backgroundType = "SOLID_COLOR",
        title = "hello world",
        solidColorIndex = 3,
        imageUrl = "xyz",
    ),
)

locking data to Map<String, Any?> makes the partial-update path the only one that compiles:

tablesDB.updateRow(
    databaseId = "db",
    tableId = "tbl",
    rowId = "row",
    data = mapOf("title" to "hello world"),
)

no refetch. fields you omit stay as they are. null in the map is how you clear.

i understand its a bit of migration. you can keep the data class in app code and convert at the call:

fun Background.toMap(): Map<String, Any?> = mapOf(
    "backgroundType" to backgroundType,
    "title" to title,
    "solidColorIndex" to solidColorIndex,
    "imageUrl" to imageUrl,
)

tablesDB.updateRow(
    databaseId = "db",
    tableId = "tbl",
    rowId = "row",
    data = background.toMap(),
)

only use toMap() when the object already has current values for every field you want to keep. for a partial update, pass the map of just the change.

@Chirag Aggarwal ⚠️ Take a look at this asap

My app all old versions are now crashing with this error.

read-only error, seems like ur team is blocked?

Which team? I didn't implemented any team feature in my app

share ur projectid

Ok wait

692ef34900323ad33c39

@Chirag Aggarwal

doesnt seem like ur project is blocked. check which endpoint this error is coming from

My Appwrite endpoint is sgp.cloud

I think that's the singapore endpoint. I don't know.

My app isn't even opening.
It crashes as soon as I do any server operation. Get request or Upsert. Any server call lead to this error.

i meant the endpoint that was resulting in this specific error 👀

@Shivam seems like your team has missed invoices