Test module fails to run in studio, succeeds from cmd line [127662898]

Verified

Bug

Status Update

No update yet.

Description

cc...@google.com

created issue #1

Mar 6, 2019 06:58PM

Build: AI-183.5429.30.35.5326993, 201902211332, AI-183.5429.30.35.5326993, JRE 1.8.0_152-release-1343-b16-5323222x64 JetBrains s.r.o, OS Linux(amd64) v4.19.12-1rodete1-amd64, screens 2560x1600, 1920x1200AS: 3.5 Canary 6; Android Gradle Plugin: 3.5.0-alpha06; Gradle: 5.2.1; NDK: from local.properties: 15.0.4075724, latest from SDK: 15.0.4075724; LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: /usr/local/google/sdk/cmake/3.6.3155560/bin/cmake -version/usr/local/google/sdk/cmake/3.6.3155560/bin/cmake: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory, from PATH: (not found) IMPORTANT: Please read

https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

./gradlew clean
./gradlew test:cC

test runs fine, but running from studio, we've seen two problems, either it prints:

Cause: cannot find main APK

Or we've also seen an error where it tries to run the test with Android stubs on the host, and hits an exception when it can't find Log.e()

I haven't been able to reproduce this with a truly minimal sample project, but it's reliable with this one - Dustin and I have both reproduced this.

TestModuleFailsInStudio.zip

3.4 MB

Download

Comments

cc...@google.com <cc...@google.com> #2Mar 6, 2019 07:20PM

We use build flavours heavily with a lot of common code. The refactoring support in AS is really good but it continually catches us out when it doesn't work across all flavours in a project. It's a big gap for serious product development.

ar...@google.com <ar...@google.com> Apr 25, 2019 10:32PM

Assigned to hu...@google.com.

hu...@google.com <hu...@google.com> #3Apr 30, 2019 08:56PM

Accepted by hu...@google.com.

We at my company need this same feature. We have a lot of white labels and need refactor the same class across flavours. :(

hu...@google.com <hu...@google.com> #4May 3, 2019 01:54AM

I need this feature too...

hu...@google.com <hu...@google.com> #5May 6, 2019 08:10PM

+1, I need this very badly

be...@google.com <be...@google.com> #6May 7, 2019 09:14AM

+1 My company also need this feature.

hu...@google.com <hu...@google.com> May 23, 2019 10:27PM

Marked as fixed.

rs...@google.com <rs...@google.com> #7Nov 23, 2019 12:21AM

Can we atleast know the status of the issue please? Will it be fixed or is it in low priority. It's been 4 years.

Message last modified on Nov 23, 2019 12:27AM

hu...@google.com <hu...@google.com> Nov 23, 2019 01:05AM

Status: Assigned (reopened)

hu...@google.com <hu...@google.com> #8Nov 26, 2019 10:26PM

We are currently investigating possibly solutions.

hu...@google.com <hu...@google.com> #9Jan 3, 2020 01:09AM

Verified by hu...@google.com.

+1 This will exclude a lot of unnecessary work. In my work I have 25 flavours. :(