We’ll use the following logic to create the screens:Īs you can see, the presenter is created lazily, because it needs to access the information passed inside of the intent (which will be available after the framework does all the activity-related initialization logic). Then if the user clicks on any of the people’s names, they get a toast greeting that particular person. When the user is finished with sliding, they can open a second screen which will show people based on these criteria (the filter itself is passed inside of the intent).

The first screen is the place where SeekBars can be used to filter out people depending on their age. To illustrate the issue let’s create a simple app. It appeared that when obtaining information from the intent while using assisted injections the intent was null (Spoiler: it had something to do with lazy presenter initializations and method references).Īll of the code can be found in my repository. I ran into this issue when my project suddenly started crashing on one of the screens with a strange NullPointerException (NPE). Method references and lambdas get translated into different java-bytecode which can cause trouble if not handled properly.

Method references and lambdas in lazy propertiesīe careful when using method references and lambdas in Kotlin, especially in combination with lazy properties and classes which are created by the Android framework (activities, fragments, services, etc).

Kotlin by lazy with parameter