Is there any chart library available for compose multiplatform?

I always get this error:

The Hilt Android Gradle plugin is applied but no com.google.dagger:hilt-android dependency was found.

I wan't to use Hilt with Jetpack Compose but always I got this error

I’m in the process of migrating from buildSrc to build-logic, and I was studying idiomatic-gradle and also Google’s now-in-android repository. But I’m having a problem, in buildSrc I’ve classes and enums that can be accessed by any module’s

build.gradle.kts

, but when using build-logic, I can’t share them, it throws

org.gradle.internal.exceptions.LocationAwareException

. Surely I’m doing something wrong because Google’s sample uses it with no problem here, but I don’t know what’s missing 😞 Any hint? Thanks 🙏

After upgrading to Gradle 8.1 (from 7.X) I got

Consumable configurations with identical capabilities within a project (other than the default configuration) must have unique attributes, but configuration ':shared:releaseFrameworkIosFat' and [configuration ':shared:releaseFrameworkIosArm64'] contain identical attribute sets. Consider adding an additional attribute to one of the configurations to disambiguate them.

I fail to understand where this does come from and what I should do. This is part of the configuration in `shared`:

listOf(
    /* App Store */
    iosArm64(),
    /* Apple Silicon iOS Simulator */
    iosSimulatorArm64(),
    /* Intel macOS Devices */
    macosX64()
).forEach {

    it.binaries.framework(
        buildTypes = setOf(NativeBuildType.RELEASE)
    ) {
        baseName = "shared"
        /* Bitcode was deprecated with XCode 14 */
        embedBitcode("disable")
        /* Exported dependencies */
        export("com.appmattus.crypto:cryptohash:${Versions.cryptoHash}")
    }
}

    val iosArm64Main by sourceSets.getting
    val iosSimulatorArm64Main by sourceSets.getting
    val macosX64Main by sourceSets.getting
//    val macosArm64Main by sourceSets.getting

    @Suppress("UnusedPrivateMember", "UNUSED_VARIABLE") // False positive
    val appleMain by sourceSets.creating {

        iosArm64Main.dependsOn(this)
        iosSimulatorArm64Main.dependsOn(this)
        macosX64Main.dependsOn(this)
//        macosArm64Main.dependsOn(this)

        dependencies {

            // Networking
            api("io.ktor:ktor-client-ios:${Versions.ktor}")

            // Database
            api("com.squareup.sqldelight:native-driver:${Versions.sqlDelight}")
        }
    }

Hi People! How do you load image resources in your compose ios app ?

Is it possible to make a sealed class parcelable? I’ve annotated the child classes with `@Parcelize`but when I add the annotation to the parent, I get an error saying “Parcelable should not be a ‘sealed’ or ‘abstract’ class”

Hi everyone, I’m dealing with an issue when trying to spy my class contains a value class inside the constructor with

spyk

which provided by

Mockk

The code as below:

@JvmInline
value class MyValueClass(Val value: String = “”) : Serializable

class A(
   Val valueClass: MyValueClass = MyValueClass()
)

// In unit test file
@Test
fun test() {
    Val mockClass = spyk<A>()
    …
}

And this error happened

io.mockk.MockKException: Can't instantiate proxy via default constructor for class A

Appreciate with your help 🙏

I set

allWarningsAsErrors = true

in all of my projects because I find that addressing warnings before they become bugs makes life easier. However a lot of build functionality uses the same concept of warning to flag things that can't be addressed by the user. There's been discussion about this before (e.g. here and here) and now I've run into it again when trying to update to Kotlin 2.0.0 in a project that uses kapt. If I set

kapt.use.k2 = false

I get this warning:

> Task :app:kaptGenerateStubsDebugKotlin FAILED
w: Kapt currently doesn't support language version 2.0+. Falling back to 1.9.
e: warnings found and -Werror specified

and if I set

kapt.use.k2 = true

I get this warning:

> Task :app:kaptGenerateStubsDebugKotlin FAILED
w: K2 kapt is an experimental feature. Use with caution.
e: warnings found and -Werror specified

in both cases my only recourse to using Kotlin 2.0.0 is to set

allWarningsAsErrors = false

which can lead to the quality of my project degrading. It would be nice if

allWarningsAsErrors

differentiated between warnings that are resolvable by the user, and warnings that are not.

We (still) use slf4j/logback in our Kotlin code. Currently, we define a

val logger: Logger = LoggerFactory.getLogger(Foo::class.java)

in the companion object of a class

Foo

. I remember a discussion about defining this as a class property instead of as a companion object property (which would then allow to use

val logger: Logger = LoggerFactory.getLogger(this::class.java)

) but I can't find it anymore. What is current best practice here ?

Whenever I try to

readln()

I get

Exception in thread "main" kotlin.io.ReadAfterEOFException: EOF has already been reached

Running the app via gradle, any ideas why it's happening?