Has anyone else ran into composables reverting to ...

# compose

[Zoltan Demant]

Has anyone else ran into composables reverting to an older state, when launching an updated version of an app through Android Studio? More context in 🧵

[Zoltan Demant]

Prefacing this with the fact that this might be studio related, or something completely different, posting here because Ive only ever had it happen when working with compose code (specifically, composables in the UI).

It works like this: I code something UI related and install the application, instead of the tweaked interface Ill see the interface from a release from several hours back. Ive seen it happen with release builds published through the play store, but mostly in my local debugging on an emulator.

Maybe I should just post an issue about this directly, but I thought Id check if anyone else is facing the same issue and whether or not its actually compose related.

[Chris Sinco [G]]

I’m not sure what the exact issue is, but I’ve heard that this can happen sometimes when using the deployment optimizations for Android 11+. You can change it with this setting to “Always install with package manager”.

[Chris Sinco [G]]

cc @Alan Leung

[Alan Leung]

Hi Zoltan.

Have you ever clear application data of your app? That might have impact.

Chris's suggestion could work but understand keeping that on will really slow down your deployment speed.

One thing I would suggestion is keep your current workflow and as soon as you run into this issue, check to make sure the build window is correct. You should see message like:

Task appcompileDebugKotlin

and it should be without the "UP-TO-DATE" at the end.

After that, try uninstalling the app and then re-Run.

If you notice compileDebugKotin isn't ran or a clean reinstall fixes it. Don't hesitate to file a bug or reach out to anyone from Studio or myself.