Has anyone encountered this issue? I'm trying to d...

# compose

[Adib Faramarzi]

Has anyone encountered this issue?
I'm trying to do `

composeView.setContent {
    Text(text = "WELCOME TO COMPOSE!")
}

and I get a runtime error
java.lang.NoSuchMethodError: No virtual method setContent(Lkotlin/jvm/functions/Function0;)V in class Landroidx/compose/ui/platform/ComposeView; or its super classes (declaration of 'androidx.compose.ui.platform.ComposeView' appears in /data/app/taxi.tap30.passenger.debug--kKKwSbfzrf377VbKRnzSQ==/base.apk)

[Colton Idle]

Are you using buildSrc ?

[theapache64]

@Adib Faramarzi Did you try this?

[Luis]

The setContent() extension is in the `

androidx.core:core-ktx

[Luis]

So check if you have that has a dependency

[Colton Idle]

If you use buildSrc, you can check the solution for this here: https://issuetracker.google.com/issues/176079157

[Adib Faramarzi]

@Colton Idle No, regular groovy.

[Adib Faramarzi]

@theapache64 @Luis Thanks, let me check

[Adib Faramarzi]

The core-ktx did not solve the issue. What's weird is the library is definitely in the module since the IDE can recognize the code (and ComposeView)

[Luis]

Ah sorry, I missread the error message. setContent is an extension on Activity, not View

[Adib Faramarzi]

It's a ComposeView.

[Luis]

Yes, I meant I was reading the error like it was a problem with an activity

[Luis]

I think maybe a rebuild project is in order

[Adib Faramarzi]

Sure

[ephemient]

to me it looks like compose plugin isn't working, but I don't have a guess as to why

[Albert Chang]

Yes this looks like compose compiler plugin not being correctly applied as @Composable () -> Unit should be Function2 instead of Function0 after transformation performed by the compiler plugin.
Are you enabling compose compiler plugin by specifying buildFeatures.compose = true in your build script?

[Cicero]

Never forget to check the imports because they will have similar the EXACT names of the wrong ones 🙂 ❤️ Hell ❤️

[brandonmcansh]

buildFeatures { compose true }

[Adib Faramarzi]

The buildFeatures is included. Re-building also didn't help.

[brandonmcansh]

Is this activity/fragment in a module or :app

[Adib Faramarzi]

in a module

[Adib Faramarzi]

could this be related to the fact that I have disabled the new JVM IR backend? (useOldBackend true )

[brandonmcansh]

Did you define buildFeatures in the module too?

[Adib Faramarzi]

Yes

[brandonmcansh]

Compose also needs import in the main app module

[Adib Faramarzi]

I have the dependencies only in the module though

[brandonmcansh]

Or api() the compose deps in the module

[Adib Faramarzi]

Let me see

[brandonmcansh]

Using dagger as well?

[Adib Faramarzi]

Yes

[Adib Faramarzi]

Including the script in the main app module did not help

[Adam Powell]

could this be related to the fact that I have disabled the new JVM IR backend? (useOldBackend true )

The compose compiler plugin is an IR plugin so yes, you've ensured it's not running on your code by doing this 🙂

[Adib Faramarzi]

@Adam Powell
That is unfortunate...
I don't seem to be able to bring compose to our project any time soon, due to the fact that Kotlin 1.5.10 (until 1.5.30) has a major issue with kotlin.Result types (and runCatching) and compose relies on these Kotlin versions

[Adib Faramarzi]

I'm wondering If I can turn the old backend off for all other modules and turn it on for the compose module.

[Adam Powell]

That should work fine. It's how a lot of projects worked with compose before 1.5 where the IR backend became the default

[Adib Faramarzi]

Thanks, that would be okay. I'll check.

[Adib Faramarzi]

I managed to make it work. Right now, all modules rely on the old backend and there's a new compose module with useOldBackend=true and everything seems to run smoothly.

[Nurlibay]

This error encountered to me now, I can't solve by adding useOldBackend=true