All posts

Tag

Guides

Crash and error reporting for the platforms and languages you actually ship on. Step-by-step setup and integration for Unreal, Unity, Xbox, PlayStation, Switch, iOS, Android, C++, and more. Start here to get BugSplat running.

Guides ·

Crash and Error Reporting for .NET

.NET fails in two different ways, and you want both covered. There's the hard crash, the process dies, often down in native or interop code, and there's the unhandled exception, the far more common case where something throws, a feature breaks, and the app limps on

BugSplat Team BugSplat Team · 2 min read
Guides ·

Crash Reporting for Electron

Crash Reporting for Electron Electron apps fail in two languages at once. There's the JavaScript layer, where you get exceptions and stack traces that look familiar. And there's the native layer underneath, the Chromium and Node internals, where a crash dumps a minidump that has nothing

BugSplat Team BugSplat Team · 2 min read
Guides ·

How to Make Unreal's Crash Dialog Your Own

Your game crashes. At the worst possible moment, mid-match, on the verge of a win, the screen dies and Unreal's Crash Report Client pops up. By default, the dialog the player sees is the generic version, the one that ships with the engine before any studio makes

BugSplat Team BugSplat Team · 3 min read