IssueTracker

I just attached a minimal test application with duplicated and multiline traces. Provided are a couple of logcat files and screenshots.

To me this isn'r really a big problem, since AS compiles my application and lets me debug it. That's what I use it for in my company. I just found it a bit annoying that something that worked one way in AS 2.x and 3.0, suddenly changed in 3.1.  The new way results more time-consuming to me while debugging and reviewing the logs.

Could this be made configurable? Not necessarily in the UI, but editing some properties file. Thanks. :)

I have the same problem.

I also have the same problem.

I also have the same problem.

I also have the same problem.

I also have the same problem.

Was it fixed reverting to the old behavior, or was it fixed making the deduplication configurable?
What release version will include the fix?

I still have the same problem on my version.
Android Studio 3.1.1
Build #AI-173.4697961, built on April 4, 2018
JRE: 1.8.0_152-release-1024-b02 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 8.1 6.3

Screenshot attached.
Is there any way to customize this kind of behavior?

@jose.aladro.jsc@gmail.com This change in behavior was inadvertent and I reverted it. The fix will go out in 3.2.

how long before 3.2 is released?  or should we just go back to 3.0 while we wait?

The fix will go out in 3.2 Canary 13 (we're at 11 now). If you're willing to put up with some instability use the canaries. I can't comment on when future stable versions will land.

canaries defeat the whole idea of wanting a bug fix.  I'd get this bug fix plus I'll gain 50 new bugs, so no thanks.  guess it's back to 3.0 since you say you aint gonna fix this in an update to 3.1

got the same behaviour and i dislike it. I would prefer to always see the complete logcat line.

I was preparing to submit a similar issue before coming across this one. Along with the problem originally described, I've noticed that the current version seems to be unable to properly filter logcat. For example, given the following log:

```
05-15 17:04:26.219 000-000/com.example.debug D/testing: onViewRecycled: CardAndTextViewHolder
    onViewRecycled: SubtitleViewHolder
    onViewRecycled: HeaderViewHolder
    onBindViewHolder: 0
```
Each log statement here has the same tag ("testing"). If the term "onViewRecycled" is applied to the logcat filter, the line containing "onBindViewHolder: 0" (line 4) should not be shown, but it is. I assume this and the original issue are both caused by the same bug, and if so, should be fixed in an upcoming version as mentioned above.

Is there an idea on when will version 3.2 be released?

The betas are out. I cannot comment on when future stable versions will land, sorry.

Thanks god 3.2 beta is finally out and it's fixed!!!

I've just spent 4 months of incredible mess cause of this issue!

Shoutout to juancnuno!

I'm trying the new 3.2 beta and yes, the deduplication no longer occurs in the logcat window. Thanks! I'm eagerly waiting for the 3.2 final version to come out.

In the other hand, the dedupliaction still occurs in the Debug window. Similar description as in Comment #1 above:

In the Android Studio debug window, logs that have the same message header (the "W/MainActivity: " part of a message), have the message header deduplicated in logs. Instead of duplicating the logs, a 4-space indentation is instead present.

W/ActivityThread: Application com.example.app is waiting for the debugger on port 8100...
I/System.out: Debugger has connected
____waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
I/System.out: debugger has settled (1386)

(spaces displayed as underscores for readability)

Please move this message to a new debug-window related thread if appropriate. Here are some screenshots:

Great, thanks. I hope it is possible to revert to Android Studio 3.0, just for a time until 3.2 comes. As this LogCat bug is a show stopper for me...

Android Studio 3.2 is finally out, with this issue fixed. Thank you!

The issue is present in 3.4.2

I'll take a look

Can you be more specific? This looks good to me.

Android Studio 3.5.2 still has this 'feature'. Please make a Preference setting to disable it.

Please make a Preference setting to disable it.

@26 Here, for a new project, that chose "project", it still occur.

I updated to 3.6.2 earlier today, all fresh and excited to start a new project. Now I'm barely holding my eyelids open, after finally figuring out why the sample navigation drawer activity template was not switching the fragments. Definitely not fixed. Hopefully I will get something useful done tomorrow.

Android Studio 3.6.2
Build #AI-192.7142.36.36.6308749, built on March 19, 2020
Runtime version: 1.8.0_212-release-1586-b4-5784211 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 5.3.11-200.fc30.x86_64
GC: ParNew, ConcurrentMarkSweep
Memory: 1246M
Cores: 4
Registry: ide.new.welcome.screen.force=true
Non-Bundled Plugins:

Even when I don't see this issue, I still see Kotlin formatting issues. It keeps formatting in a way that likes word-wrapping too much.