-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client stops syncing when server side rejects a change. #293
Comments
@danieljimenez , can you clarify? Sync broken for all objects, or just that specific object? If server cannot accept a change because it violates the schema set, then it wouldn't make sense to sync it. |
I believe it's just for that bucket, however the only thing we've been able to do to restore syncing in the app is delete / reinstall. Even removing the offending object will not resume sync. |
We've also been seeing issues with a bucket staying in sync if the client library receives an HTTP 500 from the server. |
In our testing, it seems like if the Simperium server rejects a change, the iOS client will no longer sync. We ran into this while applying a schema to our buckets. If the app attempts to send data that does not validate, it will no longer sync.
The text was updated successfully, but these errors were encountered: