Running commonTest in a KMM project when I call a function t

Question

Running commonTest in a KMM project when I call a function that uses Ktor Client I get this warning ```SLF4J Failed to load class org slf4j impl StaticLoggerBinder SLF4J Defaulting to no operation NOP logger implementation SLF4J See <http www slf4j org codes html StaticLoggerBinder> for further details ``` is it normal

CLOVIS · Answer

What are your dependencies You need a logger implementation if you want logging

Daniele B · Answer

I just realized that the warning also happens when I run the app normally not just while testing

Daniele B · Answer

In commonMain I have this dependency ```implementation io ktor ktor client logging 1 5 1 ```

Daniele B · Answer

These are all the Ktor dependencies I have in CommonMain ```implementation io ktor ktor client core $ Versions ktor implementation io ktor ktor client json $ Versions ktor implementation io ktor ktor client logging $ Versions ktor implementation io ktor ktor client serialization $ Versions ktor ```

CLOVIS · Answer

One way to fix that issue <https gitlab com braindot clovis blob master server build gradle kts|https gitlab com braindot clovis blob master server build gradle kts> It really depends on which engine you want to use

CLOVIS · Answer

If you want to go with Log back you will also need this file <https gitlab com braindot clovis blob master server src main resources logback xml|https gitlab com braindot clovis blob master server src main resources logback xml>

Daniele B · Answer

I am using Ktor Client on a multiplatform project on commonMain It seems logback is JVM only So I don t think I can add it as a dependency in CommonMain

Daniele B · Answer

Is everyone using Ktor Client on Common Main having the same issue

CLOVIS · Answer

Oh the only two times I had this issue were JVM only projects Maybe there are other artifacts for other platforms not sure

Daniele B · Answer

I was running an Android app so that s why

andylamax · Answer

< Daniele B> Yes and that warning is only printed when running on jvm Other platforms don t get that warning Adding logback to the jvm and or android target should solve your problem

Daniele B · Answer

Yes I also realized thanks