IssueTracker

This bug was linked in a change in the following release(s):

• androidx.lifecycle:lifecycle-common:2.6.0-alpha02
• androidx.lifecycle:lifecycle-livedata:2.6.0-alpha02
• androidx.lifecycle:lifecycle-livedata-core:2.6.0-alpha02
• androidx.lifecycle:lifecycle-livedata-core-ktx:2.6.0-alpha02
• androidx.lifecycle:lifecycle-livedata-ktx:2.6.0-alpha02
• androidx.lifecycle:lifecycle-reactivestreams:2.6.0-alpha02
• androidx.lifecycle:lifecycle-reactivestreams-ktx:2.6.0-alpha02
• androidx.lifecycle:lifecycle-runtime:2.6.0-alpha02
• androidx.lifecycle:lifecycle-runtime-compose:2.6.0-alpha02
• androidx.lifecycle:lifecycle-runtime-ktx:2.6.0-alpha02
• androidx.lifecycle:lifecycle-runtime-testing:2.6.0-alpha02
• androidx.lifecycle:lifecycle-viewmodel:2.6.0-alpha02
• androidx.lifecycle:lifecycle-viewmodel-compose:2.6.0-alpha02
• androidx.lifecycle:lifecycle-viewmodel-ktx:2.6.0-alpha02
• androidx.lifecycle:lifecycle-viewmodel-savedstate:2.6.0-alpha02

This release seems to have conflicting artifacts in the classpath. When both:

androidx.lifecycle:lifecycle-viewmodel-ktx:2.6.0-alpha02

androidx-lifecycle:lifecycle-livedata-ktx:2.6.0-alpha02

are added as dependencies, the following error pops up:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':sync:sync-test:checkProdDebugAndroidTestDuplicateClasses'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.CheckDuplicatesRunnable
   > Duplicate class androidx.lifecycle.ViewModelLazy found in modules lifecycle-viewmodel-2.6.0-alpha02-runtime (androidx.lifecycle:lifecycle-viewmodel:2.6.0-alpha02) and lifecycle-viewmodel-ktx-2.3.1-runtime (androidx.lifecycle:lifecycle-viewmodel-ktx:2.3.1)
     Duplicate class androidx.lifecycle.ViewTreeViewModelKt found in modules lifecycle-viewmodel-2.6.0-alpha02-runtime (androidx.lifecycle:lifecycle-viewmodel:2.6.0-alpha02) and lifecycle-viewmodel-ktx-2.3.1-runtime (androidx.lifecycle:lifecycle-viewmodel-ktx:2.3.1)
     
     Go to the documentation to learn how to <a href="d.android.com/r/tools/classpath-sync-errors">Fix dependency resolution errors</a>.

Downgrading to 2.6.0-alpha01 fixes this.

As an update to the above comment from TJ, this issue has been fixed and will be available in Lifecycle 2.6.0-alpha03.

The following release(s) address this bug:

• androidx.lifecycle:lifecycle-runtime:2.6.0-alpha03
• androidx.lifecycle:lifecycle-runtime-compose:2.6.0-alpha03
• androidx.lifecycle:lifecycle-viewmodel-compose:2.6.0-alpha03
• androidx.lifecycle:lifecycle-viewmodel-savedstate:2.6.0-alpha03

An unintentional side effect of the fix of b/286937712. The streamScreenshot API is registering an event listener for physical change events. This registration engine is using the CallbackRegistry, this thing has the unintended side effect that registration is only processed when the invokeCallbacks method is called. This is usually not a problem when using the GpuEngine as we receive frequent updates.

This is not the case for physical events. Things get unblocked as soon as a sensor state change happens.

Just wanted to add I've been experiencing this as well on an M1 Mac. For me running the app in release mode works fine. If you build and run in Debug and have the debugger attached, then the frames are not updating.

However this only happens in Canary:

Android Studio Iguana | 2023.2.1 Canary 17
Build #AI-232.10227.8.2321.11191411, built on December 7, 2023
Runtime version: 17.0.9+0-17.0.9b1087.7-11185874 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 14.2
GC: G1 Young Generation, G1 Old Generation
Memory: 3072M
Cores: 10
Metal Rendering is ON
Registry:
    debugger.new.tool.window.layout=true
    ide.instant.shutdown=false
    ide.experimental.ui=true

If I run the same exact emulator version 34.1.13-11169323, in current Stable:

Android Studio Hedgehog | 2023.1.1
Build #AI-231.9392.1.2311.11076708, built on November 9, 2023
Runtime version: 17.0.7+0-17.0.7b1000.6-10550314 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 14.2
GC: G1 Young Generation, G1 Old Generation
Memory: 3072M
Cores: 10
Metal Rendering is ON
Registry:
    external.system.auto.import.disabled=true
    debugger.new.tool.window.layout=true
    ide.text.editor.with.preview.show.floating.toolbar=false
    ide.instant.shutdown=false
    ide.experimental.ui=true

It does not have this issue.

Worth noting that the pop-out mode doesn't affect this.

Fix is in with https://android-review.git.corp.google.com/c/platform/external/qemu/+/2863491

https://android-review.git.corp.google.com/c/platform/external/qemu/+/2874534

what version of emulator should this be in?

Still seeing this issue with 34.1.15-11228956 in AS Hedgehog 2023.1.1 patch 1

FWIW Not seeing this issue anymore in latest canaries/beta.

I'm having this issue still.

Android Studio Iguana | 2023.2.1 Build #AI-232.10227.8.2321.11479570, built on February 22, 2024 Runtime version: 17.0.9+0--11185874 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. Windows 11.0

Android emulator version 34.1.18.0

This should be fixed in 34.1.19, please update and let us know.

Note

From now till end of Feb 2024, we are migrating to using a separate task item to track postmortem status, instead of using the original fixed bug. You may run into unexpected issues as we iron out the wrinkles in the automated workflow. Any questions or feedback, please email: android-hygiene-autobug-filer@.

Thank you for your patience and support.