Hello everyone wave I m trying to setup compose in an existi

Question

Hello everyone wave I m trying to setup compose in an existing project and I m facing the following error `NoSuchMethod No Static method setContent` My dependencies ```dependencies implementation androidx core core ktx 1 7 0 implementation androidx compose ui ui 1 1 1 implementation androidx compose material material 1 1 1 implementation androidx compose ui ui tooling preview 1 1 1 implementation androidx lifecycle lifecycle runtime ktx 2 4 1 implementation androidx activity activity compose 1 4 0 debugImplementation androidx compose ui ui tooling 1 1 1 debugImplementation androidx compose ui ui test manifest 1 1 1 ```

henrikhorbovyi · Answer

```kotlinVersion = 1 6 21 gradlePluginVersion = 7 2 1 ```

Oleksandr Balan · Answer

Did you add `buildFeatures` block in your gradle setup <https developer android com jetpack compose interop adding config gradle|https developer android com jetpack compose interop adding config gradle>

Adam Powell · Answer

You re not running the compose compiler plugin in the module that includes the call to `setContent`

henrikhorbovyi · Answer

```android defaultConfig minSdk = ANDROID MIN SDK VERSION compileSdk = ANDROID COMPILE SDK VERSION versionCode = System getenv VERSION CODE toIntOrNull 1 versionName = PUBLISHING VERSION buildToolsVersion = ANDROID BUILD TOOLS VERSION compileOptions sourceCompatibility = VERSION JAVA targetCompatibility = VERSION JAVA sourceSets main java srcDir src main kotlin kotlinOptions jvmTarget = 1 8 buildFeatures compose = true composeOptions kotlinCompilerExtensionVersion = 1 1 1 packagingOptions resources excludes += META INF AL2 0 LGPL2 1 ```

Adam Powell · Answer

If you are loading either the Kotlin or Android Gradle plugins but not both in your `buildSrc` then this can also happen for some non obvious gradle classpath reasons

henrikhorbovyi · Answer

That s my `android` block in build gradle kts file

Adam Powell · Answer

Do you have a `buildSrc` in this project

henrikhorbovyi · Answer

Yeah I have

Adam Powell · Answer

Does it load the Kotlin gradle plugin or Android gradle plugin

henrikhorbovyi · Answer

I created a new module which is an app inside a monolithic project

henrikhorbovyi · Answer

Yeah it loads

Adam Powell · Answer

Then have it load both plugins in `buildSrc`

henrikhorbovyi · Answer

That s my buildSrc build gradle kts ```dependencies api com android tools build gradle 7 1 2 implementation com android tools build gradle api 7 1 2 api com android tools build bundletool 1 4 0 implementation kotlin stdlib 1 6 10 implementation kotlin stdlib jdk8 enforcing the same kotlin version to avoiding classpath conflicts implementation kotlin stdlib jdk7 enforcing the same kotlin version to avoiding classpath conflicts implementation kotlin reflect implementation io reactivex rxjava2 rxkotlin 2 4 0 implementation io reactivex rxjava2 rxjava 2 2 20 implementation com squareup retrofit2 retrofit 2 9 0 implementation com squareup retrofit2 adapter rxjava2 2 9 0 implementation com squareup retrofit2 converter moshi 2 9 0 implementation com squareup moshi moshi 1 13 0 implementation com squareup moshi moshi kotlin 1 13 0 kapt com squareup moshi moshi kotlin codegen 1 13 0 testImplementation junit junit 4 13 2 testImplementation io kotlintest kotlintest assertions 3 4 2 ```

Adam Powell · Answer

They need to be able to see each other from their classloader for agp to configure the compose compiler plugin with the Kotlin gradle plugin

henrikhorbovyi · Answer

But Adam let me see if I got it I load the classpath for `kotlin gradle plugin` and `android gradle plugin` in the build gradle kts from project root Now I need to load them inside the `buildSrc build gradle kts` right

Adam Powell · Answer

yes if you load either of these plugins inside your `buildSrc` ```dependencies implementation com android tools build gradle $androidGradlePluginVersion implementation org jetbrains kotlin kotlin gradle plugin $kotlinGradlePluginVersion ``` then you must load both of them together

henrikhorbovyi · Answer

Ok I ll try it Thank you slightly smiling face

henrikhorbovyi · Answer

< Adam Powell> it worked zap thank you blob smile happy

henrikhorbovyi · Answer

We are implementing Compose in a project in the company I currently work I was really excited because it ll be the first time I m going to use Compose in a company product So thank you a lot o

Adam Powell · Answer

happy to help and I m glad you re excited smile

Adam Powell · Answer

I just filed a bug to the documentation to get this added to the page linked above hopefully I can stop answering this question soon sweat smile

henrikhorbovyi · Answer

Cool cool doge Is it open Can you share it So I can also document it in the project

Adam Powell · Answer

hmm doesn t look like it I m afraid The docs pages have a few extra buttons for filing feedback bugs for us when we look at them and that flow files them under an internal component

Colton Idle · Answer

I think I filed a bug for this wayyyyy back <https issuetracker google com issues 176079157> gt I will chat with the Documentation folks so we make it clearer in our Compose documentation sob

Colton Idle · Answer

I definitely opened another bug for this to be documented after it happened to me again but I remember someone closing it basically saying that its not composes responsibility to let people know about this

Colton Idle · Answer

Ill look for it tomorrow must sleep

Colton Idle · Answer

Oh yeah Last year Jim seemed to disuade against it plus he tagged adam joy Its come full circle I tried to be a good compose citizen shruggie <https kotlinlang slack com archives CJLTWPH7S p1623347985410800 thread ts=1623270940 306300 amp cid=CJLTWPH7S>

henrikhorbovyi · Answer

Thanks for sharing it < Colton Idle> Hope that will be documented or at least giving us a proper error message soon slightly smiling face