Exception: Set JArray values with invalid key value: "version". Int32 array index expected

[kmostofi]

Hi,
After a long time, I picked up the project to upgrade it from XamarinForms to .net Maui.
I get the above exception when it tries to push and pull sync. I compared the data in the database and the data that passed through in Json for Version column.

In the database, version = 0x000000000002D335 (byte[]) and in Json version = 'AAAAAAAC0zU=' (string).

EntityTableData has a Version byte[] property and DatasyncClientData has a version string property. This is the place that exception throws.

This is the model in the client project:
public class PrintFormat : DatasyncClientData, IEquatable
{
public string PrintFormatName { get; set; }

public bool Equals(PrintFormat other)
    => other != null && other.Id == Id;

}

and this is the model in the serverside:
public class PrintFormat : EntityTableData
{
public string? PrintFormatName { get; set; }
}

What I do wrong or missing to do?
Thanks,
Kamal

[adrianhall]

The version on the database is a byte array so that it takes advantage of concurrency checks available in entity framework core.

The version in the client is an opaque string (actually, it's a base-64 encoded version of the byte array) because you transmit a byte array most efficiently when converting it to a string, but there is little reason to convert it back to a byte array on the client.

Can't say when you are doing wrong specifically as you've provided no details of the exception.

[kmostofi]

I agree with you. This is the exception:

System.ArgumentException: Set JArray values with invalid key value: "version". Int32 array index expected. at Newtonsoft.Json.Linq.JArray.set_Item(Object key, JToken value) at Microsoft.Datasync.Client.Table.RemoteTable.GetJTokenFromResponse(ServiceResponse response) at Microsoft.Datasync.Client.Table.RemoteTable.SendRequestAsync(ServiceRequest request, CancellationToken cancellationToken) at Microsoft.Datasync.Client.Table.RemoteTable.GetNextPageAsync(String query, String requestUri, CancellationToken cancellationToken) at Microsoft.Datasync.Client.Table.FuncAsyncPageable1.AsPages(String requestUri)+MoveNext()
at Microsoft.Datasync.Client.Table.FuncAsyncPageable1.AsPages(String requestUri)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult() at Microsoft.Datasync.Client.Table.AsyncPageable1.GetAsyncEnumerator(CancellationToken token)+MoveNext()
at Microsoft.Datasync.Client.Table.AsyncPageable1.GetAsyncEnumerator(CancellationToken token)+MoveNext() at Microsoft.Datasync.Client.Table.AsyncPageable1.GetAsyncEnumerator(CancellationToken token)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()
at Microsoft.Datasync.Client.Offline.SyncContext.PullItemsAsync(String tableName, String query, PullOptions options, CancellationToken cancellationToken)
at Microsoft.Datasync.Client.Offline.SyncContext.PullItemsAsync(String tableName, String query, PullOptions options, CancellationToken cancellationToken)
at Microsoft.Datasync.Client.Offline.SyncContext.PullItemsAsync(String tableName, String query, PullOptions options, CancellationToken cancellationToken)
at TingleDbSource.Db.DbSyncAsync.SyncLoginAsync() in /Users/KM/Projects/TingleApi2/TingleBackEnd/TingleDbSource/Db/DbSyncAsync.cs:line 129`

At line 129 , the code tries to do a pullasync.

I tried a different library to understand what was going on. Dotmim.async also throw a similar exception when I use it as a Backend. However, I tested it with a direct connection to the database using Dotmim. async library and was able to get sync.

I looked at the data and noticed the data that comes through, the Version column is null, which seems Serialisation/Deserialsation has some issues with this. This is just an assumption.

[adrianhall]

I agree on the serialization / deserialization. What have you done with respects to Newtonsoft.JSON setup? Have you globally adjusted the serialization or deserialization settings? What does the response look like (JSON wise) in transit? How is your database set up? (Normally, for EF Core, we rely on the server doing the setting of the version as a concurrency token - if your database is not doing that, sync won't work).

I'm not familiar with how Dotmim.async works, so can't comment there.

[kmostofi]

I haven't done anything with Newtonsoft.JSON setup. Is it required?
No, I haven't adjusted the serialization or deseralization settgins.

The database is an azure SQL database and relational.

[adrianhall]

It looks like the version field in the database is null for some reason; that propagation through the system is causing the JSON deserializer on the client to fail, resulting in the error.

Take a look at what is coming across the wire to see if the JSON is well formed. You should see every single version field being a base-64 encoded string. If any of them aren't, that will be what is likely causing your issue. You can then look at the ID of that specific entity and go check what is in the database.