Testing Unity crashes with the sample application ‘myUnityCrasher’

Before you enable your Unity project with BugSplat technology, you may want to take a moment to experiment with our MyUnityCrasher sample application.

First, login to BugSplat with the user name fred@bugsplat.com and password Flintstone.

All crash reports in the fred@bugsplat.com account are actual crashes created with our sample applications. Reports from MyUnityCrasher are mixed in with reports from other applications on the Crashes page.

To view just the MyUnityCrasher crashes, filter using '+ Column Search' button.

To begin using MyUnityCrasher download the BugSplat Unity SDK.

Next open Unity and start a New Project. You can name this project whatever you would like. For this example, our project is named MyUnityCrasher.

Once in Unity, go to Asset and select Custom Package under Import Package. Once there open the BugSplatUnity.unitypackage file previously downloaded. This will place BugSplat into your Assets folder. Double-clicking the package will have the same effect.

Once it is in your asset folder, navigate to and select the folder bugsplat > report > scene. This will bring up the debug scene, which you will double-click on.

Double-clicking will bring up the debug scene. Run this scene by hitting the run scene button (play button) at the top middle of the Unity window.

Once you do this, you will see in the Game Panel the scene UI showing three buttons. Any of these options will post a test crash, but for this example we will use the Prompted Exception button.


By clicking that button, you will post the crash to the test database fred@bugsplat.com. To view it, navigate to the Crashes page.

To send a crash to a different database, set the database property on the Reporter object. Similarly, you can also set the app and version properties on the Reporter object to set the application name and version number respectively