Wrong handling of Sync error codes

[cmelchior]

Kotlin has an asymmetric test that fails on the latest BAAS commit 3e370f9ee73c00efe2486ce5cd91d8fceb841cd6. I'm still looking into why, but the returned error is crashing Core:

We are getting this back from the server:

json_error 230 495 6
{"message":"Client attempted a write that is outside of permissions or query filters","isRecoveryModeDisabled":false,"tryAgain":false,"logURL":"http://localhost:9090/groups/6503237182ce974ccb7d7b84/apps/6503259382ce974ccb7d7b92/logs?co_id=6503f28e82ce974ccb7e8e98","shouldClientReset":false,"action":"Warning","rejectedClientVersion":11,"rejectedUpdates":[{"table":"AsymmetricA","pk":"CmUD8oZK+IlKoE2w5A==","reason":"write to \"6503f2864af8894aa04db0e4\" in table \"AsymmetricA\" not allowed"}]}.

This type of error is crashing Core here: https://github.com/realm/realm-core/blob/master/src/realm/sync/noinst/protocol_codec.hpp#L307

According to the Sync team, this compensatingWriteServerVersion field is apparently optional, so I'm not 100% sure how you want to handle this. See https://mongodb.slack.com/archives/G0121N9LJ14/p1694694357742649?thread_ts=1694682200.728329&cid=G0121N9LJ14

[sync-by-unito]

➤ michael-wb commented:

From Kiro in the Slack thread:

for illegal asymmetric writes, error code 230 will be returned with an attached rejectedClientVersion and rejectedUpdates , but no compensatingWriteServerVersion because it does not generate a compensating write. it just drops the asymmetric object; compensatingWriteServerVersion is only included with error code 231