GitBook: [#277] updating attachements

Author: splatyourbugs

.gitbook/assets/log-viewer-bs.gif

@@ -1,10 +1,10 @@
 # Who is BugSplat?
 
-### **Our Story **
+### **Our Story** 
 
 BugSplat started in 2004 as an informal side project by David Plunkett and a couple of friends.
 
-Dave and the gang had built and maintained crash reporting tools at much larger software companies in their previous roles.  This was an experience that led them to three big takeaways: 
+Dave and the gang had built and maintained crash reporting tools at much larger software companies in their previous roles.  This was an experience that led them to three big takeaways: 
 
 1. Crash reporting was a nearly magical tool for finding and fixing crash defects.  \
 
@@ -43,13 +43,13 @@ Through it all we’ve maintained a laser focus on providing our users with the
 
 Despite the industry changes we’re still 100% self-funded and have never accepted outside investment. That means we only answer to you, our customer. We're lean, profitable, growing, and supporting ourselves and our families through this business.
 
-Today BugSplat helps developers track and fix over 500 million crashes on around 350 million computers, tablets, consoles, and phones every year. 
+Today BugSplat helps developers track and fix over 500 million crashes on around 350 million computers, tablets, consoles, and phones every year. 
 
 We know that we have an amazing gig with BugSplat. It’s a lot of work, sure, but we work every day on interesting problems with great partners. We’re a fully remote company that emphasizes flexibility, self-responsibility, and personal and professional exploration.
 
 All of this is to say...
 
-If you're a BugSplat user, thank you for making this happen. If you're not a user yet, please consider [signing up](https://app.bugsplat.com/v2/sign-up).  
+If you're a BugSplat user, thank you for making this happen. If you're not a user yet, please consider [signing up](https://app.bugsplat.com/v2/sign-up).  
 
 Cheers,
 

about/who-is-bugsplat/README.md

@@ -1,8 +1,8 @@
 # Billing and Plan Management
 
-This segment focuses on helping using to manage their current billing, update account settings around billing, and add or remove credit cards associated with BugSplat accounts.  
+This segment focuses on helping using to manage their current billing, update account settings around billing, and add or remove credit cards associated with BugSplat accounts.  
 
-**Not finding what you're looking for? **
+**Not finding what you're looking for?** 
 
 Try searching for it using the search bar at the top right of this screen.  If you still can't find the answer you're looking for,  please send us a note at [[email protected]](mailto:[email protected]).  You can also drop by our [Discord Server](https://discord.gg/K4KjjRV5ve) and talk to us directly.
 

administration/billing/billing-and-plan-managment/README.md

@@ -1,12 +1,12 @@
 # FAQs
 
-### **Welcome to the BugSplat FAQs Documentation.  **
+### **Welcome to the BugSplat FAQs Documentation.**  
 
-In this segment, users will find answers to commonly asked questions about the BugSplat app and crash reporting.  
+In this segment, users will find answers to commonly asked questions about the BugSplat app and crash reporting.  
 
 Use the left-hand menu to navigate to specific FAQs or search for your topic using the search feature at the top right-hand of the page.
 
-### **Not finding what you're looking for? **
+### **Not finding what you're looking for?** 
 
 If you still can't find the answer you're looking for,  please send us a note at [[email protected]](mailto:[email protected]).  You can also drop by our [Discord Server](https://discord.bugsplat.com) and talk to us directly.
 

education/faq/README.md

@@ -2,6 +2,6 @@
 
 Crash reports uploaded to BugSplat are typically quite small. However, you can add additional data to each crash report, for example, many customers include log files. If you add additional data to crash reports, be aware that your BugSplat subscription has crash report size limitations. The size limitations apply to the total size of the compress (zipped) crash report.
 
-Crash uploads are limited to **20 MB **(compressed), this includes the size of the minidump file or other crash artifacts generated by BugSplat, which are typically less than **50k**.  
+Crash uploads are limited to **20 MB** (compressed), this includes the size of the minidump file or other crash artifacts generated by BugSplat, which are typically less than **50k**.  
 
 BugSplat allows larger upload size limits for Enterprise level users.

education/faq/bugsplat-application-uptime-data/what-are-the-upload-size-considerations-with-bugsplat-accounts..md

@@ -34,7 +34,7 @@ When you define a crash group, all new crashes will be processed according to it
 You can only define a single group-by-level for any top-level stack frame. When you define a group-by-level, any existing crash groups for the top-level stack frame are removed.
 {% endhint %}
 
-Crash group-by-level is powerful and operates on all crashes related to the same top-level stack frame, but group-by-level is a blunt tool that doesn't work for every situation. What if some crashes don't have your interesting** **code at the selected level? If you want to do more surgical crash grouping, you need **group-similar.**
+Crash group-by-level is powerful and operates on all crashes related to the same top-level stack frame, but group-by-level is a blunt tool that doesn't work for every situation. What if some crashes don't have your interesting **** code at the selected level? If you want to do more surgical crash grouping, you need **group-similar.**
 
 #### Group Similar Crashes 
 
@@ -52,6 +52,6 @@ Let's return to our example above. We first created a group-by-level crash group
 
 Any individual crash group can be deleted. This applies to groups created with group-similar and for any single group that was automatically created with group-by-level.  You can also remove all crash groups for a single top-level stack frame.
 
-**Grouping of Existing Crashes **
+**Grouping of Existing Crashes** 
 
 When you define a crash group, you select a timeframe for regrouping existing crashes in your database. The grouping for crashes older than the selected timeframe will not be modified.  

education/how-tos/crash-grouping-concepts.md

@@ -14,7 +14,7 @@ This **Development** section includes articles that are useful for using BugSpla
 
 ****[**Commenting**](commenting.md) - is BugSplat's built-in comment tool and issue tracker.
 
-[**3rd Party Tools**](integrating-with-tools/)** **- compliment your workflow by integrating BugSplat with your issue tracker, messaging app, or another tool.
+[**3rd Party Tools**](integrating-with-tools/) **** - compliment your workflow by integrating BugSplat with your issue tracker, messaging app, or another tool.
 
 [**API**](web-services/) – is an overview of the BugSplat API.
 

introduction/development/README.md

@@ -72,10 +72,16 @@ The Crash page includes valuable information like crash time, environment, corre
 
 ### Additional Information
 
-All data covered to this point on the Crash page are found under the **Crash Overview** tab. To access additional information about crashes like **Other Threads**, **Registers**, **Modules**, **Debugger Output**, and **Attachments** — use the tabs found above the **User Details** module.
+All data covered to this point on the Crash page are found under the **Crash Overview** tab. To access additional information about crashes like **Other Threads**, **Registers**, **Modules**, **Debugger Output**, and **Attachments** — use the tabs found above the **User Details** module. 
 
 ![](<../../.gitbook/assets/viewing-tabs-crashreport (1) (2) (2) (2) (2) (2) (2) (2) (2) (2) (2) (2) (2) (2) (2) (2) (2) (2) (2) (1).gif>)
 
+#### Previwing attached files&#x20;
+
+To preview or download an attached file, simply navigate to the **Attachments** tab in a crash report and click on the right arrow next to the attachment name in order to load a preview of the attached text.
+
+![](../../.gitbook/assets/log-viewer-bs.gif)
+
 ## Summary
 
 The [Summary](https://app.bugsplat.com/v2/summary) page shows a view of an application's crash data which automatically groups crashes by the top line of the call stack, allowing users to see which defects are occurring most frequently.

introduction/development/using-the-app.md

@@ -1,11 +1,11 @@
 # Source Maps
 
-BugSplat has the ability to convert uglified and minified JavaScript stack traces into function names and line numbers from the original source. You can upload [source map](https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Use_a_source_map) files to BugSplat during your build process by leveraging [@bugsplat/symbol-upload](https://www.npmjs.com/package/@bugsplat/symbol-upload).
+BugSplat has the ability to convert uglified and minified JavaScript stack traces into function names and line numbers from the original source. You can upload [source map](https://developer.mozilla.org/en-US/docs/Tools/Debugger/How\_to/Use\_a\_source\_map) files to BugSplat during your build process by leveraging [@bugsplat/symbol-upload](https://www.npmjs.com/package/@bugsplat/symbol-upload).
 
-In order to correctly unwind uglified stack traces, you’ll need to ensure that the filename of the source map matches the file name of the original source file. For instance, if your build process generates a file `main.153ee63b.chunk.js`, the corresponding source map file should be named `main.153ee63b.chunk.js.map`. 
+In order to correctly unwind uglified stack traces, you’ll need to ensure that the filename of the source map matches the file name of the original source file. For instance, if your build process generates a file `main.153ee63b.chunk.js`, the corresponding source map file should be named `main.153ee63b.chunk.js.map`. 
 
 {% hint style="info" %}
 Be sure to upload source maps for each released version of your application for best results.
 {% endhint %}
 
-If BugSplat is unable to convert the uglified stack trace back to the original source the **Debugger Output **tab will display diagnostic information from the BugSplat backend that will help you troubleshoot.
+If BugSplat is unable to convert the uglified stack trace back to the original source the **Debugger Output** tab will display diagnostic information from the BugSplat backend that will help you troubleshoot.

introduction/development/working-with-symbol-files/source-maps.md

@@ -22,5 +22,5 @@ Once these steps are complete, users should learn more about using the BugSplat
 If at any point you get stuck and want some help—please reach out to us via our [Discord](https://discord.gg/K4KjjRV5ve) or by sending us an [email](mailto:[email protected]).
 
 {% hint style="success" %}
-🧙‍♂️** Attention new accounts**: You will also have the opportunity to follow these steps via the onboarding helper tool that's visible to new users right after they [create an account](signing-up-for-an-account-with-bugsplat.md).
+🧙‍♂️ **Attention new accounts**: You will also have the opportunity to follow these steps via the onboarding helper tool that's visible to new users right after they [create an account](signing-up-for-an-account-with-bugsplat.md).
 {% endhint %}

introduction/getting-started/README.md

@@ -118,11 +118,11 @@ Once you've posted an exception or a minidump to BugSplat click the link in the
 
 ## WebGL
 
-A few settings must be changed in order to capture function names and line numbers in a WebGL exception report. Open **File > Build Settings **and switch the platform to **WebGL** and check **Development Build.**
+A few settings must be changed in order to capture function names and line numbers in a WebGL exception report. Open **File > Build Settings** and switch the platform to **WebGL** and check **Development Build.**
 
 ![Unity Build Settings Menu](../../../../.gitbook/assets/unity-build-settings.png)
 
-Click the button that says **Player Settings**, highlight the **Player** section. Under **Publishing Settings**, select **Full With Stacktrace**. 
+Click the button that says **Player Settings**, highlight the **Player** section. Under **Publishing Settings**, select **Full With Stacktrace**. 
 
 ![Unity Player Publishing Settings](../../../../.gitbook/assets/unity-full-with-stack-trace.png)
 

introduction/getting-started/integrations/game-development/unity.md

@@ -34,7 +34,7 @@ Remember the values you use for {database}, {appName}, and {appVersion}. You wil
 
 #### Unreal Engine 4.25 and older
 
-For capturing crashes in packaged games in Unreal Engine 4.25 and earlier,** **copy `DefaultEngine.ini` to `{{output directory}}\Engine\Programs\CrashReportClient\Config\NoRedist` making sure to create folders that don't exist.
+For capturing crashes in packaged games in Unreal Engine 4.25 and earlier, **** copy `DefaultEngine.ini` to `{{output directory}}\Engine\Programs\CrashReportClient\Config\NoRedist` making sure to create folders that don't exist.
 
 **Unreal Engine 4.26 and newer**
 
@@ -52,7 +52,7 @@ Package your game, check that the **Include Crash Reporter** and **Include Debug
 
 ### Step 3
 
-To create symbolic call stacks on Windows platforms you will need to upload symbol and executable files. The easiest way to upload files is to use our `SendPdbs` command line utility. `SendPdbs` can be downloaded either by [clicking here](https://app.bugsplat.com/browse/download_item.php?item=sendpdbs) or via the [SendPDBs](../../../../education/faq/using-sendpdbs-to-automatically-upload-symbol-files.md) doc. Run it from your build folder using the following commands.
+To create symbolic call stacks on Windows platforms you will need to upload symbol and executable files. The easiest way to upload files is to use our `SendPdbs` command line utility. `SendPdbs` can be downloaded either by [clicking here](https://app.bugsplat.com/browse/download\_item.php?item=sendpdbs) or via the [SendPDBs](../../../../education/faq/using-sendpdbs-to-automatically-upload-symbol-files.md) doc. Run it from your build folder using the following commands.
 
 ```bash
 cd {your build folder}

introduction/getting-started/integrations/game-development/unreal-engine.md

@@ -8,13 +8,13 @@ Enable the Address Sanitizer by choosing the Enable Address Sanitizer (/fsanitiz
 
 ![Visual Studio Enable Address Sanitizer](../../../../.gitbook/assets/screen-shot-2021-08-03-at-5.14.10-pm.png)
 
-Modify the Visual Studio Include Directories so that the Address Sanitizer header files can be located: 
+Modify the Visual Studio Include Directories so that the Address Sanitizer header files can be located: 
 
 ![](../../../../.gitbook/assets/screen-shot-2021-08-03-at-5.27.05-pm.png)
 
-## Modify Initialization Code 
+## Modify Initialization Code 
 
-To hook into the Address Sanitizer you will call **\__asan_set_error_report_callback**_ _with the BugSplat **createAssanReport** method.  To do this, we'll need a global instance of the BugSplat MiniDmpSender object and a new asanCallback function. See below for how you would modify our myConsoleCrasher sample program:
+To hook into the Address Sanitizer you will call **\_\_asan\_set\_error\_report\_callback** __ with the BugSplat **createAssanReport** method.  To do this, we'll need a global instance of the BugSplat MiniDmpSender object and a new asanCallback function. See below for how you would modify our myConsoleCrasher sample program:
 
 ```cpp
 ...
@@ -42,7 +42,7 @@ int wmain(int argc, wchar_t** argv)
 }
 ```
 
-## Create Memory Corruption Test 
+## Create Memory Corruption Test 
 
 The only step left is to generate a memory corruption that Address Sanitizer will catch.  Here's one way to do that:
 
@@ -91,7 +91,7 @@ void HeapCorruption() {
 	}
 ```
 
-Calling HeapCorruption (or your own memory error code) will generate the Address Sanitizer report and send a crash report to BugSplat. 
+Calling HeapCorruption (or your own memory error code) will generate the Address Sanitizer report and send a crash report to BugSplat. 
 
 ## Crash Report Result
 

introduction/getting-started/posting-a-test-crash/myconsolecrasher-c-plus-plus/address-sanitizer-reports.md

@@ -4,7 +4,7 @@ To register an account with BugSplat, visit the [Sign Up](https://app.bugsplat.c
 
 ![](../../.gitbook/assets/screen-shot-2021-08-24-at-9.55.33-am.png)
 
-Once you've hit **Sign Up** you'll be a registered user of BugSplat.  
+Once you've hit **Sign Up** you'll be a registered user of BugSplat.  
 
 Then, you'll be presented with a screen welcoming you to BugSplat.  Here you can either go through a guided onboarding which aids in quickly configuring new accounts, or you can skip the onboarding and go directly to the [Dashboard](../development/using-the-app.md#dashboard) page.
 
@@ -13,5 +13,5 @@ Then, you'll be presented with a screen welcoming you to BugSplat.  Here you can
 
 
 {% hint style="info" %}
-🤝 **Looking to get access to an existing team? **You can request access from a team member using this form [here](https://app.bugsplat.com/v2/sign-up/team-access). Learn more about requesting access [here](../../administration/introduction/requesting-access-to-your-teams-accounts.md).
+🤝 **Looking to get access to an existing team?** You can request access from a team member using this form [here](https://app.bugsplat.com/v2/sign-up/team-access). Learn more about requesting access [here](../../administration/introduction/requesting-access-to-your-teams-accounts.md).
 {% endhint %}

introduction/getting-started/signing-up-for-an-account-with-bugsplat.md

@@ -33,7 +33,7 @@ Renames post and delete to postSymbols and deleteSymbols respectively
 
 * Changes the order of the parameters for BugSplatApiClient's createAuthenticatedClientForNode and createAuthenticatedClientForWebBrowser functions so that host can be an optional parameter with a default value
 
-## iOS - **Update - **September 26th, 2021
+## iOS - **Update -** September 26th, 2021
 
 * Updated documentation.