# How-to not clear the logcat on a crash

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.

* * *

![edit-filter-configuration.png](https://cdn.hashnode.com/res/hashnode/image/upload/v1643633231582/6yWP4WM1E.png)

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.

![create-new-logcat-filter.png](https://cdn.hashnode.com/res/hashnode/image/upload/v1643633184227/avAMsVTFN.png)

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!