Fixed
Status Update
No update yet.
Comments
sl...@google.com
pr...@gmail.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 inhttps://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.
In debug mode you will see: Load failed: cast.o.media.Il.create is not a function
This function appears to be missing in
nk...@google.com
I'm having this issue with 1 of my 3 Chromecasts and actually bought a new Chromecast because I thought it was broken.
dn...@google.com
nk...@google.com
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))
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))
Description
Version used: Espresso(3.0.1), Runner and Rules (1.0.1)
What steps will reproduce the problem?
1. Install orchestrator-1.0.1.apk and test-services-1.0.1.apk
2. Build App under Test and Test apk and install on device
3. execute below command for Test Orchestration
adb shell 'CLASSPATH=$(pm path android.support.test.services) app_process / \android.support.test.services.shellexecutor.ShellMain am instrument -w -e \
targetInstrumentation com.package.test/com.package.espressoTests.Instrumentation \android.support.test.orchestrator/.AndroidTestOrchestrator'
After executing above command, it starts execution on device (Samsung Marshmallow) with below log output
MdfppReflectionUtils isMdfEnforced encountered an exception. Cause: java.lang.UnsatisfiedLinkError: No implementation found for boolean com.samsung.android.security.CCManager.isMdfEnforced() (tried Java_com_samsung_android_security_CCManager_isMdfEnforced and Java_com_samsung_android_security_CCManager_isMdfEnforced__) Message: null
MdfppReflectionUtils isMdfEnforced encountered an exception. Cause: java.lang.UnsatisfiedLinkError: No implementation found for boolean com.samsung.android.security.CCManager.isMdfEnforced() (tried Java_com_samsung_android_security_CCManager_isMdfEnforced and Java_com_samsung_android_security_CCManager_isMdfEnforced__) Message: null
If we execute only one/few test case, it shows below output when execution is complete
-Final result — OK (0 tests)
If we execute batch of tests, execution stopped because of process crash due to out of memory.
How are you running your tests (via Android Studio, Gradle, adb, etc.)?
Using adb command
What is the expected output? What do you see instead?
Expected output is to continue execution of next test if there is any crash due to memory issue or due to application crash due to some other reason. I have attached few screenshots which shows memory usage when process crashed and Instrumentation file. Please let me know if you need any other details.