For the complete documentation index, see llms.txt. This page is also available as Markdown.

Localized Support Responses for Windows C++, .NET, and macOS

BugSplat's Support Response feature allows developers to display a localized message to their users at the time of a crash. The Support Response feature is currently supported by our Windows C++, .NET, and macOS integrations and support for other platforms is coming soon. The following steps will allow you to create a localized Support Response message for all crashes in your database. These same steps can be applied to create localized stack key specific Support Response messages as well.

This is about the support message, not the dialog's own text. The words on the Windows crash dialog itself — labels, buttons, body copy — come from BugSplatTheme\strings.<bcp47>.json, and BugSplatReporter.exe picks the file matching the end user's own Windows UI language with no configuration at all. The key described below is a separate thing: it is a value you choose and set in code, and it selects which support response your database returns. See Crash Dialog Branding for translating the dialog.

Step 1

Log in to the web application and navigate to the Support Response page to edit the default support response for your database

Step 2

Create a new key for the localized version of your support message by typing a value in the key field. You'll want to remember what you typed here for later.

Step 3

Enter a subject for your support message. This subject is for internal use only and will not be displayed to the customer.

Step 4

In the code you use to initialize BugSplat, provide the value you used for key from step 2.

Support Response Editor

Windows C++

The key is set with SetKey after the BugSplat instance is constructed.

If you're using the dynamic library and the C API, call BugSplat_SetKey instead:

.NET

Mac OS

Step 5

Generate a crash and ensure that the correct support response is loaded, you should see your translated message.

Support Response Page

Last updated

Was this helpful?