BugSplat is pleased to announce our integration with Assembla, a popular project and program management tool. This integration allows user to create defects directly from crash reports or Stack Keys in Assembla. Hyperlinks allow quick navigation from defects to crash reports and back. Defects created from BugSplat automatically include symbolic call stack information as well as other crash-specific data that can help your team crush bugs faster. Get more information on this integration in our docs.

Today we're announcing BugSplat's new look to our customers via email. We've made some pretty significant updates, and we're excited to walk you through them.

BugSplat now includes local variables and function arguments for our Windows Native, Unity, and Unreal C++ integrations. By including local variables and function arguments, we can provide another level of contextual information about the cause of your crash. This new feature may help reduce or eliminate the need to debug a crash report on your local development machine.

BugSplat can now (as of 23-August-2019) create an issue in Github issues from any crash report or StackKey. Github Issues is a popular issue/bug tracker used by teams everywhere in conjunction with their Github accounts. You can learn more about Github issues here.

We consider ourselves tech savvy. If you are reading this blog, you probably do too. And like us, you probably expect that computers are just supposed to work for you. However, in my experience, this close relationship we share with our machines just expands the realm of possible annoyances we encounter. Here are some easy ways to help you improve your relationship with the most important piece of equipment in your working life.

Crash reporting can alter the balance between support and development, and swing it in your favor! Sure "literally" is an overused term. But, I think it’s fair to say that “LITERALLY” nobody likes it when software crashes. Users don’t like it when the software they love using breaks. They’re left wondering what happened and how long will it be until there’s a fix.

You’re in the process of creating and launching new softwareand you want it to be as stable as possible. Or, maybe your software has been running for a while, but you’re frustrated with the bug-reporting workflow in place. Either way it’s time to look for a crash reporting process that fits your application. This leads to a natural question: Should we build it? Or should we buy it?

As part of our continuing security program here at BugSplat, we’re switching to an authentication service called Auth0 for all of our account logins. Auth0 is a universal authentication and authorization platform that supports customer-requested features like federated logins, which means authenticating with a different provider, and Multi-Factor Authentication (MFA) which is a two-step login protocol requiring separate verification from a mobile device to access your account.

You’re typing away on your computer, minding your own business when your application freezes. There’s that moment of panic, maybe the software’s just being slow. But no!! Alas, your window unexpectedly closes, your application has crashed. All of us have experienced this unfortunate event….unless you’re NASA.