In these cases, you cannot supply a non-null initializer in the constructor, but you still want to avoid null checks when referencing the property inside the body of a class. It's because you tried to access (via = null) not initialized lateinit variable.įor example, properties can be initialized through dependency injection, or in the setup method of a unit test. I'm thinking of raising a bug report but I'm not sure where to do it. Additionally, we’ll show how to use a secondary constructor with default values. First, we’ll show how to do it with a primary constructor with default values set to null. update the current job using job id to get fresh objectĪnd a when statement and they all throw the same exceptionĪny ideas? This is really weird. In this tutorial, we’ll show how to create a class instance with optional fields. Kotlin.UninitializedPropertyAccessException: lateinit property currentJob has not been initializedĪt .MainViewModel.getCurrentJob(MainViewModel.kt:40)Īt .MainViewModel.getJobsListFromApi(MainViewModel.kt:284)ĬurrentJob = jobsDataList.get(0) //maybe replace with accepted jobs depending on how details is implemented For all constructor parameters, we set a default value: class DataClassWithDefaultValues ( val name: String '', val surname: String '', val age: Number Int.

I have a codeblock with a simple null check that causes an exception Set Default Values in Primary Constructor After that, let’s improve the previous version and eliminate nullability.

Kotlin null default value