So thankfully I won’t go into a misogynistic blog post a la frustrated Mark Zuckerberg in the movie “The Social Network”, but sometimes you just need to blog to let your technical frustrations out!
I’m doing some complicated Core Data migrations where the lightweight ones won’t work. I’m migrating from one Core Data model to a completely different one, and I’m trying to map those properties over.
I’ve already discovered a wealth of information either through google, trial and error, and a bit of both, which I will share once I’ve got the entire migration code running.
I just have to say here however… I think it’s probably best to avoid these Xcode tools like a mapping model. Because they’re buggy as hell. For example, if you define a mapping model and provide source and destination models, but then change either of those source or destination models, the Mapping Model will no longer work, and even if you re-select the source and destination, it doesn’t matter: You’ve just killed your Mapping Model. Is there any info about this? No. Just “could not find a suitable mapping model”.
I’ve been trying to debug something for 3 HOURS because all you get is an EXC_BAD_ACCESS crash, and ZERO information as to what it’s all about, and NSZombies do nothing.
So I’m sitting here, taking shots into the dark and hope I discover something.
I question whether I should just give up on TOOLS, which are supposed to make your life easier, and just write the whole heavyweight migration in code. If I had started on that 3 hours ago, I’d probably be done. My data model is like 8 entity types.
Is it just me or is the quality of Apple’s tools getting worse? It’s like they produce stuff that’s 80% good. But it’s a tool chain, so 0.8 * 0.8 = 0.64. So you see where this is going…