Welcome to our series of blog posts about all the nitty-gritty details that go into building a great debug experience at scale. Today, we’re looking at Symbolicator, the service that processes all native crash reports and minidumps at Sentry.
Over a year ago, we first announced support for Minidumps in Sentry, which allows you to debug crashes from applications written in languages like C, C++, Objective-C and more — regardless of whether you’re targeting Windows, macOS, Linux, iOS, or Android.
Ever since we started logging with Bugfender back in 2015, we’ve been working towards integration with Firebase, the app development platform created by Google. Firebase is famous for the breadth of its integration libraries and millions of people use the product around the world, drawn to its sleek UI and range of features.
How do you evaluate the cost of building and maintaining your own crash reporting solution?
If used correctly crash reporting will improve your teams technical support abilities while decreasing time spent on individual issues.
When your job is to launch rockets into space, even the smallest error in your code can be catastrophic. Here's how NASA keeps their software from crashing.
As we build Crashlytics and talk to our developers, we've found that the way they use our dashboards is often nuanced and specific to their team. We've done our best to incorporate the themes we hear most often into the dashboard you see in the Firebase console, but one dashboard solution simply isn't enough.
In this tutorial, we’ll debug an iOS application with Apple’s Xcode. Xcode is a robust environment for developing and troubleshooting iOS applications. We’ll see how we can use it, alongside Raygun’s iOS Crash Reporting, to quickly address an application deficiency.