Fixed
Status Update
Comments
kd...@google.com <kd...@google.com>
pa...@google.com <pa...@google.com>
an...@nrk.no <an...@nrk.no> #2
It's been almost a month now. Is it really that hard to fix? Or has it already been fixed?
pa...@google.com <pa...@google.com> #3
Unfortunately, this is not as trivial as it may seem.
Logcat tool has a memory-saving feature that kicks in when you close the Logcat tool. When the tool is closed, we disconnect from the device, save the contents of the panel to a disk file and clear the panel. When you open the panel again, we reload the contents from the file and reconnect to the device.
The code right now doesn't handle the state of the scroll-to-end
toggle.
It's possible to do but it's tricky.
In the meantime, if you care more about preserving the scroll-to-end
state than memory usage, you can disable the feature by adding this to your custom VM options:
-Dlogcat.panel.memory.saver=false
sp...@google.com <sp...@google.com>
sp...@google.com <sp...@google.com> #4
My computer has had 64GB of RAM for a long time. You should put this setting in the Logcat settings.
And fix this bug! Don't tell me programming is hard for you! You are programmers and should solve any problem!
And fix this bug! Don't tell me programming is hard for you! You are programmers and should solve any problem!
an...@nrk.no <an...@nrk.no> #5
If it's hard to fix bugs, then stop updates and only do bug fixes.
an...@google.com <an...@google.com> #6
And this setting doesn't fix all the logcat bugs. Fix them at least!
-Dlogcat.panel.memory.saver=false
-Dlogcat.panel.memory.saver=false
Description
Describe the bug or issue that you're seeing.
We have a project with multiple modules using here . This seems to build just fine when for instance building a regular APK, but linting fails.
apply plugin: 'com.android.library'
. One of these modules (calledanalytics
) needs to use an external AAR file. We have tried to set it up as describedFor instance when we run
lintDebug
we get this error:We don't need the modules to be built as AAR-files, in the end they'll just be part of the final app. But then we assume there's either something missing in the documentation, there is an error with the linting or that we are missing some setup.
A similar issue has been discussed on StackOverflow , but that's for modules that are going to be used as actual libraries in the end - and they are refering to an old method that I guess aren't recommended anymore?
Attach log files from Android Studio
As this most likely isn't an issue with Android Studio (I just weren't allowed to create the issue anywhere else) I don't think this is needed - but let me know if it is!
If you know what they are, write the steps to reproduce:
implementation files(...)
with an AAR-filelintDebug
task or something alike itAdditional information