LogRocket displays captured session errors and crashes in the Logs pane of the session replay Developer tab. If your application code is minified or obfuscated, you will need to upload debug files from your app build to see decoded symbol names in the associated stack traces.

Upload debug files to LogRocket

Self hosted instances require additional steps, and should follow the documentation here.

To upload files you will need to install the LogRocket command line tool (requires version 0.14.0 or above):

npm install -g logrocket-cli

Unlike for JavaScript source maps, it is not necessary to create a release through the CLI before uploading mobile debug files. However, you must provide a release identifier that matches your CFBundleVersion.

LogRocket uses the dSYM files generated when an application is built to symbolicate iOS stack traces. To upload these files for use by LogRocket, use the following command:

logrocket upload-mobile  
    --platform ios  
    --release="release_identifier"  
    --apikey="your:api:key"  
    ./path/to/debug/files/myApplication.app.dSYM/

You can create an API key in the LogRocket dashboard under Settings > API Keys.

The cli will recursively scan the contents of the provided directory for relevant files and attempt to upload them (the --verbose flag can be used to see the full list of matching files). Multiple paths can be passed to the command if necessary. Once the files are uploaded, they will be used for symbolicating incoming stack traces from sessions using the specified release version.

For more information on iOS stack traces and debug files, see official documentation here.

Mobile stack traces in Issues

Stack traces are available within an iOS exception/error's Issue Details view below event previews.