The compiled .momd resources can be loaded after an “existingPartner” fetch request is changed from:
name == $name
to:
name == $NAME
It’s counterintuitive that a part of the object model that does not affect the persistence of data breaks versioning and lightweight migration. It’s clear from the documentation that this should not be the case:
Core Data’s perspective on versioning is that it is only interested in features of the model that affect persistence.
Use the power of the CHOCKLOCK to fix your Fetch Requests or delete them completely and rely on NSPredicates created in code.