Status Update
No update yet.
Comments
cl...@google.com
In debug mode you will see: Load failed: cast.o.media.Il.create is not a function
This function appears to be missing in
cl...@google.com
cl...@google.com
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))
fr...@paymentsense.com
sg...@google.com
Can you also confirm whether this is happening with our latest version? You can try the preview URL that can be found here:
ch...@google.com
ap...@google.com
So I created a custom reciever app pointing to the preview cast reciever version and I have the same error
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 (
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,
ap...@google.com
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
ap...@google.com
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 (
How come some devices use canary and some do not ?
Thanks,
Joris
cl...@google.com
ap...@google.com
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.
ap...@google.com
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?
fr...@paymentsense.com
The
an...@google.com
Thanks
an...@google.com
I just tested it and it works now !!
Thanks a bunch for your quick response.
We'll do some more testing in the next few days. We'll let you if we encounter other issues.
Thanks,
Joris
as...@gmail.com
Great -- thanks for the quick confirmation! We'll be rolling this fix out to production soon. (Full ramp will be early next week.)
Description
After the upgrade to kotlin 2.0 I face this issue during the minifyReleaseWithR8 task:
NullPointerException: Cannot invoke "com.android.tools.r8.graph.E0.D1()" because the return value of "com.android.tools.r8.graph.y.d(com.android.tools.r8.graph.I2)" is null
I've found one way to solve the issue by setting/fixing the r8 version to 8.3.37. But if I use the one that comes embedded with AGP I face the issue. I'm not sure we want to block the r8 version, I think we would like to be able to use the embedded one. I've tried with other versions like 8.5.13 and I still get the issue.
I've tried running with --stacktrace but I couldn't see much more info, attached the stacktrace.
I've found another user with a really similar issue on stackoverflow posted recently:
(We have also a similar stack in terms of libs in the project)