Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7623999
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 31, 20262026-05-31T04:50:54+00:00 2026-05-31T04:50:54+00:00

I have what appears to be a bug with Core Data in OS X

  • 0

I have what appears to be a bug with Core Data in OS X 10.7.1.

My data store (NSSQLiteStoreType) is not being automatically migrated correctly.

As a side note the exact same Core Data models are used by an iOS version of the app.

-> Here is what appears to be happening.

Up until the latest release everything has been working fine —

I have 14 revisions of the model — model 13 has been shipping for quite some time without incident.

Recently I updated my app and added a new model so I am at 14 (this is the version now used in the shipping apps).

The iOS version works just fine when migrating from model 13 to 14 — so no need to worry about that.

So rather then talking about OS X versions lets use NSPersistenceFrameworkVersions

NSPersistenceFrameworkVersions 251 being 10.6.8 and NSPersistenceFrameworkVersions 358 being 10.7.1

If we use like versions — meaning model 13 version 251 and migrate to model 14 version 251 it works fine.

same is true if we use model 13 version 358 and migrate to model 14 version 358 it also works fine

Here is where it gets interesting

if we migrate model 13 version 358 to model 14 version 251 it still works fine

However migrating from model 13 version 251 to model 14 version 358 does not work

CoreData: error: (1) I/O error for database at blah. SQLite error code:1, ‘no such column: FOK_REFLEXIVE’

Again this only happens when going from 10.6.8 (NSPersistenceFrameworkVersions 251) to 10.7.1 (NSPersistenceFrameworkVersions 358) all other permutations work just fine.

Here are the options used for migration that get passed to addPersistentStoreWithType.

// Allow inferred migration from the original version of the application.
NSDictionary *options = [NSDictionary dictionaryWithObjectsAndKeys:
                         [NSNumber numberWithBool:YES], NSMigratePersistentStoresAutomaticallyOption,
                         [NSNumber numberWithBool:YES], NSInferMappingModelAutomaticallyOption, nil];

One final thing, it appears if we only add attributes to model 14 the conversion will not break. It is only with the addition of an entity that will cause it to break.

Anybody else seeing this sort of problem. -thanks in advance.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-31T04:50:55+00:00Added an answer on May 31, 2026 at 4:50 am

    This bug appears to have been fixed in iOS 5.1 and OSX 10.7.3

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have found what appears to be a strange bug with sqlite. I have
We have this bug that only appears 30% of the time for the Release
In building my responsive website I have come across a bug that appears only
I have a Core Data model in which a Task entity includes an optional
I have run into an interesting bug where it appears that when you select
I have a strange bug that appears to happen only when the program isn't
I have discovered what appears to be a bug using MVC 3 with the
I have a bug on my site which only appears in MSN Explorer. The
I have what appears to be a corrupt index? Here is what is happening.
Update : The problem appears to have been corrupt DLLs somewhere in my PHP

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.