A modern programming language that makes developers happier.

kotlinlang

For some reason my project insists on using `navigation-compose:1.0.0-alpha08` event though my build.gradle.kts explicitly says `"androidx.navigation:navigation-compose:1.0.0-alpha10"`.
Any hint on how can I troubleshoot this?

is there perhaps some transitive dependency to the alpha08 version in your project ....should be able to see if you run something like `./gradlew :app:dependencies`

`1.0.0-alpha10` isn't quite available on Google Maven yet, FWIW - give it another ~15 minutes

Screenshot 2021-04-07 at 19.50.55.png

It seems `hilt-navigation-compose:1.0.0-alpha01` is holding `navigation-compose` down to `alpha08` ?

has there been an update to `hilt-navigation-compose` which I missed?

<@UJBPFB3SN> it should not be related to alpha10, I was on alpha09 previously but still gradle was also downgrading it to alpha08

I don't see any strict dependencies in the POM/gradle metadata

me neither, I’ll try to dig deeper even though I’m not very experienced at “navigating” in gradle dependency hell (no pun intended :rolling_on_the_floor_laughing: )

My apologies <@UJBPFB3SN>, it is indeed because `alpha10` is not yet reachable on maven.
`hilt-navigation-compose` pulls in `alpha08` so Gradle falls back to that one when it can’t find `alpha10`.

It is weird though, I thought such an issue should fail the build, not silently downgrade a dependency.

This means that also CI builds silently produced a binary with a downgraded dependency…. not cool

Hmm, I've not ever seen that behavior before, odd.