setupCoreDataStackWithAutoMigratingSqliteStoreNamed corrupt the database for iOS 5 #563

Closed
johnphan opened this Issue Sep 5, 2013 · 1 comment

2 participants

@johnphan

setupCoreDataStackWithAutoMigratingSqliteStoreNamed worked great in iOS 6 but when I tested on iOS 5 simulator, it somehow corrupted the database. The only different of the two models is a single NSString attribute. I turned on all the debug log but it's not showing any errors? Once the sqlite file is corrupted, the database became useless. So for now, I'm doing below; it's not what I want because all 5.0 users will lose their database every time they upgrade.

if (SYSTEM_VERSION_LESS_THAN(@"6.0")) {
[MagicalRecord setupCoreDataStackWithStoreNamed:@"Db.sqlite"];
} else {
[MagicalRecord setupCoreDataStackWithAutoMigratingSqliteStoreNamed:@"Db.sqlite"];
}

@tonyarnold

Given the age of this issue, and the volume of issues we have to work through, I've decided to close this alongside a number of other older issues.

If you can still replicate the issue under the latest in-development version of MagicalRecord (3.0 at the time of writing), please feel free to re-open and one of @magicalpanda/team-magicalrecord will take another look. Thanks!

@tonyarnold tonyarnold closed this Apr 8, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment