Okay. Thanks. Is there a way to get around this? I don't want to expose my field to Java code. I thought this was a bug.

okkero: The backing field of a lateinit property gets the visibility of the property setter.

Why was this decision made?

To satisfy both requirements: - expose the field of lateinit for DI frameworks by default, - still provide the way not to expose it if not required

So there is no way to expose the setter of a lateinit property without exposing the backing field?