Derived attributes are available since iOS 13 and aim to improve fetch performance in many different scenarios. ... You can symbolicate a crash log with Xcode 9 ... Tag: ios,crash,xcode6,symbolicatecrash,symbolicate I have recently submitted an app to the app store and it has gotten rejected. The app I made was specifically iPhone only, however i was unaware that you had to make sure it ran on an iPad as well (Apple Guidelines 2.10) and hence my app was rejected due to it crashing when the reviewers ran it ... After reading all these answers here in order to symbolicate a crash log (and finally succeeding) I think there are some points missing here that are really important in order to determine why the invocation of symbolicatecrash does not produce a symbolicated output. There are 3 assets that have to fit together when symbolicating a crash log: La tentative de symbolicate le crash de journaux à partir de Xcode, l'organisateur a malheureusement fait absolument rien, et tente d'utiliser la symbolicatecrash fichier dans Xcode du contenu de l'emballage a également échoué. Si je suis là, à gauche avec la seule autre option que je connais. These unique dSYMs are identified by a UUID marked in both the crash log and dSYM bundle. As such, a dSYM bundle from a Debug iPhone Simulator Build will not map properly with a Release Build. Hence it is important to collect the dSYMs appropriate for the crashes you are working with, especially once you've launched your app into the wild. Не понятно почему, они выслали crash log, но я не уверен, что все понимаю: P.S. Я сделал Symbolicate через XCode и получил более детальный Crash Log: Можно увидеть backtrace исключения: