Hi I just added `androidx compose runtime` with NO other cha

Question

Hi I just added `androidx compose runtime` with NO other changes to the code base and NO extra added dependencies to my app and enabled the compose compiler and suddenly pressing the back button from one fragment doesn t allow the fragment it s going back to to load properly is this a known bug

Grégory Lureau · Answer

Are you working on Android 13 looks like <https developer android com guide navigation predictive back gesture|predictive back gesture> related

dave08 · Answer

The device I m using is api level 28 but the compileSdk is 33

dave08 · Answer

And nope I don t seem to have that enabled

dave08 · Answer

It seems like for some reason when setting setPopUpTo explicitly in `navigate ` s NavOptions works around the problem but this really isn t supposed to happen

dave08 · Answer

< Ian Lake> Sorry to bother you but any idea what this can be It s a real big blocker for our current migration to compose which is already well under way

Ian Lake · Answer

File an issue against Compose with a minimal sample project that reproduces your issue if you think the Compose Runtime is doing something weird

dave08 · Answer

I don t think I m the first one to use the nav component with compose dependencies I m just wondering if this is some configuration issue What does the compose runtime compiler change that might be messing up the backstack

Ian Lake · Answer

Absolutely nothing hence why a minimal sample project would be helpful

dave08 · Answer

I guess there s no easy workarounds in the meanwhile then I currently have a deadline and this is really getting things stuck I wouldn t mind opening an issue after having finished the work I have before the deadline

dave08 · Answer

Or maybe a way I could pinpoint the problem to get to some workaround Like I said setting setPopUpTo in NavOptions when calling navigate works I m using safeArgs kotlin maybe it s getting messed up there but then I d need to manage the backstack myself I guess

Ian Lake · Answer

I think without seeing your code in a project I don t think anyone can figure out what workarounds might work to a problem only you are experiencing

Ian Lake · Answer

I d look at the dependencies report and see if including the Compose Runtime is upgrading one of your other dependencies fragments etc and try that upgrade independently first

dave08 · Answer

Ok that s an idea thanks

dave08 · Answer

It seems to have been because of kotlinx synthetics once I migrated to ViewBinding it started working

dave08 · Answer

It seems like the compose compiler gets confused about synthetics this should REALLY be pointed out in the migration to compose docs I wasted about three days on this issue < Ian Lake>