Hi, we have a dependency problem with our iOS target

The MPP iOS App Project `export`s both projects A and B. Projects Y, A and B have

kotlinx.serialization

and

ktor

as dependencies.

I think this would be better asked in #kotlin-native

Will be fixed in 1.3.30

@svyatoslav.scherbina is it fixed in the latest eap?

Yes. Btw, why do you find headers containing duplicated information?

Well that’s the whole issue, and you just said it’s fixed, so I don’t understand your question

The compilation error from this screenshot is fixed in 1.3.30.

Ok, thanks for the confirmation. We’ll start migration to 1.3.30 EAP then. Do you have an issue number we can follow?

Do you have an issue number we can follow?

What do you mean?

We’ll start migration to 1.3.30 EAP then

Alternatively you can prevent exporting

JsonPrimitive

to framework headers and continue using 1.3.2*.

I mean that this issue should have been reported somewhere like on https://youtrack.jetbrains.net/ but I can’t find it

Do you export

kotlinx.serialization

explicitly, like you do with project

A

?

We never explicitely export

kotlinx.serialization

,

ktor-client

or any other lib

If you don’t use

transitiveExport

in Gradle, then

JsonPrimitive

class is exported because it is used in public API. Please inspect your header to locate public API which brings

JsonPrimitive

to the header.

@svyatoslav.scherbina we’re exposing a

val

of type

KotlinxSerializer.() -> Unit

in an

object

. Would that cause

JsonPrimitive

to be exported somehow? It’s the only thing we found

Please inspect your header instead of projects.

Ok, we found it. We have a reference to

Json

is a public API, which references

JsonElement

, which references

JsonPrimitive