Crash when run Jetpack Compose App in Android Studio 2021.1.1 Canary 4 [194289155]

Fixed

Bug

Status Update

No update yet.

Description

om...@gmail.com

created issue #1

Jul 21, 2021 06:11PM

Jetpack Compose release version: 1.0.0-rc01

Android Studio Build:

Android Studio Bumblebee | 2021.1.1 Canary 4
Build #AI-211.7628.21.2111.7545178, built on July 13, 2021
Runtime version: 11.0.10+0-b96-7249189 amd64
VM: OpenJDK 64-Bit Server VM by Oracle Corporation
Windows 10 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 1280M
Cores: 16
Registry: external.system.auto.import.disabled=true, ide.balloon.shadow.size=0
Non-Bundled Plugins: IdeaVIM (0.69), Key Promoter X (2021.1.1), com.github.lppedd.idea-conventional-commit (0.18.0), com.intellij.javafx (1.0.3), String Manipulation (8.15.203.000.3), com.mallowigi (36.0), io.github.fatihbozik.intellij-license-generator (0.0.13), net.vektah.codeglance (1.5.4), mobi.hsz.idea.gitignore (4.1.0), some.awesome (1.14), wu.seal.tool.jsontokotlin (3.7.1), org.jetbrains.kotlin (211-1.5.21-release-317-AS7442.40), com.developerphil.adbidea (1.6.2), com.chrisrm.idea.MaterialThemeUI (6.7.2), me.schlaubi.gradleupdater (2.0.1), com.suusan2go.kotlin-fill-class (1.0.7), org.intellij.plugins.markdown (211.7142.37), com.jetbrains.edu (2021.6-2021.1-936), tanvd.grazi (211.7442.4)

Emulator Version: 30.8.1

Device:

Name: Pixel_5_API_31

CPU/ABI: Google APIs Intel Atom (x86_64)

Path: C:\Users\wafer-li\.android\avd\Pixel_5_API_31.avd

Target: google_apis [Google APIs] (API level 31)

Skin: pixel_4

SD Card: 512M

fastboot.chosenSnapshotFile: 

runtime.network.speed: full

hw.accelerometer: yes

hw.device.name: pixel_5

hw.lcd.width: 1080

hw.initialOrientation: Portrait

image.androidVersion.api: 31

tag.id: google_apis

hw.mainKeys: no

hw.camera.front: emulated

avd.ini.displayname: Pixel 5 API 31

hw.gpu.mode: auto

hw.ramSize: 1536

PlayStore.enabled: false

fastboot.forceColdBoot: no

hw.cpu.ncore: 4

hw.keyboard: yes

hw.sensors.proximity: yes

hw.dPad: no

hw.lcd.height: 2340

vm.heapSize: 256

skin.dynamic: yes

hw.device.manufacturer: Google

hw.gps: yes

hw.audioInput: yes

image.sysdir.1: system-images\android-31\google_apis\x86_64\

showDeviceFrame: yes

hw.camera.back: virtualscene

AvdId: Pixel_5_API_31

hw.lcd.density: 440

hw.arc: false

hw.device.hash2: MD5:3274126e0242a0d86339850416b0ce34

fastboot.forceChosenSnapshotBoot: no

fastboot.forceFastBoot: yes

hw.trackBall: no

hw.battery: yes

hw.sdCard: yes

tag.display: Google APIs

runtime.network.latency: none

disk.dataPartition.size: 6442450944

hw.sensors.orientation: yes

avd.ini.encoding: UTF-8

hw.gpu.enabled: yes

Steps to Reproduce:

Create New Project in wizard
Wait for Gradle synchronizing things
Click Run App at top-right corner

And it will crash, with those logs:

