---
title: Crash Logs
description: Couchbase Lite on Objective-C -- Using symbolicate to decode crash logs
pubDate: 2026-08-17T09:53:44.266Z
antora:
  editUrl: https://github.com/couchbase/docs-couchbase-lite/edit/release/3.3/modules/objc/pages/troubleshooting-crashes.adoc
  xref: xref:3.3@couchbase-lite:objc:troubleshooting-crashes.adoc[]
---

[Consult the llms.txt file for a full list of contents](/llms.txt)
[View original HTML](/couchbase-lite/3.3/objc/troubleshooting-crashes.html)

# Crash Logs

> Description — _Couchbase Lite on Objective-C — Using symbolicate to decode crash logs_  
> Related Content — [Using Logs](troubleshooting-logs.md) | [Troubleshooting Queries](troubleshooting-queries.md)

## [](#symbolication)Symbolication

In order to make sense of a crash report you will need to symbolicate its content. Symbolication being the process of replacing memory addresses in a crash report with human-readable function names and line numbers.

## [](#finding-local-dsym)Finding local dSYM

To locate the local dSYM files:

* For scheme based builds, they are located in the derived data path
* For the target based builds, they are located in the configuration build directory path, as specified in the _target_ setting
* For archives, they are located in `.xcarchive`.

> [!TIP]
> If you still cannot locate the file, then use `mdfind` as described in the _Symbolication Troubleshooting_ section of the _Apple Technical Note TN2151 — Understanding and Analyzing Application Crash Reports_: <https://developer.apple.com/library/archive/technotes/tn2151/%5Findex.html>

## [](#the-couchbaselite-dsym)The CouchbaseLite dSYM

Couchbase Lite's `dSYM` folder is located in the same directory as the Couchbase Lite binary framework (this also applies for _Cocoapod_ and _Carthage_). It has the same filename as framework but has a `.dSYM` extension.

Example 1\. dSYM in CouchbaseLiteSwift

```objc
couchbase-lite-swift_enterprise_2.7.0/iOS/CouchbaseLiteSwift.framework.dSYM
```

## [](#how-to-obtain-the-dsym-file-for-your-app)How to obtain the `.DSYM` file for your app

To symbolicate crash reports generated by these apps you must download the generated dSYM files. Do this using _Xcode's Organizer_ or direcly from _App Store Connect_.

### [](#downloading-dsym-using-xcode-organizer)Downloading dSYM using Xcode Organizer

1. Within _Xcode's_ _Archives Organiser_, select the required archive
2. Within the _Archive Information_ dialog panel, select **Download Debug Symbols** button  
The dSYM files are downloaded to the archive bundle in a folder named `dSYMs`  
See _Download debug symbols_: <https://help.apple.com/xcode/mac/current/#/devef5928039>

### [](#downloading-dsym-directly-from-app-store-connect)Downloading dSYM directly from App Store Connect

1. Inside _My Apps_ choose the **Activity** section
2. Locate the required build (the one you want to download dSYM files for)
3. In the _Includes Symbols_ column, select the download `dSYM` link .

## [](#using-third-party-crash-report-tools)Using third-party crash report tools

You can upload your dSYM files to third-party crash reporting tools for analysis, either automatically via script or a manual _zip_ file upload. Links for some of the more popular crash reporting tools are included below.

Example 2\. Third party crash reporting tools

* Firebase Crashlytics: <https://firebase.google.com/docs/crashlytics/get-deobfuscated-reports>
* Instabug: <https://docs.instabug.com/docs/ios-symbolication>
* Bugsee: <https://docs.bugsee.com/sdk/ios/symbolication/>
* Microsoft Visual Studio App Center: <https://docs.microsoft.com/en-us/appcenter/diagnostics/ios-symbolication>
* Apteligent: <https://www.apteligent.com/technical-resource/symbolicating-an-ios-crash-report/>

## [](#obfuscated-symbols-%5Fhidden)Obfuscated symbols (`_hidden`)

Xcode includes obfuscated symbols in dSYM files if apps are uploaded to Apple without symbols.

In such cases you need to to de-obfuscate dSYM files before symbolicating. De-obfuscation is done automatically if downloading through Xcode. But if you use _App Store Connect_, you may need to, use the `xcrun` command on each .dSYM file inside the downloaded dSYM folder.

Example 3\. De-obfuscation using xcrun

```objc
xcrun dsymutil -symbol-map <pathToApplicationArchieve>.xcarchive/BCSymbolMaps <pathToDownloadedDSYMs>/3B15C133-88AA-35B0-B8BA-84AF76826CE0.dSYM
```

> [!TIP]
> See Translating 'hidden' symbol names back to their original names: <https://developer.apple.com/library/archive/technotes/tn2151/%5Findex.html>

## [](#related-content)Related Content

###### [](#)

How to . . .

* [Prerequisites](gs-prereqs.md)
* [Install](gs-install.md)
* [Build and Run](gs-build.md)

.

###### [](#-2)

Learn more . . .

* [Databases](database.md)
* [Documents](document.md)
* [Blobs](blob.md)
* [Remote Sync Gateway](replication.md)
* [Handling Data Conflicts](conflict.md)

.

###### [](#-3)

Dive Deeper . . .

[Mobile Forum](https://forums.couchbase.com/c/mobile/14) | [Blog](https://blog.couchbase.com/) | [Tutorials](https://docs.couchbase.com/tutorials/)

.