Development issue/problem:

Since the AS 1.1 Preview 2 update I get red lines under all my log messages.

Log.d(TAG, Message) ;

With a message: The logbook can contain up to 23 characters….

Basically I haven’t updated anything but Android Studio itself. Is this a mistake?

How can I solve this problem?

Solution 1:

No, it’s not a mistake.

From the latest version of Android Studio goes to version 1.1 Preview 2,

Checks that the tag passed to the log call, if its value can be resolved, does not exceed 23 characters (as required by the Log API).

As briefly explained in the latest changes, this is due to the fact that the protocol API does not allow tags of more than 23 characters.

SLF4J Android has an explanation for this:

…] the length of these labels is currently limited to 23 characters (23 = 32 – 8 for the name space prefix – 1 for the end point C).

that matches the Android source code.

Currently, the only feature that explicitly mentions this exception is Log.isLoggable(),

IllegalArgumentException is launched as tag.length() > 23.

However, the notes show that the logger makes an exception in release mode (it is ignored in debug mode).

You can disable the fluff control like Terence does in his answer, but you’ve been warned.

Solution 2:

You can turn it off if you want.

In Android Studio, Analysis -> Validation Code.

Under Audit Profile, click on the button with the 3 horizontal dots.

The next window should open. Find the newspaper and erase the log labels for too long.

The logging tag can be at most 23 characters –

Update : Android Studio 2.2, it is located under Android Ribbon : Correction

The logging tag can be at most 23 characters –

Solution 3:

Addendum to @Terence’s reply

You can also disable a specific check by sorting it in your build.gradle:

ribbonOptions {
Disable LongLogTag

Or by adding the ribbon.xml file with xml to your :

Solution 4:

You can never ignore this check, it can certainly cause unexpected results on your output version because it throws exceptions and stops execution (it will not crash your application).

I learned a terrible lesson the other day: In debug mode everything is fine, but in the output version everything behaves differently.

Solution No 5:

It’s a new change, and in this building it’s a new battery test. And that means

Checks that the tag passed to the log call, if its value can be resolved, does not exceed 23 characters (as required by the Log API).

For more information you can read point 3 under the link.

If you don’t want to, minimize the number of characters on your label and make sure they don’t exceed 23.

Solution No 6:

To explain why this is happening:

Depending on the AOSP source code, you can connect to any label. The problem is Log.isLoggable.

Log.isLoggable checks the system property log.tag. if the priority to log is enabled. You will find the documentation relating to this mechanism here:

public static boolean isLoggable (String tag, int level)
Checks whether the log of the specified tag can be recorded at the specified level. The default level of each beacon is set to INFO. This means that each level above and including INFO is recorded. Before invoking the logging method, check if you want your tag to be logged. You can change the default level by setting the system property: setprop log.tag. When the level is either VERBOS, DEBUG, INFO, WARNING, ERROR, ASSISTANCE or SUPPRESS. SUPPRESS disables the registration of your label. You can also create a local.prop file with: log.tag.= and place it in /data/local.prop.


Under API 26 (Oreo), the limit for system property keys was 31 characters. And log.tag…length() + 23 equals 31. If you call Log.isLoggable on Android Oreo with a tag longer than 23 characters, it will fall as described in the source code. Since Android O this restriction no longer applies.

The plush rule only exists to protect you from all these (mostly) useless details.

Log.isLoggable’s documentation also states that the IllegitimateArgumentException is not thrown because API 24, which I know is wrong. Under:

Solution No 7:

Decision year 2020 ver.

build.gradle (app)

android {
lintOptions {
disable LongLogTag
} // Set this.

Solution No 8:

This error message was given to me for the library node_module complaining about the separate library node_mode.

I added this ribbon options property to the node_module build file of the gradle library.

android {
lintOptions {
abortOnError false

The library was an advanced push notification.

The :@aws-amplify/pushnotification:ribbon job failed.

Updated file: node_modules/@aws-amplify/pushnotification/android/build.gradle

Good luck!

log.d android studio,android logging best practices,android logging library,what is log output level samsung,fungsi log e android studio,logging support to android application,log isloggable,log getstacktracestring,log assert,log_tag,verbose logging android,android logger,android log exception

You May Also Like

4 Browsers that are Super Awesome

Facebook Twitter Pinterest Reddit Messenger WhatsApp Xbox One supports a wide range…

URBN Power Bank Review, Made In India Power Bank, 18W, QC 3.0 + PD

The Indian smartphone accessory brand URBN has recently launched its latest thin…

What You Need to Do If You See a Netflix VPN Error

A global pandemic changed millions of lives in a few months. Many…

How To Activate Microsoft Office 2010 Permanently 2021

How to permanently activate Microsoft Office 2010 – Who doesn’t know MS…