Fixed
Status Update
Comments
xa...@google.com <xa...@google.com> #2
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
xa...@google.com <xa...@google.com> #3
I'm having this issue with 1 of my 3 Chromecasts and actually bought a new Chromecast because I thought it was broken.
ga...@google.com <ga...@google.com> #4
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))
ga...@google.com <ga...@google.com> #5
Thanks for reporting the issue. We will investigate further and get back to you with our findings.
an...@google.com <an...@google.com> #6
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
Can you also confirm whether this is happening with our latest version? You can try the preview URL that can be found here:
fi...@gmail.com <fi...@gmail.com> #7 Restricted+
Restricted+
Comment has been deleted.
wi...@gmail.com <wi...@gmail.com> #8 Restricted
Restricted
Comment has been deleted.
Description
The
JavaPreCompileTask
computes KSP and annotation processors that are consumed in downstreamJavaCompile
tasks. For annotation processors, the compilation task in AGP computes if any processors are non-incremental, and (correctly) reports a warning for any non-incremental processors found.However, there's a bug in
JavaPreCompileTask
's logic as it merges the KSP and annotation processing classpath when computing, meaning that dependencies on the KSP classpath are incorrectly treated as if they are going to be on the JavaCompileannotationProcessorClasspath
.Essentially, in this bit of logic
It shouldn't be merging together the ksp and annotation processor artifacts, as KSP dependencies do not participate in the
JavaCompile
classpath.In the meantime, I can work around this with the following snippet in Kotlin gradle DSL.