“Apple Maps Guides”

These two files consume more memory compare than others. So i want to extract/validate the content in that.I can’t really help on the asset catalogue stuff — that’s outside of my area of expertise — but I can offer some guidance with regards your executable.You can poke around inside a Mach-O image using tools like nm, otool and size (see their man pages for more info) but I find it’s better to come at this from the build side. My weapon of choice here is the link map, which lists every symbol included in your Mach-O and its size. To create this link map, set the Write Link Map ( LD_GENERATE_MAP_FILE) build setting. Once you have this map, first use it to verify that your Mach-O doesn’t include extraneous stuff. If it does, you can then investigate why it’s not being stripped out. After that, you can process the data to determine what’s contributing most to the size and use that to guide your optimisations.Share and Enjoy — Quinn “The Eskimo!” Apple Develo

You made it clear that you probably couldn't move away from custom mapping models, but for the awareness of other folks, I'd still mention that using custom mapping models is now discouraged, as discussed here. To to comment your question, every time you change your model version, you need to regenerate the model mapping file so the version hashes are matched. You can do so by executing Xcode File > New > File From Tempdate... menu, pick Core Data > Mapping Model in the new file template sheet and then follow the guide to finish that. If you do re-create the mapping model after changing the model, but still see the “can't find mapping model for migration error, it may be that Xcode fails to create the mapping model with the right hashes, which will be an Xcode bug. In that case, you can probably work around the issue by tweaking the mapping model with your own code. To do that: Figure out the version hashes of the entiti