Obsolete
Status Update
No update yet.
Comments
sb...@google.com
xa...@android.com
cm...@google.com
cy...@gmail.com
can you share your android studio version
su...@gmail.com
Is this happening with Studio 3.0?
ma...@gmail.com
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).
[Deleted User] <[Deleted User]>
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)
hu...@google.com
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.
Description
OS version: Linux OpenSuse 12.3
Java JRE/JDK version: java version "1.7.0_21"
Java(TM) SE Runtime Environment (build 1.7.0_21-b11)
Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode)
Running unit tests with gradle connectedCheck works OK. However I would like to change the behavior:
- do not start the test run on _all_ connected devices by default, this should be an option. Usually one runs tests on one device to check a specific problem. It also takes more time to runs tests on all devices.
- the gradle process to run tests seems to uninstall the package under test, then installs the package again with the tests and runs it. This is a major difference from running tests via Eclipse. The Eclipse procedure does not uninstall the package but updates the APKs and runs the instrumented tests. Uninstalling a package results in loss of data (probably some production data). Test package usually create/use their own temporary data to run the tests, thus no reason the clean the whole package. This problem together with the "start on all connected devices" may lead to unexpected behavior and loss of data.