2021-07-22 10:08:00.731 7212-7212/li.wafer.myapplication E/AndroidRuntime: FATAL EXCEPTION: main
    Process: li.wafer.myapplication, PID: 7212
    java.lang.AbstractMethodError: abstract method "void androidx.lifecycle.DefaultLifecycleObserver.onCreate(androidx.lifecycle.LifecycleOwner)"
        at androidx.lifecycle.FullLifecycleObserverAdapter.onStateChanged(FullLifecycleObserverAdapter.java:36)
        at androidx.lifecycle.LifecycleRegistry$ObserverWithState.dispatchEvent(LifecycleRegistry.java:354)
        at androidx.lifecycle.LifecycleRegistry.addObserver(LifecycleRegistry.java:196)
        at androidx.compose.ui.platform.AndroidComposeView.onAttachedToWindow(AndroidComposeView.android.kt:808)
        at android.view.View.dispatchAttachedToWindow(View.java:20752)
        at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:3490)
        at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:3497)
        at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:3497)
        at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:3497)
        at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:3497)
        at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2578)
        at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:2091)
        at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:8584)
        at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1037)
        at android.view.Choreographer.doCallbacks(Choreographer.java:845)
        at android.view.Choreographer.doFrame(Choreographer.java:780)
        at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1022)
        at android.os.Handler.handleCallback(Handler.java:938)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at android.os.Looper.loopOnce(Looper.java:201)
        at android.os.Looper.loop(Looper.java:288)
        at android.app.ActivityThread.main(ActivityThread.java:7829)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:982)

Comments

om...@gmail.com <om...@gmail.com> #2Jul 21, 2021 06:13PM

Project: platform/frameworks/support
Branch: androidx-main

commit a330c0d3bcdd41326f37968a60e6084ad4a2e32c
Author: Chet Haase <chet@google.com>
Date: Wed Jul 05 07:26:46 2023

Convert APIs using PointF to use Float instead

PointF is a convenient mechanism for passing around x.y values
representing 2D points. But there are downsides, including:
- Converting to PointF: You may not have the data in PointF form
to begin with, so using an API which takes PointF requires converting
the data to that form (including allocating a PointF object every time)
- Mutability: Point structures can be mutated internally, causing
unpredictability in what that mutation means. Should the library
react to those changes? Ignore them? Do defensive copies (requiring
even more allocations)? Using primitive types like Float make the
behavior more obvious (by making the data inherently immutable).
- Allocations: Whenever we use object types, there are necessarily
allocations on the Java heap for them. This puts pressure on the GC
at both allocation and collection time. Given the amount of points
being passed around (especially at morph creation time, when curves
are being split and created), this causes a lot of PointF objects to
be allocated (even temporarily). Using Float avoids that problem.

Also fixed bug with unclosed paths causing discontinuity at the
start/end point.

Bug: 276466399
Bug: 290254314
Test: integration and unit tests pass
Relnote: PointF parameters changed to Float pairs
Change-Id: Id4705d27c7be31b26ade8186b99fffe2e2f8450e

M graphics/graphics-shapes/api/current.txt
M graphics/graphics-shapes/api/restricted_current.txt
M graphics/graphics-shapes/src/androidTest/java/androidx/graphics/shapes/CubicShapeTest.kt
M graphics/graphics-shapes/src/androidTest/java/androidx/graphics/shapes/CubicTest.kt
M graphics/graphics-shapes/src/androidTest/java/androidx/graphics/shapes/PolygonMeasureTest.kt
M graphics/graphics-shapes/src/androidTest/java/androidx/graphics/shapes/PolygonTest.kt
M graphics/graphics-shapes/src/androidTest/java/androidx/graphics/shapes/RoundedPolygonTest.kt
M graphics/graphics-shapes/src/androidTest/java/androidx/graphics/shapes/ShapesTest.kt
M graphics/graphics-shapes/src/androidTest/java/androidx/graphics/shapes/TestUtils.kt
M graphics/graphics-shapes/src/main/java/androidx/graphics/shapes/Cubic.kt
M graphics/graphics-shapes/src/main/java/androidx/graphics/shapes/CubicShape.kt
M graphics/graphics-shapes/src/main/java/androidx/graphics/shapes/FeatureMapping.kt
M graphics/graphics-shapes/src/main/java/androidx/graphics/shapes/FloatMapping.kt
M graphics/graphics-shapes/src/main/java/androidx/graphics/shapes/Morph.kt
M graphics/graphics-shapes/src/main/java/androidx/graphics/shapes/PolygonMeasure.kt
M graphics/graphics-shapes/src/main/java/androidx/graphics/shapes/RoundedPolygon.kt
M graphics/graphics-shapes/src/main/java/androidx/graphics/shapes/Shapes.kt
M graphics/graphics-shapes/src/main/java/androidx/graphics/shapes/Utils.kt
M graphics/integration-tests/testapp-compose/src/main/java/androidx/graphics/shapes/testcompose/DebugDraw.kt
M graphics/integration-tests/testapp-compose/src/main/java/androidx/graphics/shapes/testcompose/ShapeEditor.kt
M graphics/integration-tests/testapp/src/main/java/androidx/graphics/shapes/test/MaterialShapes.kt

