Core data app & data loss
Core data app & data loss
- Subject: Core data app & data loss
- From: Kimo <email@hidden>
- Date: Wed, 5 Dec 2007 20:36:05 -0800
I have a strange problem with my Core Data app, and not sure what to
do about it. This Core Data app was written several years ago and has
been very stable under Tiger with no reported bugs. However, when
Leopard came out, about 10 people (less than 1% of the amount of
users) told me that after they upgraded to Leopard, they experienced
data loss with my app. I haven' t been able to pinpoint it down, but
it seems to occur after they perform some edits and then save (or Save
As) the file. Later they come back to the file only to find the file
completely empty (file size zero K). The app only saves file in XML
format (not binary or SQLite format).
This is obviously a very serious problem to these customers, and I
have no idea where to look for the problem. For all I know it's an OS
problem. Regardless, is there method I should exam? The app
overrides configurePersistentStoreCoordinatorForURL:ofType:error:
(which I realize has been deprecated in OS 10.5) so it can prepare
the metadata for the file. Or maybe something in
writeToURL:ofType:forSaveOperation:originalContentsURL:error:? Any
suggestions appreciated.
Thanks,
Kimo
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden