When fetch requests are defined and we get a mapping operation error on a matching URL deleteLocalObjectsMissingFromMappingResult treats all managed objects matching the URL as orphaned.
As a result we lose all objects that match the request URL:
and, as far as we can see
This is handled correctly only if the operation was canceled thanks to this line in RKManagedObjectRequestOperation.m
if ([weakSelf isCancelled]) return completionBlock(mappingResult, responseMappingError);
For the time being we are using this workaround
if (responseMappingError) return completionBlock(mappingResult, responseMappingError);
Hey @saniul, a failing unit test would really help us track down the problem. Thanks.
Add unit test for github issue #1695
Fix issue #1695 with deletion of managed objects if a response mapper…
… error is encountered
Fix issue with deletion of managed objects if a response mapper error…
… is encountered. closes #1695