Versions
BugSplat's Versions Page
Last updated
Was this helpful?
BugSplat's Versions Page
Last updated
Was this helpful?
The page lists each unique application name and version sent to BugSplat. It displays the first and last report dates of each crash report. If symbols have been uploaded with this application name/version, the symbol size will be greater than zero.
Symbol files can be added and removed via the page. Symbol files are required for BugSplat to display call stacks with function names and line numbers. BugSplat will automatically clean up symbol files that are no longer in use, and in most cases, you will not need to remove symbol files manually. If you uploaded incorrect symbol files, uploaded duplicates, or have uploaded extraneous symbol files, we recommend removing unnecessary files so that BugSplat can process your crashes as fast as possible.
Symbols are typically uploaded using command line tools (such as ) as part of your build process. If you'd like to add Symbol files manually, you can use the Upload Symbols button to upload symbols for a new version or expand a row to upload symbols to an existing version. For more information on manually uploading symbols, please visit this . To remove symbol files, expand a row that corresponds to the version you'd like to remove and click the Delete button. Note that the row showing the application name/version will not be deleted, but it will show a size of zero.
If needed, you can retire old versions of your application using the page. BugSplat does not process crash reports from retired versions, nor do they contribute to your crash volume. Since retired crash reports are essentially invisible to you, we suggest retiring versions only if you no longer support that version of the product.
BugSplat's and SDKs support the creation of . Full Dump support can be added to your subscription for an additional cost. We recommend only enabling Full Dump support on an as-needed basis to ensure end-user crash uploads and processing happens quickly. If you are interested in Full Memory Dumps, please contact our team. Once Full Dump support has been added to your account, you can enable it on a per-version basis. First, navigate to the page, click the Columns button, and ensure the Full Dumps column is visible. Next, click the checkbox for the version generating Full Memory Dumps. Finally, you will need to ensure your application has configured BugSplat to generate Full Memory Dumps when this setting is enabled.
For more information on how to configure the BugSplat SDK to generate Full Memory Dumps, please see this .
