Crashlytics reports with Swift methods are hard to read

Question

I recently discovered problems reading Crashlytics reports for crashes in Swift code.
In the picture below you can see what happend to the method names. I've highlighted the interesting information in it:

String+File.swift line 21 $SSo7UIImageC7mymoduleE4load_5blocky10Foundation3URLV_yABSg_s5Error_pSgtctFZ080$S7mymodule23ProfileViewControllerC18loadProfilePictureyy10Foundation3URLVFySo7a6CSg_s5G9_pSgtcfU_AC0ijK0CSgXwz_XxTf1ncn_nTf4ndn_n

It is still usefull but harder to read and understand. Even though, sometimes it doesn't help at all.

I just wonder if there is a way to fix this.

Stayathome

xcrun swift-demangle most likely is what you are looking for – Haddix

@Haddix is right. here is more on Swift mangling – Fattish

I'm experiencing the same issue. This may lead to something (the "Dealing with mangled symbols" section). It could be related to the migration they're making to the Firebase, because it has started a couple days ago for me, with an app already in production. – Eward

Mike from Firebase and Fabric here. Any symbolication changes are unrelated to any migrations. If you can contact support(at)fabric(dot)io with a link to the issues that you believe aren't being symbolicated correctly, please do so that we can dig in more. – P

Answer 1

I had the same issue. It seems to be issue on Crashlytics side. When you use latest (Crashlytics 3.11.1, Fabric 1.8.2) Frameworks then issue is visible. Workaround is to use oldest version. For example: (Crashlytics 3.10.7, Fabric 1.7.11). I reported this bug to Crashlytics support team.

Vasiliki

Can you please confirm these versions (Crashlytics 3.10.7, Fabric 1.7.11) provides a solution for this problem? Recently I tried to use these versions and reports are still wrong mangled. – Comitia