Fixed
Status Update
No update yet.
Comments
uc...@google.com
so...@google.com
Hey thanks for reporting! We're just starting to dig into this.
Can you run
$ adb version
and also
$ which adb
Can you run
$ adb version
and also
$ which adb
xo...@google.com
$ adb version
Android Debug Bridge version 1.0.31
$ which adb
/usr/bin/adb
BTW - "adb kill-server" also does the job, so it's really the server restart, not "adb logcat" that kicks off logging in AS again.
Android Debug Bridge version 1.0.31
$ which adb
/usr/bin/adb
BTW - "adb kill-server" also does the job, so it's really the server restart, not "adb logcat" that kicks off logging in AS again.
xo...@google.com
Thanks for the report. I've fixed the lint warning, which should no longer trigger for attempts to assign ext.minSdkVersion no matter which syntactic form is used for it; this fix should appear in Arctic Fox beta whenever that's released. Earlier versions will continue to have the erroneous warning, for which the workaround of assigning it in an explicit ext block should work.
Description
AI-181.4668.68.32.4763614, JRE 1.8.0_152-release-1136-b02x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.12.6 unknown, screens 2560x1440, 1680x1050; Retina
Android Gradle Plugin: 3.1.2
Gradle: 4.4
NDK: from local.properties: (not specified); latest from SDK: (not found);
LLDB: pinned revision 3.1 not found; latest from SDK: (package not found);
CMake: from local.properties: (not specified); latest from SDK: (not found); from PATH: (not found);
when assigning a variable via the `buildScript.ext.` space, Studio complains if the name matches the SDK. This is used in a multi-module project to easily share the same SDK versions around and update accordingly.