Fixed
Status Update
No update yet.
Comments
jo...@gmail.com
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. :)
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. :)
uc...@google.com
rp...@google.com
pa...@gmail.com
I have the same problem.
cj...@cjlights.com
I also have the same problem.
wa...@gmail.com
I also have the same problem.
li...@gmail.com
I also have the same problem.
ju...@google.com
ws...@gmail.com
I also have the same problem.
ju...@google.com
[Deleted User] <[Deleted User]>
Was it fixed reverting to the old behavior, or was it fixed making the deduplication configurable?
What release version will include the fix?
What release version will include the fix?
mo...@gmail.com
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?
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?
ju...@google.com
@jose.aladro.jsc@gmail.com This change in behavior was inadvertent and I reverted it. The fix will go out in 3.2.
lo...@gmail.com
how long before 3.2 is released? or should we just go back to 3.0 while we wait?
ju...@google.com
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.
lo...@gmail.com
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
el...@googlemail.com
got the same behaviour and i dislike it. I would prefer to always see the complete logcat line.
em...@orbyt.me
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.
```
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.
[Deleted User] <[Deleted User]>
Is there an idea on when will version 3.2 be released?
ju...@google.com
The betas are out. I cannot comment on when future stable versions will land, sorry.
so...@gmail.com
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!
I've just spent 4 months of incredible mess cause of this issue!
ju...@braze.com
Shoutout to juancnuno!
[Deleted User] <[Deleted User]>
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
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: Applicationcom.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:
In the other hand, the dedupliaction still occurs in the Debug window. Similar description as in
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
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:
kr...@gmail.com
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...
[Deleted User] <[Deleted User]>
Android Studio 3.2 is finally out, with this issue fixed. Thank you!
ca...@gmail.com
The issue is present in 3.4.2
ju...@google.com
Can you be more specific? This looks good to me.
ri...@gmail.com
Android Studio 3.5.2 still has this 'feature'. Please make a Preference setting to disable it.
b....@group-kd.com
Please make a Preference setting to disable it.
hu...@gmail.com
Comment has been deleted.
Description
- Before AS 3.1, there was no deduplication behavior. Message headers with the same content were present in the logcat window.
- In AS 3.1, this behavior appears to be added. Message headers with the same content get replaced with the 4-space indentation. This results in logs that are incredibly hard to read.
I would appreciate to either revert to the old behavior or a setting where I can disable the deduplication in the window.
Attached are screenshots of the behavior in Android Studio 3.1 and a logcat snippet also from Android Studio 3.1.
Android Studio 3.1
Build #AI-173.4670197, built on March 21, 2018
JRE: 1.8.0_152-release-1024-b01 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.13.3
Reproduced using a Pixel 2 XL on API 27 and on emulator.
Reproduction steps:
1. Open AS logcat window
2. Look for logs that occur at the same time and have the same tag (i.e. same message header)
3. The first log should have the message header present and subsequent lines sharing the same message header will have the message header replaced with a 4-space indentation.