I have a problem with `val` in `companion object` ...

# kotlin-native

[ribesg]

I have a problem with val in companion object having incorrect value on iOS, anyone saw anything about that? For example I have this in a subclass of UICollectionViewCell (hence the object superclass):

companion object : UICollectionViewCellMeta() {
        const val HEIGHT = 100.0
    }

But when I print the value of HEIGHT anywhere it has a nonsense value, maybe returning a pointer or reading random memory, it returns something like 6e-310. It also does not return the same value every time its read from different instances of the subclass of UICollectionViewCell . Wtf?
Note: Removing const doesn’t change anything. No problem if the val is global, local to the class or a getter (val HEIGHT: Double get() = 100.0)

[Kris Wong]

my guess is that your companion object has not been instantiated

[ribesg]

🤨

[Kris Wong]

subclasses of NSObject aren't accessible from native code...

[ribesg]

@Kris Wong what does that mean

[Kris Wong]

they are marked as inaccessible in the interface header

[ribesg]

Maybe, I still don’t see any link to the issue here

[ribesg]

I don’t understand why companion objects of subclasses of NSObject aren’t instantiated while other companion objects are. I also don’t know if I can force their instantiation

[Kris Wong]

you are saying this only occurs for classes that subclass NSObject

[Kris Wong]

those classes are inaccessible from the native side

[Kris Wong]

__attribute__((unavailable("Kotlin subclass of Objective-C class can't be imported")))
__attribute__((swift_name("FeatureViewController")))
@interface FeatureModuleFeatureViewController : NSObject
@end;

[ribesg]

What native side? Everything is native

[ribesg]

Or maybe, nothing is native. I don’t know what you mean, I’m not using any Objective-C or Swift

[Kris Wong]

you said "having incorrect value on iOS", so I assumed you were accessing it from an iOS app

[ribesg]

I do, but I only have Kotlin code