MultiConnectSDK › SDK Apps
14. Errors
What is caught
After McApp.StartAsync, MultiConnectSDK reports your game's errors to the dashboard by itself:
- every exception, and every
Debug.LogError, in Unity; - unhandled exceptions, and exceptions in tasks nobody awaited.
A crash that closes the game still reports: the error is written to the device straight away and sent on the next start.
Not caught:
- native crashes (signals, ANRs, out-of-memory kills), which need a native crash reporting SDK;
- errors that happen before
McApp.StartAsyncruns.
Cost on the device: each distinct error is sent once per session with a count, at most 20 distinct errors are queued, and sends happen at most every 30 seconds.
Report caught exceptions and server errors
Script 14.1: Report an exception you caught
using System;
using MultiConnect.App;
public static class SafeCall
{
public static void Run(Action action)
{
try { action(); }
catch (Exception ex) { McAppErrors.Report(ex); }
}
}
On a game server or .NET API, call McAppErrors.StartForServer() once at startup. It reads the SDK key from MC_SDK_KEY, or takes it as an argument. Server errors are marked as coming from a server.
The Errors page
On the app page, open Errors.
- Grouping: errors with the same cause are grouped across builds.
- Each group shows its count, the players affected, platforms and versions, a stack trace, and recent samples with the device, OS and the last log lines before it.
- Resolve, Ignore or Reopen a group. A resolved group opens again only if it happens on a newer version than the one you resolved it in, so you hear about real regressions only.
Collect turns error reports off and on for the app.

