Useless call on not-null type

Reports calls on not-null receiver that make sense only for nullable receiver.

Several functions from the standard library such as orEmpty() or isNullOrEmpty have sense only when they are called on receivers of nullable types. Otherwise, they can be omitted or simplified as the result will be the same.

Remove redundant call and Change call to … quick-fixes can be used to amend the code automatically.

Examples:

  fun test(s: String) {
      val x = s.orEmpty() // quick-fix simplifies to 's'
      val y = s.isNullOrEmpty() // quick-fix simplifies to 's.isEmpty()'
  }

Locating this inspection

By ID

Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.

UselessCallOnNotNull

Via Settings dialog

Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.

Settings or Preferences | Editor | Inspections | Kotlin | Probable bugs

Suppressing Inspection

You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:

//noinspection UselessCallOnNotNull

More detailed instructions as well as other ways and options that you have can be found in the product documentation:

IntelliJ IDEA 2025.2

Inspection Details
By default bundled with:	IntelliJ IDEA 2025.2, Qodana for JVM 2025.2,

Last modified: 18 September 2025