I am seeing some weird behavior when producing an ...

# kotlin-native

[Sam Schilling]

I am seeing some weird behavior when producing an obj-c framework and using it in Swift. My framework A has a dependency B that is another Kotlin library that it brings in through gradle via a maven repo. In B I have a class that is structured like this:

open class Fail(val code: IFailCode = CODE.ERROR_404) {

    enum class CODE(override val description: String, override val code: Int) : IFailCode {
        ERROR_404("Resource could not be found", 404),
        …
    }
    
    interface IFailCode {
        val code: Int
        val description: String
    }
}

The weird thing is that when I use the generated framework from A in a Swift app, I can access Fail and IFailCode, but not the enum class CODE. Also of note, they are named BFail and BFailIFailCode. Following this pattern I would expect CODE to be accessible as BFailCODE but it is not.

Why wouldn’t I be able to access CODE from Swift when I can access Fail and IFailCode? The only difference I see is that one is an enum while the other two are a class and an interface. Do these behave differently when converted to objc framework?

[Kris Wong]

have you looked at the generated Obj-C header from Xcode?

[Sam Schilling]

Yeah, CODE or any renaming of it isn’t in there

[Kris Wong]

interesting

[Kris Wong]

it's weird that the interop docs don't mention enum anywhere

[Kris Wong]

https://kotlinlang.org/docs/reference/native/objc_interop.html

[Sam Schilling]

I know enums can be exported because I have other enums defined in my framework that work fine. But this enum that comes from a dependency of my framework isn’t showing up

[Kris Wong]

ahhh

[Sam Schilling]

maybe enum doesn’t show up in those docs because it is covered under class?

[Kris Wong]

is it an api dependency, and are you exporting it?

[Sam Schilling]

what do you mean by api dependency?

[Kris Wong]

in the gradle file, instead of implementation

[Sam Schilling]

oh

[Sam Schilling]

lemme check

[Sam Schilling]

pretty sure it’s implementation

[Sam Schilling]

yep, implementation

[Kris Wong]

https://kotlinlang.org/docs/reference/building-mpp-with-gradle.html

[Kris Wong]

Exporting dependencies in frameworks

[Sam Schilling]

I don’t want to export all classes from my dependency

[Sam Schilling]

Just certain ones

[Kris Wong]

i'm afraid it doesn't work that way

[Sam Schilling]

I mean, it currently is working

[Kris Wong]

perhaps you can trick it by using the symbols you need from B within A

[Sam Schilling]

My framework A depends on B where Fail and IFailCode are defined

[Sam Schilling]

And I can access both from my Swift application

[Sam Schilling]

Yes, I think that’s what it is

[Sam Schilling]

Because I include Fail in the function signature of some of my public methods of A