Crash reports are not clear and not being symbolicated

[gouravkumar1207]

Issue:-

Previously we were using embrace 5.X version so we found that iOS crashes are not being symbolicated and error reports like Culture Cloud 0x2d300c _mh_execute_header + 2961420 so after this we updated embrace version from 5.x to 6.x but still facing same issue crash reports are not clear and not being symbolicated.

• iOS Version :—— Swift 5, iOS 16, Xcode 16.0
• Embrace SDK Version :—— 6.4.2
• Whether you are testing on an emulator or physical device ——— we are facing this issue on production for all users (physical device)

[ArielDemarco]

Hey @gouravkumar1207, the SDK does not perform offline symbolication; in our case, the symbolication process is handled by the backend. For this, you'll probably need to add some configuration to your project. Have you followed the guides in the documentation related to this? Just in case, here are the links for version 5.x and 6.x.

[gouravkumar1207]

@ArielDemarco but we are manually uploading DSYM file on embrace from setting section

[ArielDemarco]

By examining the dSYM Upload History and the list of crashes in the Crashes menu, I've noticed that some dSYMs are missing; specifically, the dSYM UUIDs from Culture Cloud and RealmSwift appear to be absent for all the crashes. Unless you locate and upload these specific dSYMs, the dashboard wont be able to symbolicate the crashes. Note that when you open a non-symbolicated crash from the Crashes menu, you can see a suggestion there to use the mfind command to locate those dSYMs on the Mac that performed the build.

That being said, I strongly encourage you to follow the documentation related to automating the symbol upload in your project setup (either if it's 5.x or 6.x). We provide tools so you don't have to manually find dSYMs, which can be particularly challenging if you're uploading your app from a CI environment

[gouravkumar1207]

as you can see in attached screen shot embrace showing we have successfully uploaded correct DSYM file corresponding of UUIDs in 5 nov

[ArielDemarco]

Ok, so digging deeper I found out that there's some sort of weirdness in the dSYM file we've got. Considering the issue is related to the dsym and the process dsym uploading (and given its a not an SDK) issue i'm going to close this issue out and reach out to you in the community slack.

[gouravkumar1207]

Thanks @ArielDemarco