Has someone ever faced this?
# announcements
p
Has someone ever faced this?
a
Yeah I ran into this recently but the code compiles so I guess it's intellij messing up.
a
I also ran into this using 1.4.30
e
invalidate cache & restart ?
(doing that is like restarting a windows machine - fixes all weird issues)
t
same problem with if, it requires else some case
r
would prob just do an else
p
It's an exhaustive statement, I don't want an else (that's the whole point of sealed classes)
👍 1
l
I have this issue, it appeared after I added a dependency (
:mobuleB
) to my
:moduleA
, where both
:moduleA
and
:mobuleB
depends on
:moduleC
.
p
According to the ticket it happens when you depend from android modules on pure kotlin modules