CODEWITHSUNDEEP
iosxcodeloggingcrashtestflight
Christian A. Strømmen
Christian A. Strømmen

Reputation: 3231

Why aren't the crashlogs from Testflight symbolicating in Xcode?

I just started getting crash reports from Testflights for a pre-release app that I'm working on, but for whatever reason Xcode isn't properly symbolicating the logs.

This is what I'm seeing in Xcode

The build is available (was built, archived and uploaded on this computer in this version of Xcode), so what am I missing here? Why aren't these crash logs symbolicated?

Upvotes: 15

Views: 2421

Answers (3)

codingFriend1
codingFriend1

Reputation: 6807

For anybody getting here because their crash logs are not symbolicated in the XCode Organizer, there are two things required:

  1. You have to have the .dsym files on your computer. If you have the release archive on the same Mac, this is automatic. If not, you need to ask your teammates to hand them to you. (By extracting them from the appropriate archive via Right click > Show in Finder > Show package contents). It seems the dsyms are no longer stored on App Store Connect and cannot be downloaded there.
  2. XCode uses Spotlight to find the .dsyms. Make sure that Developer resources are set to be indexed in System Settings. You can also manually move the .dsyms to a location that you know is being indexed.

Another thing that took me a while to figure out:
If a crash log is not automatically symbolicated, you can manually trigger that by doing a right-click anywhere on the stack trace.

Upvotes: 0

RyanTCB
RyanTCB

Reputation: 8224

I still get this in Xcode 10. As a work around. Add the crash logs to your devices logs and they will be symbolicated. At least in my experience.

Step 1- In Xcode Window>Devices & Simulators [select your device on the left]>view device logs.

Step 2- Then Xcode> Window> Organizer > Crashes tab. Right click a crash and click show in finder. This shows .xccrashpoint files. Right click> show package contents. Drill down into the folders until you see the .crash files. Then drag them into the device logs list we opened in step 1

Upvotes: 2

Christian A. Strømmen
Christian A. Strømmen

Reputation: 3231

Apparently this is a bug that started happening when Apple started accepting bitcode. Not all of the dSYMs are downloaded when you click on 'Download dSYMs…' in the Xcode organizer. Here's how I fixed it:

  1. Manually downloaded the dSYMs from the build page in iTunes Connect
  2. Right-clicked on the crash log in Xcode and opened it in Finder
  3. The xcrashpoint file you'll find is an archive, so right-click and show package contents
  4. Drill down to your .crash file(s)
  5. Copy the .crash file(s) to a different directory, for instance the desktop
  6. Copy the dSYMs folder you downloaded to the same directory
  7. Open Terminal, cd to the folder
  8. In terminal, set the developer dir path:

export DEVELOPER_DIR='/Applications/Xcode.app/Contents/Developer'

  1. Then symbolicate the files with (replace your paths and filenames here):

/Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources/symbolicatecrash name_of_crashfile.crash name_of_downloaded_dSYMs_dir/ > output.log

And voila! You have your symbolicated crash log.

Upvotes: 9

Related Questions