0

Simply we have built the app and uploaded to Crashlytics. In case when issue arise we try to check what went wrong but we can't because:

enter image description here

enter image description here

How can we upload missing dsym files? Where can we get it from?

OR

What should we change in project to upload dsyms automatically.

halfer
  • 19,824
  • 17
  • 99
  • 186
Bartłomiej Semańczyk
  • 59,234
  • 49
  • 233
  • 358
  • 1
    check this https://stackoverflow.com/questions/50170638/how-to-find-dwarf-dsym-folder-path-and-dwarf-dsym-file-name-in-xcode-9-3/50170729#50170729 – Reinier Melian Nov 06 '18 at 10:27
  • 1
    and this https://stackoverflow.com/questions/50287216/fabric-api-key-not-valid/50287615#50287615 – Reinier Melian Nov 06 '18 at 10:28
  • Possible duplicate of [Crashlytics: "We're missing a dSYM to process crashes"](https://stackoverflow.com/questions/34077722/crashlytics-were-missing-a-dsym-to-process-crashes) – Mike Bonnell Nov 06 '18 at 15:48

1 Answers1

0

How can we upload missing dsym files? Where can we get it from?

dSYMs files for each archive are found locally on your build machine at the directory /Library/Developer/Xcode/Archives

Right click on your xcarchive file then Show Package Content, you will find your dSYMs directory there, you will have to zip them and upload them to Fabric manually.

You can also get the dSYMs for a specific build from your AppStoreConnect activity page.

What should we change in project to upload dsyms automatically.

By default Fabric dSYMs are uploaded automatically after the archive through the Fabric /run script added to Build Phases in the beginning of Fabric integration.

Though it might fail sometimes for different reasons. Like having the Bitcode enabled

You can also use different tools for build automation like Fastlane which provides an upload dSYMs command.

Mohamed M. Hassanin
  • 41
  • 3