Accessing Logs and Crash Reports on iOS and tvOS

Download and read iOS and tvOS logs and crash reports either directly from device or from TestFlight.


Accessing iOS and tvOS Logs and Crash Reports

iOS applications built with Unreal Engine produce crash logs that developers can use to debug their projects and fix code issues. However, for security reasons, the debug symbols are not available with the crash logs themselves. You will see keys and numbers, but to see names of functions or information about variables in a human-readable format, you need to match your logs to a database of symbols for your project.

There are several processes for re-symbolicating your logs and reading them, depending on how you delivered your debug builds to devices. TestFlight is Apple's application for delivering test builds to a large number of possible devices, and it provides logs from those builds to developers. You can also obtain logs directly through USB debugging.

You need a Mac and Xcode to read logs for iOS projects. Other operating systems and IDEs will not work with the workflows on this page.

1. Accessing Logs Directly from Device

If you are debugging directly through USB or Ethernet, follow these steps to view a symbolicated crash log:

  1. In Xcode, from the main menu, select Window > Devices and Simulators.

  2. Click the iPhone you want to obtain crash data from, then click View Device Logs.

  3. Control-click the log you want to read, then click Re-Symbolicate and export Log.

This will provide a human-readable log with debug symbols.

2. Accessing Logs from TestFlight

When an application delivered through TestFlight crashes, it produces an XCrashPoint file containing crash information. To read these files, you need to have a .dSYM file with debug symbols for your project, then you need to extract the crash report and re-symbolicate it.

For specific information about deploying applications through TestFlight and accessing logs, refer to Apple's documentation on TestFlight. This section will provide information about how to symbolicate them once you have obtained them.

Generating a .dSYM File

To generate a .dSYM file, follow these steps:

  1. Open Unreal Editor.

  2. Open your Project Settings, then navigate to Platforms > iOS > Build.

  3. Enable Generate dSYM file for code debugging and profiling.

    Check the Generate dySM file option

  4. Package your project.

The .dSYM file for your project will appear in your project folder, under /Binaries/iOS.

.dSYM files have a timestamp showing when they were packaged. Take note of this information so you can match .dSYM files to the correct build.

Extracting the Crash Report and Re-Symbolicating

To obtain your crash report and re-symbolicate it so that you can read it, follow these steps:

  1. Obtain an XCrashPointfile from TestFlight. You can use the following command line input to do this.

    export PATH="/Applications/$PATH"

  2. Control-click on the .XCrashPoint file, then click Extract .crash file. You can also export this information using the following command line input:

    export PATH="/Applications/$PATH"

  3. Open XCode, then look at the terminal. Use it to navigate to your Xcode .package.

  4. Use the symbolicatecrash tool by running the following command line:

    export DEVELOPER_DIR="/Applications/" cp -i /Applications/ ././symbolicatecrash unsymbolicated.crash symbols.dSYM > symbolicated.crash

The above instructions use default directories. Use the locations of your .crash and .dSYM files when you run these command lines.

Xcode will then provide a crash log with function names and variables visible.

언리얼 엔진 문서의 미래를 함께 만들어주세요! 더 나은 서비스를 제공할 수 있도록 문서 사용에 대한 피드백을 주세요.
설문조사에 참여해 주세요