Lazy initialized objects are always created

Question

In some case my broadcast receiver is not required and so need to check if the receiver is null or not but somehow this object is not null even if not using it and causing crash.

private val myBroadCastReceiver by lazy {
   MyBroadcastReceiver()
}
if(myBroadCastReceiver != null) unregisterReceiver(myBroadCastReceiver)

Arjun · Accepted Answer · 2021-03-01 15:42:00Z

5

when you are trying null check, its initialised and thus it not null. Try this this instead of lazy.

private var myBroadCastReceiver : MyBroadcastReceiver? = null

or try this answer Kotlin: Check if lazy val has been initialised

edited Mar 1, 2021 at 15:42

answered Feb 21, 2019 at 16:36

Arjun

3582 silver badges14 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Arjun Over a year ago

stackoverflow.com/questions/36623177/…\You can go through this to know which is appropriate to use lateinit or lazy initialisation

Zoe - Save the data dump Over a year ago

This needs to be a var though

Arjun Over a year ago

i changed val to var

Rafa · Accepted Answer · 2019-02-22 02:29:22Z

4

Because you declare myBroadcastReceiver as Lazy, that means that you won't use it until you call MyBroadcastReceiver(). Which you do in your if statement.

So if you check it that way, it won't be null, because you actually execute MyBroadcastReceiver() here if(myBroadCastReceiver...)

edited Feb 22, 2019 at 2:29

answered Feb 21, 2019 at 16:35

Rafa

3,3695 gold badges42 silver badges76 bronze badges

Collectives™ on Stack Overflow

Lazy initialized objects are always created

2 Answers 2

3 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

3 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related