https://android-review.googlesource.com/2649119

b9...@gmail.com <b9...@gmail.com> #3Jul 21, 2021 06:42PM

PointF was the main (possibly only) mutability issue, marking this as fixed

yu...@gmail.com <yu...@gmail.com> #4Jul 21, 2021 08:33PM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.graphics:graphics-shapes:1.0.0-alpha04

ae...@google.com <ae...@google.com> #5Jul 22, 2021 12:00AM

Assigned to au...@google.com.

aurimas@, are you the right person for triaging Android Studio version-specific issues? I saw you upgraded AndroidX to Bumblebee Canary 3 last week. This bug report might be specific to Bumblebee Canary 4, I'm not certain.

au...@google.com <au...@google.com> #6Jul 22, 2021 12:28AM

Status: New

Tested this quickly locally, it seems that the studio template creates a project that crashes out of the box. Updating compose_version to 1.0.0-rc02 and kotlin-gradle-plugin to 1.5.10 fixed the crash for me locally. We likely want to update studio template to use the latest of compose and kotlin.

au...@google.com <au...@google.com> #7Jul 22, 2021 12:30AM

Moving to studio component for triage.

This is a pretty bad user experience so ccing annachiarab@ to make sure this gets attention

au...@google.com <au...@google.com> #8Jul 22, 2021 12:32AM

It is likely to be addressed ag/Iafc18b104ff77fcd513d35db224d48f3b915a4e3

ky...@gmail.com <ky...@gmail.com> #9Jul 22, 2021 02:40AM

I am running into this same issue on a project using compose 1.0.0-rc02, kotlin-gradle-plugin 1.5.10, AGP 7.1.0-alpha04, and AS 2021.1.1 Canary 4. It is only when I install app from AS. When I build from gradle via command line, I can run the app just fine.

b9...@gmail.com <b9...@gmail.com> #10Jul 22, 2021 04:22AM

#6 Did you run the app through cmd or IDE?

om...@gmail.com <om...@gmail.com> #11Jul 22, 2021 05:29AM

I test the case #9 describe with 1.0.0-rc01 and 1.0.0-rc02

It turns out that it is not related to the compose_version.

If you build from gradle via command line, it will just works fine.

But run in IDE it will crash.

go...@maax.gr <go...@maax.gr> #12Jul 22, 2021 12:28PM

Same error here

ma...@gmail.com <ma...@gmail.com> #13Jul 22, 2021 01:10PM

I don't think this is an Android Studio issue. I updated three existing projects to AGP 7.1.0-alpha04 and all of them broke. They all throw the exception listed in the original report.

If I roll each project back to AGP 7.1.0-alpha03 they all work again, even if I build from AS Bumblebee 2021.1.1 Canary 4.

It certainly seems to be an AGP issue, to me.

Message last modified on Jul 22, 2021 01:10PM

ga...@google.com <ga...@google.com> #14Jul 22, 2021 02:09PM

Assigned to ga...@google.com.

I'm able to reproduce, looking into it now.

ga...@google.com <ga...@google.com> #15Jul 22, 2021 02:29PM

The issue is that AGP passes min api level 21 to D8 causing it to remove the default methods from DefaultLifecycleObserver (make them abstract) but it does not pass desugaring classpath when rewriting invocations in AndroidComposeView.onAttachedToWindow.

