Does compose Alpha 04 work with kotlin 1.4.20? (Before you say "Just try it" I'm trying to migrate ...

# compose

[Colton Idle]

Does compose Alpha 04 work with kotlin 1.4.20?

(Before you say "Just try it" I'm trying to migrate an existing project where 1.4.20 solves other issues like kotlinx.synthetics, plus some other kotlin bugs I had, and so it's hard for me to tell who the culprit is which is why I'm just posing the question 😄)

EDIT: Aha! I think I have my answer.

Even though the newest AS canary mentions kotlinCompilerVersion '1.4.10' it also mentions ext.kotlin_version = "1.4.20-M1"

[Colton Idle]

@jim I'm probably missing something here... but any reason why AS canary 13 (released today) ships with

ext.kotlin_version = "1.4.20-M1"

[jim]

Based on your comment/question... it says that inside the new Compose project template I presume?

[jim]

If so, that's probably an oversight, please file a bug.

[Colton Idle]

Correct

[Colton Idle]

But the kotlinCompilerVersion is set to 1.4.10

kotlinCompilerVersion '1.4.10'

so maybe they can be set to different values?

[jim]

nope, I think kotlinCompilerVersion takes precedence/overrides, but in theory, they should always match.

[Colton Idle]

Interesting... the new project > compose app does build... so there's that. 😄

[jim]

well, if they're specifying the kotlinCompilerVersion then that is overriding the ext.kotlin_version so your version is effectively 1.4.10 for the compose module

[Colton Idle]

Interesting. Did not know.

This would be solved by a bug that I already filed I suppose: https://issuetracker.google.com/issues/168225750