Hi, I think I asked this before, but does anyone k...

# multiplatform

[Jason]

Hi, I think I asked this before, but does anyone know why sometimes when you access an exported class from Shared Code library into iOS, the swiftName is prefixed as such? For example, sometimes I can just use ViewModelStoreOwner as is in one project but in another I have to name it '`Lifecycle_viewmodelViewModelStoreOwner`'? I'm not sure what dictates this naming convenstion when the iOS framework library is generated.

[Michael Krussel]

I believe this happens when the library that contains ViewModelStoreOwner was not exported in the framework.

To fix it, you add it to the list of exported dependencies, but than all symbols in the library get included increasing the size of the framework.

[Jason]

@Michael Krussel thanks, I think we talked about this before. I do export the library already for iOS framework. What's weird is i export Skie library also and I can access those type names just fine like KoinComponent and such.

[Michael Krussel]

I wonder if there are two ViewModelStoreOwner being exported, so they need something to mark them as different

[Jason]

possibly, but in the generated objective-c framework header, i only see the Lifecycle_viewmodelViewModelStoreOwner type. This really bugs me actually haha, I will keep trying to investigate why it does this.