Sometimes the sync client fails to apply a received changeset due to the violation of some invariant:

• Updating an object that doesn't exist
• Invalid prior size in list operations
• Unknown table/column referenced

The error message along with the stacktrace gets sent to the server when this happens.
To make it easier for us to understand/debug the root cause, adding more context to this error message would be helpful. A few ideas for things that might be helpful:

• Is the client doing a "sync" or "async" open?
• Is the client in the process of doing a reset/recovery?
• probably other stuff?