When a library starts to use jetpack compose for s...

# compose

[Frank van der Laan]

When a library starts to use jetpack compose for some of its UI components, do all apps using the library have to setup compose dependencies as well?

[Mehdi Haghgoo]

No, I think the library has already fetched them!

[Frank van der Laan]

Do you think or know, because I’m having problems with this.

[Frank van der Laan]

"ClassNotFoundException: Didn't find class "androidx.compose.runtime.internal.LiveLiteralKt" is logged in the app. Even when it does not use the composables from the library.

[Mehdi Haghgoo]

Sorry, my bad. Every module has its own gradle file. So, you should set up Compose in your app module as well.

[Frank van der Laan]

I’m afraid so. FYI: the library is an external library, I’m not talking about modules

[Mehdi Haghgoo]

Right. And even an external library can also be considered a module. It is "structurally the same as an Android app module".

[Frank van der Laan]

Correct answer is: it is possible: a compose library with non-compose consumer apps. The error I had was related to the live-edit feature and I could disable it for the crashing legacy views with @NoLiveLiterals

[Mehdi Haghgoo]

Great. Just curious, how do you use your Compose components inside the non-compose consumer app?

[Chris Sinco [G]]

So is this a bug with Live Edit in an app with both Compose and Views?