How-to not clear the logcat on a crash

A quick and simple Android Studio trick

UpdatedFebruary 3, 2022

Android Developer working at the Dutch Railways (Nederlandse Spoorwegen) who is passionate about mobile development and always eager to learn. I'm focused on creating a Design System using Jetpack Compose and working on an engaging city walk app for exploring new places. With a strong command of Java and Kotlin, I thrive on staying up-to-date with the latest advancements in Android technology. My goal is to build innovative and user-centric solutions that enhance the overall user experience. Beyond coding, I enjoy immersing myself in nature, capturing scenic views through my camera lens, and indulging in a good book.

Comments

Join the discussion

No comments yet. Be the first to comment.

More from this blog

An Introduction to Paparazzi for Snapshot Testing

Using Jetpack Compose

Aug 3, 20235 min read

An Introduction to Paparazzi for Snapshot Testing

10 Tips to stay a Happy Developer

As a developer, it's easy to get caught up in the daily grind of writing code, fixing bugs, and meeting deadlines. It's important to remember, however, that being a happy and fulfilled developer is just as important as being a competent one. Here are...

Jan 4, 20233 min read

Android Jetifier — Can we say Bye-Bye yet

Bye Bye or What?

Nov 10, 20211 min read

Android Jetifier — Can we say Bye-Bye yet

Gson using AutoValue and Polymorphism

The problem and solution explained

May 19, 20183 min read

Random Thoughts

5 posts

Android Developer working at the Dutch Railways (Nederlandse Spoorwegen) who is passionate about mobile development and always eager to learn.

It is already annoying that your app crashes. But even more so when you can’t find the crash in the logcat due to the app restarting on either the emulator or a physical device.

Luckily, there is a very simple and quick solution for this, it stops Android Studio from clearing the logcat which means you can stop trying to reproduce it multiple times or are forced to use the command line. You can just start fixing the actual error instead.

It only consists of two steps, first open the logcat window in your Android Studio if it’s not already there. On the top right, you see the filters dropdown. Open this and select Edit Filter Configuration.

In the Create New Logcat Filter window fill in the Package Name of your application. In my case, it is eu.walkthecity. You can fill in anything you want in Filter Name but I would recommend putting the name of your application there so you can easily find it back if you’re working on multiple apps.

The Log Level can be set to anything you want as crashes are always reported as Error. I used Verbose so I can just leave this filter on when looking for my debug messages as well.

Voila, you’re done. Simple right? Now back to more important stuff and get those amazing apps out there!

Command Palette

Comments

More from this blog