Possible issue with androidTest dependencies on aar artifacts [36991193]

Fixed

Bug

[AOSP] duplicate

[AOSP] Released

Migrated-Tools-Gradle

Migrated-Tools-Studio

Status Update

No update yet.

Description

xa...@android.com

created issue #1

Mar 8, 2014 01:51AM

Version of the plugin: 0.9.0

How to reproduce
-> Use any AAR dependency with the '"androidTestCompile" scope , like androidTestCompile 'com.jakewharton.espresso:espresso:1.1-r2'

Actual result
-> The java classes are not accessible from the android test source code

When did this bug start happening?
-> I noticed it starting from 0.9.0, might have been present sooner though.

When does the bug occur?
-> Always

Describe any workarounds you have found
-> Change the scope to "compile" solves it but not an appropriate solution

Comments

sk...@gmail.com <sk...@gmail.com> #2Apr 28, 2014 05:53AM

can you share your android studio version

xa...@android.com <xa...@android.com> May 1, 2014 12:55AM

Marked as fixed, reassigned to xa...@android.com.

[Deleted User] <[Deleted User]> #3Jun 9, 2014 09:04AM

Is this happening with Studio 3.0?

pe...@gmail.com <pe...@gmail.com> #4Jun 13, 2014 07:53AM

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]> #5Jun 19, 2014 09:30PM

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)

ja...@gmail.com <ja...@gmail.com> #6Jun 23, 2014 07:23PM

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.

ja...@gmail.com <ja...@gmail.com> #7Jun 23, 2014 07:41PM

The test build works for me on the command line but not in AS 0.6.1, plugin 0.11.2. Adding `provided 'com.example.package'` just above `androidTestCompile 'com.example.package'` fixes the build so that those classes are resolved in AS, but the test build doesn't work at runtime due to other related issues. This particular *.iml file is missing the espresso jars.

ho...@gmail.com <ho...@gmail.com> #8Jun 24, 2014 04:07PM

Same issue here with AS 0.6.1 and gradle 1.12

an...@gmail.com <an...@gmail.com> #9Jul 23, 2014 11:49PM

This issue is still reproducible in AS 0.8.2 and Gradle 0.12.2 - AS can't resolve espresso code imported via double-espresso. Workaround is to add to the provided scope as well.

sk...@gmail.com <sk...@gmail.com> #10Jul 25, 2014 03:18PM

This bug still reproduced in AS 0.8.4 and com.android.tools.build:gradle:0.12.+

sd...@gmail.com <sd...@gmail.com> #11Aug 22, 2014 08:40PM

[Comment deleted]

sd...@gmail.com <sd...@gmail.com> #12Aug 22, 2014 08:43PM

This bug should be reopened, I'm also seeing it in AS 0.8.6 w/Gradle 0.12.2 and com.jakewharton.espresso:espresso:1.1-r3. "Provided" scope does NOT resolve the issue for me.

xa...@android.com <xa...@android.com> Sep 10, 2014 01:28AM

Status: New (reopened)

fo...@gmail.com <fo...@gmail.com> #13Jan 12, 2015 10:47PM

This thing still persist and repeats in Android Studio 1.0 too.

je...@google.com <je...@google.com> Mar 26, 2015 11:58PM

Assigned to cm...@google.com.

xa...@android.com <xa...@android.com> Apr 7, 2015 06:47PM

Reassigned to xa...@android.com.

jo...@gmail.com <jo...@gmail.com> #14Apr 16, 2015 03:32PM

Is there a fix in the works for this soon? Trying to use assertj with androidTestCompile not working correctly.

st...@gmail.com <st...@gmail.com> #15Apr 29, 2015 04:56PM

This is a huge pain.

I've managed to workaround this with the solution described here:

http://stackoverflow.com/a/23305154/2136792

Essentially, for each dependency you mark with androidTestCompile, also mark it provided and your editor will stop complaining.

ro...@gmail.com <ro...@gmail.com> #17Jun 10, 2015 09:58AM

Bug still exists in Android Studio 1.3-PREVIEW 3

rc...@gmail.com <rc...@gmail.com> #18Jul 15, 2015 02:50PM

This issue still exists in AS 1.3 build #AI-141.2024585 using gradle:1.2.3. The weird thing is that the espresso classes were being recognized for a few days and then all of a sudden they are not showing up under my External Dependencies. Can you guys please fix this?!!!

je...@google.com <je...@google.com> Aug 31, 2015 04:40AM

Reassigned to ch...@google.com.

ch...@google.com <ch...@google.com> #19Aug 31, 2015 09:48PM

