Today we’re excited to announce the launch of Smart Search. We hear all the time from mobile development teams that crash grouping is a constant source of frustration for developers. We think applying Smart Search to crashes is the answer.

Grouping crashes is a delicate matter for two reasons: 1) developers have a different definition of grouping aggressiveness, and 2) there are different ways of grouping crashes as there are more than one question each grouping helps answer. So we have decided to make crash grouping flexible – after all, a crash may be part of more than one group.

Our Apteligent Labs™ Smart Crash Search introduced two new views into your list of issues. Smart Crash Search has been received with great enthusiasm by our customers, and it was time to graduate it to a full-fledged solution.

At launch it offers two new pieces of functionality:
– The ability to identify all the crashes that have the same root cause as the crash at hand – and resolve them as one
– The ability to identify all the crashes that have originated in the same source file as the crash at hand

The successful development and deployment of Lumos, our new data processing platform, has eliminated the restrictions of the old platform, giving us more insight into the data we collect and allowing us to bring this innovative feature to you.

Key features and benefits of Smart Crash Search include:
– Access to more diagnostics information to address the root cause of a problem
– More efficient triage of crashes with decreased noise on the crash summary page
– Fast elimination of bugs not originating in one’s source code

It also helps turn teams from being reactive to proactive. As teams identify crashes that happen in specific files and modules, they can diagnose the health of these modules and schedule preventive actions, future proofing their code and making the application more robust on a go-forward basis.

Here is how it works:

1. Fixing a problem

As you are diagnosing a problem, you can go to Smart Crash Search and find all the crashes that we believe have the same root cause in our system.

This gives you access to granular diagnostic information and accelerates resolution time. You can also easily diff stack traces to quickly tell whether the two crashes are indeed the same.

2. After you have fixed a problem

After you resolve a crash, you can do another Smart Crash Search to resolve in bulk all of the crashes with the same root cause – they will all disappear from your crash summary page as one big resolved group.

3. Assessing the health of a module

You can search for problems that have originated in the same file – you can assign them to the team maintaining this module, find more information about what may be wrong with the module and find out quickly whether the ‘patient’ needs to be admitted. It gives you a good idea of the robustness of this component and you may want to schedule time to make it more robust to prevent crashes in the future.

Crashes can also be grouped with others that originated from the same file

Smart Crash Search is now available to all tiers. We recommend that you look at all of your resolved crashes for the last 30 days and check to see if there are any similar crashes that you have left open. It’s holiday cleaning time!