You'll probably use this one most frequently out of all available Log methods. As you might imagine, you'll use this one for debugging purposes. For instance, maybe you want to double-check a method is being called successfully, you could print an informational message to the log reading something like 'X method called!'. Developers usually use this to proactively investigate unusual or unexpected behavior in an application. Use this when you suspect an issue may be occurring, but haven't yet received full-on error messages. The Log.e() message can then print details about the error. Developers will commonly use this in a block of code meant to catch an error. Use this when you know an error has occurred, and you're logging details about that error.

Let's briefly cover what these different methods are, and when to use each: Log.e()

However, unlike JavaScript's console.log(), there are many different methods from Android's Log class we can use to log information. It both displays messages in real time and also keeps a history so you may view older messages.Īfter placing Log methods we can run our app and look view the logcat to see what data or information has been recorded. The logcat displays system messages, and messages/information you manually record with Log methods. We can add log methods that will write data to Android Studio's logcat. This allows us to see what certain variables are defined as, or check whether methods are being called.Īndroid Studio has the capability to write log messages in a very similar manner. It’s a method that allows us to write to the JavaScript console in the browser.

When writing JavaScript in your Intro to Programming and JavaScript courses, you probably encountered console.log(). Then, in the next lesson we'll learn how to add breakpoints to strategically pause our code and narrow down where bugs and errors are occurring. First, we'll learn how to record helpful information into an area of Android Studio known as the logcat.

In the next two lessons we'll explore two Android-specific approaches to debugging. Bugs occur all the time, and that's simply a normal part of development. Sometimes code that once worked perfectly no longer functions after implementing new code. Sometimes code doesn't work on the first try. Now that you're in your level 3 Epicodus course, you've probably come to realize how much trial-and-error goes into coding.

Android studio logcat not filtering