Status Update
Comments
si...@google.com <si...@google.com>
si...@google.com <si...@google.com> #2
And create a non-compose app will just works fine.
si...@google.com <si...@google.com>
si...@google.com <si...@google.com>
si...@google.com <si...@google.com>
si...@google.com <si...@google.com> #3
no...@google.com <no...@google.com> #4
Same issue here, app crashes on start when using android-gradle 7.1.0-alpha04 and AS Canary 4
si...@google.com <si...@google.com>
si...@google.com <si...@google.com> #5
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.
si...@google.com <si...@google.com> #6
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.
si...@google.com <si...@google.com>
si...@google.com <si...@google.com>
si...@google.com <si...@google.com> #7
Moving to studio component for triage.
This is a pretty bad user experience so ccing annachiarab@ to make sure this gets attention
si...@google.com <si...@google.com>
si...@google.com <si...@google.com>
si...@google.com <si...@google.com>
si...@google.com <si...@google.com>
ub...@gmail.com <ub...@gmail.com> #8
It is likely to be addressed ag/Iafc18b104ff77fcd513d35db224d48f3b915a4e3
[Deleted User] <[Deleted User]> #9
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.
ub...@gmail.com <ub...@gmail.com> #10
gr...@google.com <gr...@google.com> #11
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.
aa...@marinosoftware.com <aa...@marinosoftware.com> #12
si...@google.com <si...@google.com>
so...@google.com <so...@google.com>
so...@google.com <so...@google.com>
so...@google.com <so...@google.com>
ap...@google.com <ap...@google.com> #13
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.
ap...@google.com <ap...@google.com> #14
I'm able to reproduce, looking into it now.
ap...@google.com <ap...@google.com> #15
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
.
ap...@google.com <ap...@google.com> #16
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.
ap...@google.com <ap...@google.com> #17
Current workaround is to (temporarily) increase your minSdkVersion
to 24+ in build.gradle
file.
ap...@google.com <ap...@google.com> #18
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.
na...@google.com <na...@google.com> #19
To clarify, the issue is not in Android Studio (the IDE), but it is in the Android Gradle plugin.
Description
We have the Linkify and LinkifyCompat classes. Moreover, URLSpan on android handles the visual aspects of the links and also touch handling.
However, the current system suffers a lot from a few behaviors:
- linkify using patterns make text processing slow
- the developer had no control over the creation of URLSpans which caused them not to be able to have custom logic on click.
On android hyperlinks can be styled at the widget level.
This ticket is for the first step of hyperlink support which enables the display of hyperlinks.
related document: