Hi, all. I updated IDEA to 2017.2 yesterday (with the new Kotlin plugin) and IDEA went haywire - bug filed, with a Java Resolver error of some kind (I'd have to look at the bug to remember what the exact name was). Has anyone else experienced similar? Is it something I'm doing wrong, is it related to the JVM I'm using? (I'm using Zulu, for example.)

We just had to downgrade because the latest IDEA / kotlin plugin does not quite import some libraries

yeah, that's what I did. I didn't know if my situation might be unique

Can confirm that reverting to IntelliJ

2017.2.1

with plugin

1.1.3-release-IJ2017.2-2

and kotlin

1.1.3-2

works

@dreamreal ^^^ does this fix your breakage?

hey folks, there seems to be no “convert to expression body” intention for me in kotlin 1.1.4 plugin for Android Studio 2.3.3

the only way I can make it to trigger is making my function one-line:

@User uploaded a file:

but if it’s not, then there’s no warning, and no intention =/

@User uploaded a file:

Are you sure you're putting the caret at the same position both times?

yes, the start of the body, the

{

there’s no such intention in the intentions list even

@User uploaded a file:

only the block body intention

^ @mglukhikh

@adeln "Convert to expression body" is now an inspection with "No highlighting, only fix" default level. It's active on

return

keyword even for multi-liners

@mglukhikh but it’s not, for me, unfortunately (for multi-liners)

@adeln Try this example please:

fun longFun(): Int {
    return run {
        32
    }
}

Set caret inside

return

keyword, press Alt+Enter and check "Convert to expression body" is here or not

alt+enter does not respond =/

(for me it's here)

Which version of IDEA / AS do you have?

but it’s there if I make it one-line

Android Studio 2.3.3

Could you please open your settings and find inspection with "expression body syntax is preferable here"? Which severity does it have?

it’s warning

@User uploaded a file:

@adeln Apologies, in AS 23 this inspection really shows nothing for multi-liners. We'll fix it in

1.1.4-2

or

1.1.4-3

hotfix update

@mglukhikh thanks!