Marked as fixed.

As far as I can tell, this is fixed in gradle:1.3.1. I am able to reproduce it with gradle 1.2.3, but not 1.3.1. If this is still occurring with gradle 1.3.1 or later, please let me know and provide information on how to reproduced it.

jo...@gmail.com <jo...@gmail.com> #20Sep 2, 2015 06:34PM

Still happening. Will try to build a sample project soon

jo...@gmail.com <jo...@gmail.com> #21Sep 11, 2015 05:22PM

Not happening anymore. I was probably doing someting wacky on my build.gradle.

sz...@gmail.com <sz...@gmail.com> #22Sep 18, 2015 09:52AM

Unfortunately it still happens with gradle 1.3.1, too. Using compile instead of androidTestCompile works. Android Studio 1.3.2.

ja...@gmail.com <ja...@gmail.com> #23Jan 26, 2016 12:25PM

This is still broken using gradle 1.3.1

androidTestCompile 'org.mockito:mockito-core:1.10.19'

pa...@gmail.com <pa...@gmail.com> #24Aug 9, 2016 09:17AM

[Comment deleted]

[Deleted User] <[Deleted User]> #25Aug 15, 2016 09:52PM

I'm currently having this issue with Android Studio 2.1.2. Trying to use espresso classes and for some reason the matcher for "allOF" is not being recognized despite being used in the espresso documentation.

al...@gmail.com <al...@gmail.com> #26Sep 5, 2016 01:33PM

Why is this closed since it's still happening ?

ch...@google.com <ch...@google.com> #27Sep 6, 2016 04:42PM

This bug is considered closed because it wasn't reproducible when it was tested. If it is still happening with the latest version, it is most likely due to a different issue. Please file a new bug with details on how to reproduce the problem, preferably with a sample project.

Issue 36991193

Description

Issue summary

Comments

sk...@gmail.com <sk...@gmail.com> #2Apr 28, 2014 05:53AM

xa...@android.com <xa...@android.com> May 1, 2014 12:55AM

[Deleted User] <[Deleted User]> #3Jun 9, 2014 09:04AM

pe...@gmail.com <pe...@gmail.com> #4Jun 13, 2014 07:53AM

[Deleted User] <[Deleted User]> #5Jun 19, 2014 09:30PM

ja...@gmail.com <ja...@gmail.com> #6Jun 23, 2014 07:23PM

ja...@gmail.com <ja...@gmail.com> #7Jun 23, 2014 07:41PM

ho...@gmail.com <ho...@gmail.com> #8Jun 24, 2014 04:07PM

an...@gmail.com <an...@gmail.com> #9Jul 23, 2014 11:49PM

sk...@gmail.com <sk...@gmail.com> #10Jul 25, 2014 03:18PM

sd...@gmail.com <sd...@gmail.com> #11Aug 22, 2014 08:40PM

sd...@gmail.com <sd...@gmail.com> #12Aug 22, 2014 08:43PM

xa...@android.com <xa...@android.com> Sep 10, 2014 01:28AM

fo...@gmail.com <fo...@gmail.com> #13Jan 12, 2015 10:47PM

je...@google.com <je...@google.com> Mar 26, 2015 11:58PM

xa...@android.com <xa...@android.com> Apr 7, 2015 06:47PM

jo...@gmail.com <jo...@gmail.com> #14Apr 16, 2015 03:32PM

st...@gmail.com <st...@gmail.com> #15Apr 29, 2015 04:56PM

ro...@gmail.com <ro...@gmail.com> #17Jun 10, 2015 09:58AM

rc...@gmail.com <rc...@gmail.com> #18Jul 15, 2015 02:50PM

je...@google.com <je...@google.com> Aug 31, 2015 04:40AM

ch...@google.com <ch...@google.com> #19Aug 31, 2015 09:48PM

jo...@gmail.com <jo...@gmail.com> #20Sep 2, 2015 06:34PM

jo...@gmail.com <jo...@gmail.com> #21Sep 11, 2015 05:22PM

sz...@gmail.com <sz...@gmail.com> #22Sep 18, 2015 09:52AM

ja...@gmail.com <ja...@gmail.com> #23Jan 26, 2016 12:25PM

pa...@gmail.com <pa...@gmail.com> #24Aug 9, 2016 09:17AM

[Deleted User] <[Deleted User]> #25Aug 15, 2016 09:52PM

al...@gmail.com <al...@gmail.com> #26Sep 5, 2016 01:33PM

ch...@google.com <ch...@google.com> #27Sep 6, 2016 04:42PM

Add comment

Issue metadata