Espresso missing guava dependency [65486414]

Fixed

Bug

[AOSP] mac

Status Update

No update yet.

Description

ro...@gmail.com

created issue #1

Sep 8, 2017 06:39PM

IMPORTANT: Please read

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

Studio Build:
Version of Gradle Plugin: 162.2228.14
Version of Gradle: 3.3
Version of Java: 1.8.0_73 (Oracle Corporation 25.73-b02)
OS: Mac OS X 10.12.6 x86_64

Steps to Reproduce:
1. Make an Android project
2. Install Espresso
3. Add the following to build.gradle:
androidTestCompile 'com.android.support.test.espresso:espresso-core:3.0.1', {
exclude group: 'com.android.support', module: 'support-annotations'
}
androidTestCompile 'com.android.support.test.uiautomator:uiautomator-v18:2.1.1'
androidTestCompile 'com.android.support.test.espresso:espresso-web:3.0.1'
androidTestCompile 'com.android.support.test.espresso:espresso-accessibility:3.0.1'
androidTestCompile 'com.android.support.test.espresso:espresso-contrib:3.0.1'
androidTestCompile 'com.android.support.test:runner:1.0.0'
androidTestCompile 'com.android.support.test:rules:1.0.0'
androidTestCompile "org.jetbrains.kotlin:kotlin-stdlib-jre7:$kotlin_version"
androidTestCompile "org.jetbrains.kotlin:kotlin-test-junit:$kotlin_version"
4. Create espresso test
5. Enable AccessibilityChecks by

https://developer.android.com/training/testing/espresso/accessibility-checking.html
Example (in kotlin):
companion object {
@BeforeClass @JvmStatic
fun enableAccessibilityChecks() {
AccessibilityChecks.enable()
}
}
6. Run Tests

It will say: "Empty test suite."
See:

https://stackoverflow.com/questions/46097973/android-espresso-accessibility-check-failing

To Fix:
I had to add androidTestCompile 'com.google.guava:guava:20.0' to the app gradle file.

Comments

uc...@google.com <uc...@google.com> Sep 12, 2017 07:28PM

Assigned to sn...@google.com.

sn...@google.com <sn...@google.com> #2Sep 13, 2017 05:31PM

Reassigned to uc...@google.com.

I have also seen this issue, careful analysis has shown it appears to be related to the canary version of the caf_receiver framework.

In debug mode you will see: Load failed: cast.o.media.Il.create is not a function

This function appears to be missing in

https://www.gstatic.com/cast/sdk/libs/caf_receiver/canary/cast_receiver_framework.js, the code in the non-canary framework, located at

https://www.gstatic.com/cast/sdk/libs/caf_receiver/v3/cast_receiver_framework.js doesn't have this issue.

uc...@google.com <uc...@google.com> Sep 13, 2017 09:18PM

Reassigned to xa...@google.com.

je...@google.com <je...@google.com> Sep 15, 2017 09:45PM

Reassigned to hu...@google.com.

hu...@google.com <hu...@google.com> #3Sep 17, 2017 12:23AM

I'm having this issue with 1 of my 3 Chromecasts and actually bought a new Chromecast because I thought it was broken.

ja...@gmail.com <ja...@gmail.com> #4Nov 29, 2017 07:04PM

Hi There,

I am also experiencing this issue. I have 9 chromecasts V3, all bought at the same time and on 2 of them I was not able to cast images using either the
default or styled media reciever.
When comparing the debugs of a working and non working device I found that the non working one is using the canary framework instead of the V3

First of all i checked and this device doesn't have the Preview program on, how come it gets beta code ?

The error is as stated above on the cast.o.media.Il.create function

Non working canary
c = c.startsWith("image/") ? cast.o.media.Il.create(b) : .L(new hu(b,ku))

Working V3
c = c.startsWith("image/") ? .K(new ot(b)) : _.K(new Nt(b,Qt))

ja...@gmail.com <ja...@gmail.com> #5Nov 29, 2017 07:41PM

Thanks for reporting the issue. We will investigate further and get back to you with our findings.

ja...@gmail.com <ja...@gmail.com> #6Nov 29, 2017 08:19PM

Thanks for reporting the issue. We will investigate further and get back to you with our findings.

Can you also confirm whether this is happening with our latest version? You can try the preview URL that can be found here:

https://developers.google.com/cast/preview-url

hu...@google.com <hu...@google.com> #7Dec 7, 2017 06:11PM

Reassigned to sl...@google.com.

Hello,

So I created a custom reciever app pointing to the preview cast reciever version and I have the same error

https://www.gstatic.com/cast/sdk/libs/caf_receiver/preview/cast_receiver_framework.js
It looks like the bug is also present in the preview version.

The problem I have is even if I specify to use the v3 cast reciever (

https://www.gstatic.com/cast/sdk/libs/caf_receiver/v3/cast_receiver_framework.js) in my custom reciver app in the debbugs is see the chromecast using the canary library (

https://www.gstatic.com/cast/sdk/libs/caf_receiver/canary/cast_receiver_framework.js) ... Why?

Why this chromecast in particular has this behavior ?
serial number is: 1125ADSFDMJ

Is there another version of the cast_receiver_framework.js that i could use ?

Thanks,

hu...@google.com <hu...@google.com> #8Dec 7, 2017 06:14PM

Can you please confirm if this preview version is the same one announced on [Feb 10th (https://groups.google.com/g/cast-sdk-announcements/c/-dLdTPHTvDc) that is now in canary testing?

There are disconnects between the dates in the announcement channel and the release notes this year, alignment seems to be be better in Nov/Dec last year.

ja...@gmail.com <ja...@gmail.com> #9Dec 7, 2017 11:57PM

Hello,

The SDK version is CAST SDK CAF Version: 3.0.0095 the shaka player loaded is 3.0.10. So apparently not the same as the one announced on Feb 10th (3.0.8).
I attached the whole debug output with the preview framework (

https://www.gstatic.com/cast/sdk/libs/caf_receiver/preview/cast_receiver_framework.js)

How come some devices use canary and some do not ?

Thanks,

Joris

sl...@google.com <sl...@google.com> #10Dec 8, 2017 06:10PM

Marked as fixed.

To answer your questions, as we roll out the releases, some devices will see the new release (canary) and others will see the old release until the new release is fully ramped up in production. In Feb we found an issue with Shaka player version 3.0.8 which was fixed in version 3.0.10. We delayed the rollout of the receiver release to get the updated Shaka player 3.0.10 into the release, and that's what's currently in canary (and in preview). (The preview URL will always point to the newest build about to be released.)

For the cssting photos bug reported here, engineering has implemented a fix, and we hope to update the release with the fix tomorrow. We'll do our best to update this bug as soon as the fix is in canary.

ja...@gmail.com <ja...@gmail.com> #11Dec 8, 2017 06:56PM

We're in the process of updating the preview URL with the fix, which should be in place in an hour or so. Joris or John, once that's in place, would you be able to do quick check against the preview URL with the development version of your apps to verify that this has fixed the problems reported?

ve...@gmail.com <ve...@gmail.com> #12Jun 28, 2019 07:05AM

The preview URL has been updated with the fix.