I'm still having some serious issues. I've tried all suggestions from all three responses. One or two of the suggestions worked once or twice, but nothing worked reliably.
Is it possible that the dataModel itself is corrupt? I rebuilt it by creating a new data model and copying all of the objects into it. Didn't make a difference. After copying the entities into the new data model and rearranging them, I created the custom classes for each. I've been putting my methods in categories on each of the individual classes so I can quickly delete the custom classes and re-create them after making model changes without having to cut and paste the methods. I ran the app once to confirm that it was working and added some sample data, saved and quit. I highlighted the .xcdatamodel and did a Design > Data Model > Add New Version. That created the Config.xcdatamodeld with an unnumbered version of the datamodel (Config.xcdatamodel) and a numbered copy named Config 2.xcdatamodel. I go into Config.xcdatamodel and add a single string attribute to one entity, Clean and Build & Go. I get the missing source model error. Quincey, you asked about the log for PrototypePath. It's: 2010-08-20 11:44:12.044 IconConfig[86221:a0f] Prototype path is /Users/brad/iconConfigClone/IconConfig/IconConfig/build/Debug/IconConfig.app/Contents/Resources/Config.momd 2010-08-20 11:44:12.046 IconConfig[86221:a0f] Prototype URL is file://localhost/Users/brad/iconConfigClone/IconConfig/IconConfig/build/Debug/IconConfig.app/Contents/Resources/Config.momd/ If I delete the attribute I just added, it compiles and runs. The two versions appear in my target's Compile Sources, but the .xcdatamodeld does not. Could this have something to do with the problems I'm having? Is there some build setting that might be causing this? I don't think there's anything tricky going on with my -managedObjectModel or -persistentStoreCoordinator, but, I'd be glad to post the code. Thanks in advance. This is driving me nuts! Brad On Aug 20, 2010, at 12:28 AM, Jack Nutting wrote: > On Fri, Aug 20, 2010 at 8:21 AM, Steve Steinitz > <stein...@datatactics.com.au> wrote: >> - Removed any stray mopping models, just in case >> > > I didn't see your question until you'd already solved it yourself, but > I just wanted to highlight this one point; Assumming you're referring > here to old .mom files, I'd almost bet money that this is the only > thing you needed to do (either manually delete the old file from your > target app, or "build clean"). Like Quincey mentioned, if your app at > runtime finds both Model.mom and Model.momd, it will use the former > and then either ignore the latter or give you cryptic errors (I forget > which). > > -- > // jack > // http://nuthole.com > // http://learncocoa.org _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
