Skip to main content

Posts

Fixed : App crash on update with core data changes

Why migration required ? When the model does not match the store, a migration is required. In order to perform a migration, Core Data (technically, an instance of NSMigrationManager) requires these things: The destination managed object model (the one with the changes) A managed object model that can open the existing store The ability to infer mapping between the two models (for a lightweight migration), or a manual mapping model Permission to attempt to perform an automatic migration (for a lightweight migration) It is therefore absolutely essential that you never make changes to the managed object model for a released version of an app. That is, if your app is already in the App Store,  don’t change a single thing in that version of the managed object model . Solution for the Crash while update an application from the app store: Create a  new version  of the managed object model! This reminds me to mention some other best practices to adopt when worki...

Symbolicating Crash Logs

Link to download symbolicatecrash file https://github.com/chrispix/ symbolicatecrash-fix 1. Using XCode:  This is probably the easiest way to symbolicate the crash reports, but not always effective. To symbolicate using XCode you need three files: a.     Crash report (.crash file). b.     Symbol file (.dSYMB file). c.     Application bundle (.app file). In most of the cases you will have “yourapp.ipa” file, to extract “yourapp.app“ from “yourapp.ipa” just change the extension of “yourapp.ipa” to “yourapp.zip” and extract the zip file, you will get a folder named “Payload”, in this folder you will have “yourapp.app” package. 2. Using symbolicatecrash command: Some times XCode do not symbolicate the crash log properly, In this situation we can use symbolicatecrash script manually. Before proceeding keep you “.app”,  ”.dSYM” and “.crash” files in one folder. Now open ...