it can lead to accidental crash
# android
d
it can lead to accidental crash
d
I know 🙂 But the properties are generated in Kotlin, so they can be done more stricty (
@Nullable
). There is a ticket for it. https://youtrack.jetbrains.com/issue/KT-18012
k
diego-gomez-olvera: Right. Platform types like Yan said. AFAIK, it doesn't do any strict checking of whether or not that property actually exists. Also, it was once non nullable, but that was quickly relaxed. Keep in mind that the view, even if present, are only available between onviewcreated and onviewdestroyed. So they can indeed be both nullable and not