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

Thank you for the report. We will try to fix this soon. In the meantime, could you please start the emulator from the console (see the commands below), open the camera app to crash it and attach the output, it might help to figure out what the problem is:

cd /Users/YOUR_USERNAME/Library/Android/sdk/emulator
./emulator -list-avds
./emulator -verbose -avd YOUR_AVD_FROM_PREVIOUS_STEP

if there is a crash report to send, please send it and attach the report id.

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

We got a crash report (thanks JP): 872e3b20bc34905b. It says EXC_BAD_INSTRUCTION / 0x00000001 and the console also says "Illegal hardware instruction". I suspect the new MacOS brought a new hypervizor which causes this behavior. Haitao, could you please take a look?

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

We have quite some crashes like this:

product_name="AndroidEmulator" AND crash.Reason="EXC_BAD_INSTRUCTION / 0x00000001" AND cpu.Architecture="arm64"

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

The most of crashes happen here:

vVertical_Scale_ARGB_8888_Accelerate
vImageVerticalShear_ARGB8888
vImageVerticalShear_ARGB8888
vImageScale_ARGB8888

vRotateClockwise270Degree_ARGB8888_Accelerate2
vRotate_90_ARGB_8888_270Degree_Accelerate2

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

I suspect EXC_BAD_INSTRUCTION happens in vImageRotate90_ARGB8888 and vImageScale_ARGB8888 which are used by webcam on MacOS.

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

With complete honesty, I have to say that I’m extremely disappointed by the handling of this issue by google and by the fact that it came out in the first place. I need to use android studio for work purposes and I am forced to switch to a different machine. Mac OS Sonoma has been in beta testing for months and google has had plenty of time to ensure the application would be properly running. I expect this issue to have the maximum priority and to be solved very soon.

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

Hi rforzani22, I am sorry for this experience. This bug is my top priority. We expect a fix to be merged within a week. You should be able to download a build directly from our build server (https://ci.android.com/builds/branches/aosp-emu-master-dev/grid) once the fix is merged. The release process will take some additional time.

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

Thanks for making it a top priority, looking forward for the fix, good luck!

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

We confirmed #comment6. I removed vImageRotate90... and vImageScale... and use what I could find (which is not as efficient as vImage... ones, we will try to figure out why these functions crash), it does not handle all aspect ratios and resolutions so far (it might crash for different reasons, I will be working on this tomorrow). If anyone wants to try my local build, I can share it.

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

I had to downgrade my Mac to Ventura and I realized on Mac Ventura android studio emulator ask for webcam permission which I allowed and worked but on Sonoma it doesn't ask for permission when I open camera app on webcam0

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

I would be willing to try out your local build if you can share it and I’ll let you know my experience.

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

Marked as fixed.

How can I try your local build? Can I download from somewhere?

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

rforzani22 and treblew2017, I shared a Google Drive link with you, see your email.

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

Can I try it too?

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

lechun.sk, I shared with you.

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

Still doesn't work for me It crashes when I open the camera, this report emulator verbose

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

lechun.sk, this is unexpected. Do you mind uploading a crash report and sharing its id?