A modern programming language that makes developers happier.

kotlinlang

I used to get `"cannot access file, it is used by another process"` errors after adopting compose for my phone app; I saw that IntelliJ addressed it in one of their latter releases, and after it got merged into Android Studio I havent ran into it again.

Unfortunately, the same thing seems to repeat itself now that Im actively working on a wear specific app. Has anyone else ran into this? Any insights?

Do you have a stacktrace, or existing mobile bug report? Hard to avoid guessing just from this one line.

Also, just a guess but is this on windows.

Regardless, raising a bug at <https://issuetracker.google.com/issues/new?component=1077552&amp;template=1598429|https://issuetracker.google.com/issues/new?component=1077552&amp;template=1598429> is probably worth it.

I have never seen this and I am struggling to see how this is going to be a Compose for Wear OS specific issue. If there is a reproducible project might be worth raising against Android Studio

There is already a bug with discussion here: <https://issuetracker.google.com/167701947> and yea some comments suggesting isn’t not compose related. <@U0266GMRPQU> Android Studio team is already looped in the bug, so the best we can do is to wait for their triage. Does cleaning project/invalidating caches help to workaround the issue?

Running on Windows 11.

Thanks <@U02GMQDL9FG> I was just commenting exactly that :grin: My comment in the issue tracker is pretty outdated, but I can see that I was using Electric Eel 3 - and I believe <https://www.reddit.com/r/androiddev/comments/vbi6i4/android_studio_electric_eel_canary_4_now_available/|this> post is about the release that finally fixed it for me (I previously read about IntelliJ fixing the underlying issue).

I can clean &amp; build to fix it, but it happens every other build when working with wear (not phone). If theres anything I can do to test, do let me know.