Crash symbolication

Bugsee is able to properly process and symbolicate crash reports that are uploaded from your users. Even if your binary has its symbol stripped, Bugsee will do wonders guessing the right symbols. In some cases it might be enough to root cause the problem, however best results will be achieved when Bugsee can match a crash report with a symbol file (dSYM) of crashed build.

Bugsee can automatically upload managed (PDB/MDB) and platform native (like, dSYM) debug symbols during the build phase. The system is smart enough to automatically match the right symbols to a crash report.

Auto upload

Symbols are collected and uploaded during build. We install several hooks into target projects build flow which are triggered autmatically.

The only thing you need to do is specify your Bugsee application token for your Project to let us properly link debug symbols. Add special assembly attribute BugseeAppToken to ${Project-Root}/Properties/AssemblyInfo.cs file (If it does not exists, create one).

using System.Reflection;
using System.Runtime.CompilerServices;
using System.Runtime.InteropServices;
using BugseePlugin;

// Various [assembly: Attr()] declarations go here

// Add this line:
[assembly: BugseeAppToken("YOUR-ACTUAL-TOKEN-HERE")]

Manual dSYM upload

In some cases you might need to upload dSYM files manually. Bugsee accepts .zip files with one or multiple dSYM files inside. Once you have located the files and compressed them into an archive, click on the "Manual upload" button within Bugsee and either drag your files over the dialog or click on it to open the file browser:

Manual upload

Once a dSYM file is uploaded manually, we are going to re-process old issues related to that specific build, the process might take some time, usually several minutes.