0

I have a small utility app which populates a persistent store that I package with an iPhone app. I recently upgraded to OS X Maverick and now my app is behaving differently than it did before. When this line executes:

[self.managedObjectContext save:&error]

...I now get two new files: my objects.datastore-wal and objets.datastore-shm. The new objects I am adding seem to be stored here instead of the original objects.datastore file, because deleting them reverts my changes.

Why are my changes not persisted to the original DB? Am I missing a step here? Is there some call I need to make to the PersistentStoreCoordinator? This behavior is definitely different than I was seeing in Mountain Lion, when I always had just one file to work with.

Bryan
  • 8,748
  • 7
  • 41
  • 62
  • 1
    See also [Core Data and iOS 7: Different behavior of persistent store](http://stackoverflow.com/questions/18870387/core-data-and-ios-7-different-behavior-of-persistent-store). – Martin R Nov 01 '13 at 19:34
  • If I am not wrong, there were some changes to how the records are stored in the datastore file starting from iOS7 (saw it in the WWDC 2013 Core Data videos). Possibly the same thing? – Max Nov 01 '13 at 19:35
  • Thanks, I found link #2 there extremely helpful. – Bryan Nov 01 '13 at 20:08

0 Answers0