Fixed
Status Update
Comments
nk...@google.com <nk...@google.com>
sn...@google.com <sn...@google.com> #2
can you share your android studio version
sp...@google.com <sp...@google.com> #3
Is this happening with Studio 3.0?
nk...@google.com <nk...@google.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).
sn...@google.com <sn...@google.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)
jo...@google.com <jo...@google.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.
jo...@google.com <jo...@google.com> #7
BTW Mine occurred in 2.3.3 and I can't record any espresso tests (they all fail).
Description
Version used: 2.2.2
What steps will reproduce the problem?
See
How are you running your tests (via Android Studio, Gradle, adb, etc.)?
Android Studio
What is the expected output? What do you see instead?
See
For analysis and a proposed solution see