AFNetworking/AFIncrementalStore — pull request #120 by julienfantin (2012-12-03 16:47:33+00:00)
Title: Fix empty NSSaveChangesRequest in `AFIncrementalStoreContextDidSaveRemoteValues`

The original instance of NSSaveChangesRequest was passed to both
`AFIncrementalStoreContextWillSaveRemoteValues` and
`AFIncrementalStoreContextDidSaveRemoteValues`.

The probleme here was that CoreData removes the objects from the sets
referenced in the original request as they are saved. This means that
from a notification handler for
`AFIncrementalStoreContextDidSaveRemoteValues` you are provided with an
`NSSaveChangesRequest`instance whose sets are either empty or nil,
leaving you unable to get a reference on the managed objects.

This is fixed here by creating a new NSSaveChangesRequest with copies of
the original sets.

This works fine for my purpose, so far but could there be some unexpected side-effects?