Create constraints between lifecycle artifacts [242871265]

Fixed

Bug

Status Update

No update yet.

Description

il...@google.com

created issue #1

Aug 17, 2022 05:23PM

Component used: Lifecycle

Version used: 2.6.0-alpha01

Until feature requests such as b/146802533 are released, Gradle does not do any enforcement that Lifecycle artifacts are of the same version (i.e., you could mix and match lifecycle-common:2.6.0-alpha01 with lifecycle-runtime:2.5.1).

Gradle supports constraints, which ensure that upgrading a transitive dependency will also upgrade other dependencies.

We should manually add two way constraints, similarly to what was done for Paging in b/235256201, to the various lifecycle artifacts, which will help Gradle enforce the same version policy we intend.

The pairs of artifacts we should add constraints to should match the dependencies we have right now, which should mean the list looks something like:

lifecycle-common and lifecycle-common-java8
lifecycle-common and lifecycle-runtime
lifecycle-runtime and lifecycle-runtime-ktx
lifecycle-runtime and lifecycle-runtime-compose
lifecycle-runtime and lifecycle-runtime-testing
lifecycle-livedata-core and lifecycle-livedata-core-ktx
lifecycle-livedata-core and lifecycle-livedata
lifecycle-livedata and lifecycle-livedata-ktx
lifecycle-reactivestreams and lifecycle-reactivestreams-ktx
lifecycle-viewmodel and lifecycle-viewmodel-ktx
lifecycle-viewmodel and lifecycle-viewmodel-savedstate
lifecycle-viewmodel-savedstate and lifecycle-viewmodel-compose

Comments

ap...@google.com <ap...@google.com> #2Aug 20, 2022 05:23AM

Update: I was able to downgrade to 32.1.10 and I can confirm it's smooth again. The issue is indeed in emulator version 33.1.1

ap...@google.com <ap...@google.com> #3Aug 20, 2022 07:25AM

It's happening to me too and I also confirm that reverting to 32.1.10 fixes the issue.

We should have an easier way of reverting versions. AS should allow picking the version similarly to how we already do for the other tools in SDK manager.

ap...@google.com <ap...@google.com> #4Aug 20, 2022 07:25AM

Hi,

would you try to turn on hardware GPU rendering (instead of auto GPU) and see if it fixes this issue?

ap...@google.com <ap...@google.com> #5Aug 20, 2022 07:25AM

Hi,

I'm currently not able to change this option, it is greyed out.

ap...@google.com <ap...@google.com> #6Aug 20, 2022 07:25AM

Hi,

there are 2 ways to set it:

1. use a google_apis image (instead of google_apis_playstore). it will re-enable the option.
2. go to your avd folder (usually located in ~/.android/avd/your_avd_name.avd/), open config.ini and hardware-qemu.ini, then modify those lines:

hw.gpu.enabled=yes
hw.gpu.mode=host

ap...@google.com <ap...@google.com> #7Aug 22, 2022 06:12PM

Hi,

Yes, option 2 fixes the issue (which also persists on 33.1.2 btw). Even though I get a warning when I start the emulator (see attachments).

Will this option be enabled "out of the box" in a future version?

ap...@google.com <ap...@google.com> #8Aug 22, 2022 06:12PM

Hi,

we suspect a bug in gpu detection logic on Mac M1, and will try to address it in upcoming releases.

ap...@google.com <ap...@google.com> #9Aug 23, 2022 04:43PM

Hi Devki,

would you help to cp aosp/2451107 to next stable and canary releases? Thank you!

ap...@google.com <ap...@google.com> #10Aug 23, 2022 07:35PM

Hi Devki,

Could we cherry-pick it to canary release as well? Thanks!

ap...@google.com <ap...@google.com> #11Aug 23, 2022 07:57PM

@yahan it will be picked up in the next canary since we are doing snaps!

ap...@google.com <ap...@google.com> #12Aug 24, 2022 08:02PM

Thanks!

ap...@google.com <ap...@google.com> #13Aug 26, 2022 04:47PM

Marked as fixed.

Was able to force the emulator to use the host GPU by opening it via the terminal with

./emulator -avd Resizable_API_33 -gpu host

ap...@google.com <ap...@google.com> #14Aug 26, 2022 04:47PM

I believe this is still happening in 33.1.10

na...@google.com <na...@google.com> #15Sep 12, 2022 05:51PM

Chris, would you help to send us the verbose log?

da...@google.com <da...@google.com> #16Sep 28, 2022 02:38PM

User on #comment13 should provide it. User was the one who reported this still happening with Play Store images, via Slack communities. I can also try to repro myself.

sa...@google.com <sa...@google.com> #17Oct 17, 2022 05:23PM

do you still have this problem with latest 33.1.20+ ?

na...@google.com <na...@google.com> #18Oct 24, 2022 01:38PM

If that question is for me, I've tested changing the config.ini back to "hw.gpu.mode=auto" and it appears to be fine. I have 33.1.2.0.