v0 contents for change resolver

[crspybits]

Dany is getting errors on the UI in Neebla. When he sent me logs, I saw lots of the following:

2021-03-27 14:30:47.434 [Error] [main] [SyncServer+DelegateHelpers.swift:80] reportUploadError(fileUUID:trackerId:error:) > couldNotGetHTTPURLResponse

And when I got him to repro the issue and I looked at the server logs, I saw:

[2021-03-28T01:34:30.410Z] [ERROR] [FileController+UploadFile.swift:52 finish(_:params:)] v0 contents for change resolver (CommentFile) were not valid: Optional("{\"senderId\":\"3\",\"sendDate\":\"2021-03-27T18:31:08Z\",\"id\":\"57856333-6D46-40CF-82BF-B71C6121F567\",\"sende")
[2021-03-28T01:34:30.411Z] [ERROR] [RequestHandler.swift:74 failWithError(failureResult:)] v0 contents for change resolver (CommentFile) were not valid: Optional("{\"senderId\":\"3\",\"sendDate\":\"2021-03-27T18:31:08Z\",\"id\":\"57856333-6D46-40CF-82BF-B71C6121F567\",\"sende")
[2021-03-28T01:34:30.412Z] [INFO] [RequestHandler.swift:145 endWith(clientResponse:)] REQUEST /UploadFile: ABOUT TO END ...
[2021-03-28T01:34:30.413Z] [INFO] [RequestHandler.swift:149 endWith(clientResponse:)] REQUEST /UploadFile: STATUS CODE: internalServerError

[crspybits]

I think this is related to the iOSBasics issue:

Version 0.13.3 (3/15/21)

• Fix issue where additional uploads for a file group could start even when the file group is currently uploading.

[crspybits]

On that v0.13.3 iOSBasics issue, is that dealing with a condition where (a) an initial upload somehow fails, and (b) does't inhibit a subsequent upload of a mutation change to that prior upload occurs. I think there's a logical error in uploads in iOSBasics-- I suspect v0 uploads aren't being prioritized.

[crspybits]

v0.18.0 of iOSBasics has a fix for this issue.