Status Update
Comments
xa...@android.com <xa...@android.com>
ja...@gmail.com <ja...@gmail.com> #2
can you share your android studio version
ja...@gmail.com <ja...@gmail.com> #3
Is this happening with Studio 3.0?
xa...@android.com <xa...@android.com>
pj...@pj-co.com <pj...@pj-co.com> #4
Note: This worked for me on Windows 7 Pro 32-bit (with Android Studio 2.3.3). Seems like an issue with adt-branding module (which should contain the "/idea/AndroidStudioApplicationInfo.xml" resource).
wz...@gmail.com <wz...@gmail.com> #5
Hi, also happened on Mac Book Pro 15 retina mi-2015
MacOs Sierra 10.12.6
Android Studio 2.3.3
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
MacOs Sierra 10.12.6
Android Studio 2.3.3
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
ni...@gmail.com <ni...@gmail.com> #6
Thank you for this feedback. Your feedback helps make sure Android development tools are great! Given your issues has been resolved I am closing this issue.
he...@gmail.com <he...@gmail.com> #7
Why not exclude the transitive dependency?
ja...@gmail.com <ja...@gmail.com> #8
Because that would be the job of the build system. Hence the bug report!
xa...@android.com <xa...@android.com> #9
This is fixed in 1.1
Description
For example, App1 depends on Lib1 which depends on Guava. App1's instrumentation tests depends on Lib2 which also depends on Guava. If there were no Lib1 dependency, Guava still needs to be included in the test APK for Lib2 to use it.
The tooling needs to detect dependencies in the instrumentation test scope which duplicate that of the compile scope and demote them to being provided.