b9...@gmail.com <b9...@gmail.com> #16Jul 22, 2021 07:52PM

Another workaround is to change the deploy option from Default APK to APK from app bundle, then we could deploy to device via Android Studio.

ga...@google.com <ga...@google.com> #17Jul 23, 2021 08:04AM

Current workaround is to (temporarily) increase your minSdkVersion to 24+ in build.gradle file.

jo...@gmail.com <jo...@gmail.com> #18Jul 23, 2021 09:31AM

This issue isn't related to Canary 4. I had this issue with Canary 4 but uninstalled it and then installed Arctic Fox (2020.3.1) RC 1 and this issue was still there. Changing the minSdkVersion to 24+ does fix the problem.

ga...@google.com <ga...@google.com> #19Jul 23, 2021 09:38AM

To clarify, the issue is not in Android Studio (the IDE), but it is in the Android Gradle plugin.

b9...@gmail.com <b9...@gmail.com> #20Jul 23, 2021 09:40AM

Buy why compiled through cmd will work?

ga...@google.com <ga...@google.com> #21Jul 23, 2021 09:45AM

This is because when building from the IDE, AGP knows the API of the device which is used for deployment. This information is used to optimize the dexing pipeline (e.g avoid desugaring unless you run on device 23-). In AGP 7.1.0-alpha04 we introduced a bug where:

the api version used for dexing is minSdkVersion e.g 21
because we deploy to a device 24+ (e.g 30), desugaring is not requested

This means that D8 (dex compiler) will strip interface method and make them abstract, but it will not perform full rewriting, which leads to AbstractMethodError.

When building from the command line, minSdkVersion used for dexing and deciding if desugaring should be performed is the same, so that's why you see no issues.

b9...@gmail.com <b9...@gmail.com> #22Jul 23, 2021 09:47AM

Great explanation! Wait for your fix thanks.

ga...@google.com <ga...@google.com> #23Jul 26, 2021 07:17PM

Marked as fixed.

This will be fixed in AGP 7.1.0-alpha06. Until that version is released, you can use workarounds from #21.

Change id: Ifcdc39995ff4f05c4bdfd4622127e15dd0f33d4d

ma...@aexp.com <ma...@aexp.com> #24Nov 2, 2021 04:45PM

This also seems to happen in Bumblebee Canary 3 with Compose 1.1.0-Beta01.

ga...@google.com <ga...@google.com> #25Nov 2, 2021 04:47PM

Re #24: Can you please file a separate issue with a sample project, idea.log, build output, and logcat crash info?

fr...@daon.com <fr...@daon.com> #26Apr 28, 2022 10:54AM

what were the workarounds for this exactly? I'm experiencing this very same issue with AGP 7.1.3

ga...@google.com <ga...@google.com> #27Apr 28, 2022 10:58AM

Re #26: This issue should be fixed in AGP 7.1.3. Can you please file a new bug with details listed in #25?

be...@crisalid.com <be...@crisalid.com> #28Jan 24, 2023 11:02AM

I have the same error (AbstractMethodError on DefaultLifecycleObserver.onCreate) using the newer version of Android Studio: Electric Eel

Is there any similar report that isn't 1 or 2 years old?

sh...@gmail.com <sh...@gmail.com> #29Jun 2, 2023 05:39AM

I have error please fix it with YouTube premium

be...@gmail.com <be...@gmail.com> #30Nov 14, 2023 09:40AM

I face the same issue with agp version 8.1.2

ga...@google.com <ga...@google.com> #31Nov 14, 2023 09:54AM

Re #30: Can you please file a separate issue with a sample project that reproduces the bug? See https://developer.android.com/studio/report-bugs for more details on information that we need.

be...@gmail.com <be...@gmail.com> #32Nov 23, 2023 10:30AM

Re #31: Ok.I will create a separate issue soon.
I could fix the problem by upgrading minSdkVersion from 21 to 24. But, it's not the fix I wanted. I didn't understand the #21 workaround. Can you explain more about?