IssueTracker

The ToT dependency was coming from compose:test-utils. Jeremy raised aosp/2254837 to pin this to a prebuilt.

Alternatively, we could have added explicit androidTestImplementation dependencies on ToT to ensure it's available during dependency resolution.

TL;DR If we express a constraint on androidx.thing:thing:$TOT_VERSION which maps to the tip-of-tree version for :thing:thing, then any occurrence of androidx.thing:thing:$VERSION where the constraint is present must also include :thing:thing somewhere in the transitive dependencies.

My understanding of this issue is:

• Project A's library code depends on prebuilt B.

• Project A's test depends on prebuilt B and also library C.

• Library C declares a constraint saying that B must be the same version as Library C.

• When resolving dependencies for Project A's tests, these tests depend on prebuilt B and library C, so library C's dependency information is also considered.

• Library C says it requires B of the same version.

• To reconcile:

  • these requirements:
    • the dependency on prebuilt B
    • the constraint for B to match the version of C
  • Gradle looks for a prebuilt of B with version matching C.

• No prebuilt of B exists with the same version matching Library C, so Gradle fails to resolve the dependency.

Is this right?

The request in b/146802533 is that libraries should publish this constraint information (rather than that Gradle should know how to automatically update prebuilt dependencies into project dependencies), so I think this issue is probably different

No prebuilt of B exists with the same version matching the prebuilt of C, so Gradle fails to resolve the dependency.

Just to make sure we're aligned, this should read "library C" rather than prebuilt? It's library C (e.g. project(C) with version $X) that expresses a constraint on prebuilt B at version $X.

Assuming we're aligned...

Yes however if library B (e.g. project("B")) exists in the set of dependencies and its version matches C, then Gradle will successfully resolve the dependency by "upgrading" prebuilt B to library B.

No prebuilt of B exists with the same version matching the prebuilt of C, so Gradle fails to resolve the dependency.

Just to make sure we're aligned, this should read "library C" rather than prebuilt? It's library C (e.g. project(C) with version $X) that expresses a constraint on prebuilt B at version $X.

Yes! Fixed, thanks

The request in b/146802533 is that libraries should publish this constraint information (rather than that Gradle should know how to automatically update prebuilt dependencies into project dependencies), so I think this issue is probably different

Slightly different. Fixing b/146802533 will necessarily involve fixing this issue, since emitting constraints into all projects will cause this issue.

Given that this was caused by tests using different dependency versions than the library's runtime dependencies, though, maybe this is broken-as-intended? The fix that Jeremy implemented was to pin the tests to the same version.

Marking as Fixed even though the general problem can still occur. Unclear that we need a systemic fix.

Please check for this issue on the latest software beta build and share the new bugreport along with the screenrecord.

Android bug report (to be captured immediately after reproducing the issue) For steps to capture a bug report, please refer: https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Screen Record of the Issue by enabling show taps Please capture screen record or video of the issue using following steps: adb shell screenrecord /sdcard/video.mp4 Subsequently use following command to pull the recorded file: adb pull /sdcard/video.mp4 Attach the file to this issue.

Please provide the information as requested in comment #28, for us to further investigate this issue. Unfortunately the issue will be closed within 7 days if there is no further update.

With beta 4 on pixel 7 pro , this bug still happens to me when watching YouTube videos or any videos in Chrome app etc especially when clicking landscape screen or rotating the phone. The videos become choppy and freezes and either have to go back to portrait back to landscape to fix it.

VERY ANNOYING!🤦🏻‍♂️

Would have think an update for YouTube or Android System Webview would have fixed it by now. Guess not🙄

Hi, This issue is specific to [YouTube] media playback choppiness. For all other types of issues, please open a new issue along with the bug report here https://goo.gl/TbMiIO.

@comment#9, #12, #13, #14, #15, #20, #23, #26 and #30 Please share the bugreport as described in comment#28.

@comment#10, #21, #24, #27 Please raise a new issue with the bugreport captured on the latest beta build.

@comment#16, Please check for this issue on the latest software build and share the new bugreport as described in comment#28.

Comment#18 please confirm if the issue is observed or not as we couldn't find any suspicious logs in the bugreport.

Please provide the information as requested in comment #31, for us to further investigate this issue. Unfortunately the issue will be closed within 7 days if there is no further update.

Also all other affected users, please check for this issue on the latest software build and share a new bugreport along with the screen record.

Android bug report (to be captured immediately after reproducing the issue) For steps to capture a bug report, please refer: https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Screen Record of the Issue by enabling show taps Please capture screen record or video of the issue using following steps: adb shell screenrecord /sdcard/video.mp4 Subsequently use following command to pull the recorded file: adb pull /sdcard/video.mp4 Attach the file to this issue.

Note: Please upload the bug report and screenrecord to google drive and share the folder to android-bugreport@google.com, then share the link here.

Please check for this issue on the latest beta build / latest stable build and share the new bugreport (to be captured immediately after reproducing the issue) along with the screenrecord, If the issue persists.

Please provide the information as requested in comment #55, for us to further investigate this issue. Unfortunately the issue will be closed within 7 days if there is no further update.

As there is no bugreport shared from the latest beta build / latest stable build, we will be closing this issue as Obsolete.

If you continue to have this issue, please open a new issue and add the relevant information along with a reference link to the earlier issue.

Regarding:

No update was provided for outdated devices like pixel 4a 5g or pixel 5

We are no longer offering updates for the Pixel 4 and earlier devices (Pixel 4a (5G) / Pixel 4a / Pixel 4 / Pixel 4 XL / Pixel 3 / Pixel 3XL / Pixel 3a). Please see this support article for more information : https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices&zippy=%2Cpixel-phones%2Cnexus-devices