Android builders all internationally depend on Firebase Crashlytics to floor detailed insights and context into the occasions resulting in a crash. Crashlytics provides you a whole view into your app’s stability — serving to you monitor, prioritize, and repair essential points earlier than they influence a lot of customers.
Nevertheless, even with detailed and real-time crash stories, troubleshooting often requires you to leap between the Crashlytics console and your codebase to find the error. Taking a look at stack traces in a browser after which having to navigate by your supply code to seek out the best place to set your breakpoints is mentally taxing and will be irritating. And it’s simple to overlook new stories when you’re not recurrently checking the Firebase Console.
That’s why Android Studio Electrical Eel introduces the brand new App High quality Insights window, which helps you uncover, examine, and reproduce points reported by Crashlytics multi functional place and throughout the context of your native Android Studio undertaking.
Should you’re already utilizing Crashlytics in your app undertaking, getting began with App High quality Insights solely requires a number of clicks. All it’s a must to do is be sure to’re logging into Android Studio with the identical Google Developer account you utilize to entry Firebase Crashlytics for this undertaking. To log in, open the App High quality Insights window by navigating to View -> Software Home windows -> App High quality Insights , click on the Log in hyperlink, and comply with the prompts.
Should you’re not utilizing Crashlytics in your undertaking but, you are able to do so by following these directions.
When you’re logged in, navigate to the App High quality Insights window in Android Studio. The IDE then downloads the most recent crash information on your app, sorted by people who happen most continuously.
Once you click on on a particular problem, detailed data is proven together with the pattern stack hint, affected units, and affected Android variations.
1: Present particulars concerning the newest incidence of the occasion you click on. You possibly can see the occasion’s stack hint and click on on the stack hint to leap to the related strains in your code base.
2: Break down the crash counts by machine sort.
3: Break down the crash counts by Android model. Together with the crash counts by machine sort, you’ll be able to decide which person teams are most affected.
With the App High quality Insights window you’ll be able to leap from the crash report back to the related line of code, which resolves the most important friction when triaging crash stories.
Notice: As a result of the IDE navigates to the precise file and line quantity indicated within the stack hint, if there have been latest code modifications between your present checkout and the model of the app that prompted the crash, the IDE may not precisely navigate to the related strains of code.
Moreover, when you’re already within the code editor, the gutter on the left reveals a crash icon on the related strains of code which have the corresponding crash report. Clicking the crash icon opens the detailed report pane, which lets you leap between the crash stories to the code seamlessly.
The next filters enable you slim down the checklist of crash stories to those you care about most.
In case your undertaking contains a number of app modules, be sure that the module you need to see points for is chosen from the module dropdown menu.
Choose or deselect the icon to toggle the visibility of the crash stories relying on the severity, deadly ❌ or non-fatal ⚠️.
To view solely stories with crashes which have occurred not too long ago, you should utilize the dropdown to pick the specified timeframe, corresponding to “7 days” or “30 days”. This lets you see crashes which can be comparatively new or are at the moment affecting your customers. Setting a special worth additionally updates person and occasion counts throughout the instrument to replicate the chosen timeframe.
Lastly, when you’ve not too long ago launched a brand new model of your app to manufacturing, and also you solely need to see the most recent crashes that have an effect on that launch, you should utilize the App model selector to pick a number of variations of your app that you just need to see crash stories for.
Should you use the preview model of Android Studio, you’ll be able to strive the brand new options added in Android Studio Flamingo (now in Beta) that can assist you troubleshoot the reason for the crashes extra successfully and make it simpler to collaborate together with your colleagues.
Viewing and enhancing notes
Now you can view and fix notes to points instantly from the IDE. These notes will be considered by different workforce members who even have entry to the Crashlytics undertaking, in order that the progress of an investigation will be shared throughout the workforce.
Open/Shut the problem from Android Studio
Should you’ve uploaded a repair to a tough problem, let everybody know by closing the problem instantly from Android Studio by clicking the Shut motion! This lets your teammates know that they’ll give attention to fixing different points.
Remember, once you refresh the App High quality Insights window after closing a problem, these points are not seen in Android Studio and you must navigate to Crashlytics console to view the closed points.
Should you shut a problem by mistake, merely click on the motion to Undo shut.
Android Studio Flamingo provides the next further filters to slim down the crash stories at a extra granular stage.
Alerts
You possibly can filter the problems by Crashlytics alerts. Alerts are connected to points which have sure traits. For instance:
- Early: Points with a excessive share of occasions throughout the first 5 seconds of a person’s session
- Contemporary: New points that appeared within the final 7 days
- Regressed: Points which have re-occurred and we’ve re-opened
- Repetitive: Points with occasions that occurred a number of occasions per person
System
Investigating points can generally require understanding patterns, corresponding to sure crashes occurring on particular OEMs or machine fashions. Now, you’ll be able to filter crash stories by a number of OEMs and particular machine fashions.
Working system model
Equally, chances are you’ll need to establish if sure points are associated to a particular platform model. For instance, one which has launched habits modifications your app isn’t correctly dealing with. Now you’ll be able to filter points by particular Android platform variations.
As well as, filters with plenty of choices at the moment are searchable so you’ll be able to customise your view quicker, with out scrolling by all of the menu choices.
Troubleshooting crash stories is a vital a part of the event life cycle, which helps to ship a greater person expertise together with your app. We will’t wait so that you can strive the App High quality Insights window and listen to what you consider it.
Be sure that to additionally take a look at the documentation concerning the App High quality Insights window for the entire checklist of obtainable options.
As at all times, when you discover any points or suggestions, don’t hesitate to file a problem on our problem tracker.
Completely satisfied coding!
