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.