Guides

Crash Reporting for Xbox

A crash on Xbox is a different kind of problem than a crash on PC. You can't ask a player to dig a log file out of a folder. You can't reproduce it on a dev kit you don't have in front of you.

Crash Reporting for Android

If you're shipping native C++ on Android through the NDK, the crash story is different from anything in the managed Java or Kotlin world. A crash in your native layer doesn't give you a tidy Java stack trace. It gives you a native signal and a

Divide by Zero Crashes: What They Are and How to Track Them Down

If you've seen INT_DIVIDE_BY_ZERO in a crash report, or watched your app vanish with an "integer division by zero" error, you've hit one of the more abrupt failures in native code. There's no graceful exception to catch, no warning.

Crash Reporting for Nintendo Switch 2

Switch 2 is a new platform, and new platforms are where crashes hide. New hardware, new performance envelope, and a player base that will run your game in ways your test plan never imagined. Add the usual console constraints, no log file to walk a player through, no remote access,

Crash Reporting for PlayStation

When a PlayStation build crashes, you're debugging a console you can't treat like a PC. No log folder to walk a player through, no remote shell, often no way to reproduce it on the dev kits you have on hand. And on a platform where stability

Crash Reporting for iOS

iOS crash reports are technically available and practically useless until you symbolicate them. Apple gives you a .crash file full of memory addresses, and the only thing that turns those addresses into your function names and line numbers is the matching .dSYM. Miss that match and you're staring