A Wear OS release built with Gradle Plugin 8.4.0/8.5.0 may cause java.lang.IllegalAccessError [347676160]

Verified

Bug

Status Update

No update yet.

Description

ys...@gmail.com

created issue #1

Jun 17, 2024 03:45PM

DESCRIBE THE ISSUE IN DETAIL:
The release build of a Wear OS app with ongoing activity may cause java.lang.IllegalAccessError, if built with Gradle Plugin 8.4.0/

8.5.0. The error does not occur if built with Gradle Plugin 8.3.0.

STEPS TO REPRODUCE:
1. Download the attached project.
2. Build the app using assembleRelease.
3. Install the APK into a Wear OS emulator with API 33.
4. Tap the "Start" button.
5. The app will crash with the error:
java.lang.IllegalAccessError: Illegal class access: 'com.example.testgradlebug.MyService' attempting to access 'androidx.wear.ongoing.OngoingActivityData' ...

The error will not occur if change the following line in gradle/libs.versions.toml:
agp = "8.5.0"
to:
agp = "8.3.0"

ATTACH SCREENSHOTS/RECORDINGS OF THE ISSUE

ATTACH LOG FILES (Select Help > Show Log in Files, or Show Log in Finder on a Mac)

------------------

IMPORTANT: Please read

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

------------------

Studio Build: AI-241.15989.150.2411.11948838, built on June 11, 2024
Version of Gradle Plugin: 8.5.0
Version of Gradle: 8.7
Version of Java: 17.0.10+0-17.0.10b1087.21-11609105 aarch64
OS:

TestGradleBug.zip

89 KB

Download

Comments

es...@google.com <es...@google.com> Jun 17, 2024 05:59PM

Assigned to an...@google.com.

cm...@google.com <cm...@google.com> Jun 19, 2024 02:42PM

Reassigned to hu...@google.com.

hu...@google.com <hu...@google.com> #2Jun 19, 2024 02:53PM

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.

ys...@gmail.com <ys...@gmail.com> #3Jun 20, 2024 02:07AM

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

hu...@google.com <hu...@google.com> #4Jun 21, 2024 07:38PM

Reassigned to sg...@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))

ch...@google.com <ch...@google.com> Jun 26, 2024 08:44AM

Reassigned to ch...@google.com.

ch...@google.com <ch...@google.com> #5Jun 27, 2024 08:43AM

Accepted by ch...@google.com.

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

ap...@google.com <ap...@google.com> #6Jun 28, 2024 08:16AM

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

ap...@google.com <ap...@google.com> #7Jun 28, 2024 11:35AM

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,

ap...@google.com <ap...@google.com> #8Jun 28, 2024 11:54AM

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.

ap...@google.com <ap...@google.com> #9Jun 28, 2024 11:54AM

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

ap...@google.com <ap...@google.com> #10Jun 28, 2024 11:54AM

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 <ap...@google.com> #11Jun 28, 2024 11:58AM

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?

ap...@google.com <ap...@google.com> #12Jun 28, 2024 11:58AM

The preview URL has been updated with the fix.

ap...@google.com <ap...@google.com> #13Jun 28, 2024 11:58AM

Hi, can you please confirm whether this issue is fixed or not with the latest Preview URL?

Thanks

ch...@google.com <ch...@google.com> #14Jun 28, 2024 01:42PM

Marked as fixed.

Hi,

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

ys...@gmail.com <ys...@gmail.com> #15Jun 30, 2024 04:03AM

Great -- thanks for the quick confirmation! We'll be rolling this fix out to production soon. (Full ramp will be early next week.)

ch...@google.com <ch...@google.com> Jul 1, 2024 06:06AM

Status: Assigned (reopened)

ap...@google.com <ap...@google.com> #16Jul 2, 2024 07:42AM

I've tested and confirm that the issue is resolved in preview mode, also appreciate your rapid feedback.

As I'm new to building and support Chromecast based applications I'd like to better understand an aspect of the release and testing process.

Was the issue we experienced present in the preview release of Feb 1st or Feb 10th, or were unannounced updates to the preview version made after the fact.

What I want to understand is if we monitor preview releases and test our application regularly with them can we avoid this type of issue impacting us in the future? Based on our admittedly very limited sample of Chromecasts it looks like Canary was in use on 10-20% of devices before this issue was identified.

ap...@google.com <ap...@google.com> #17Jul 2, 2024 07:42AM

Thanks for testing, John! Yes, this issue has been present since the initial preview release was released in February. You should have been able to see this in the initial preview that was released back then. So going forward, testing with the preview URL prior to a new release will be the best way to ensure that you can catch issues affecting your app in advance of a new release.

ap...@google.com <ap...@google.com> #18Jul 2, 2024 07:43AM

Excellent, thanks for the confirmation. I wasn't working in this space back when the preview release came out. It's good to know that if we subscribe and monitor the cast SDK announcements we'll be able to detect issues early and ensure the ongoing functionality of our product.

Thanks again to you and all the team for the excellent support we've received on this issue.

ch...@google.com <ch...@google.com> #19Jul 2, 2024 10:42AM

Marked as fixed.

We've updated the canary with the fix -- can you verify that you're now seeing that the problem is fixed?

ys...@gmail.com <ys...@gmail.com> #20Jul 3, 2024 10:08AM

I have one device that was running canary previously, this device is no longer having the issue. I tried to use a published SMR to get debug info and confirm the loaded resource but I can't seem to get the remote debug console to work on this device, a first gen Chromecast. The console is working properly when connected to a V3 device but this one isn't running canary. If there's info I can provide or a way to validate if it's running canary please let me know.

Joris should be able to validate with a canary device that can debug for final confirmation tomorrow.

ch...@google.com <ch...@google.com> Jul 3, 2024 10:17AM

Verified by ch...@google.com.

an...@google.com <an...@google.com> #21Jul 24, 2024 08:39PM

Are you able to connect via adb connect? If so, after connecting you can use adb logcat to get logs, and then you should be able to see the receiver version in the logs. Also see https://stackoverflow.com/questions/39481241/chromecast-debug for some other troubleshooting tips. (My guess is you've already tried both of these, but if not, maybe one of them will help.)

ys...@gmail.com <ys...@gmail.com> #22Jul 25, 2024 11:42AM

The canary version CAST SDK CAF Version: 3.0.0096 is working as well.

Thanks for the great support :-)

an...@google.com <an...@google.com> #23Aug 9, 2024 12:55AM

Terrific -- thanks for verifying!

ys...@gmail.com <ys...@gmail.com> #24Aug 9, 2024 02:18AM

info@nexussistemas.com.mx