Wednesday, July 1, 2026
HomeiOS Developmentios - Why do some dSYMs have the identify of targets and...

ios – Why do some dSYMs have the identify of targets and a few have hex names?

[ad_1]

If I create an archive of my app then look domestically inside the .archice/dSYMs the information in there have human readable reads similar to nameOfMyApp.app.dSYM, nameOfAnExtension.appex.dSYM and there are 5 of them in complete (I’ve 4 app extensions).

However then after importing this archive to Testflight, if I obtain the dSYMs from there there are actually 8 of them and have names like 11b18846-7eec-38f4-bdd5-8df4f1df42c1.dSYM

Why is there this distinction?

When crashlytics says there’s a lacking dSym, is it potential to add the native human-readable dSYMs slightly than the TestFlight ones? (the rationale I wish to do that is complicated to elucidate and political). Nevertheless it could seem its not potential to do that as a result of after they’re uploaded to crashlytics their inner uuid is displayed (within the command line) and it would not correspond to any of the uuids crashlytics says is lacking and crashlytics continues to say they’re lacking.

So what are these dSYMs with human readable names and what’s their function/use if those in Testflight are the helpful ones?

[ad_2]

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments