I'm trying your restkit fork because I think sync ability is a really valuable feature. Also I would know if you think this version is ready for production environment.
Although, I see two errors in my tests:
If I create a record on ios database, restkit calls the server in order to create the same record on the other side. Perfect! But if I close the application (kill), when the app will be launched again, restkit tries to call again in order to create the record. The result is that record is created twice. If I close and open again, it continues to create record every time I open app.
If I delete a record on ios database, restkit doesn't call the server until the next post call (just create another record). A test case for this could be:
create a record (restkit call server, all is fine)
delete this record (restkit doesn't call the server, so ios and server are not synced)
create another record (restkit post to the server in order to create record and delete the old one).
But for some reasons the old entity appears again in the ios db. So the server is up to date with the latest changes but ios db has not good data.
Let me know if I didn't understand something or if I found a bug.
I'm trying your restkit fork because I think sync ability is a really valuable feature. Also I would know if you think this version is ready for production environment.
Although, I see two errors in my tests:
Let me know if I didn't understand something or if I found a bug.