Crashlytics reports with Swift methods are hard to read

Viewed 453

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.

1 Answers

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.

Related