The newest update seems to have changed some depen...

# refreshversions

[dave08]

The newest update seems to have changed some dependency names... so Android Studio didn't load up the new definitions for some reasons, and code complete was still using the old version even after cleaning the build and .gradle folders a few times... so I had to guess what they were changed to 🙈... it's a good thing there was the new list on the site...

[jmfayard]

sounds important
do you mind to go back in your git history,
create a branch from before the update
update and see what failed?

[dave08]

implementation(AndroidX.lifecycle.runtimeKtx)
implementation(AndroidX.lifecycle.runtime.ktx)

[dave08]

testImplementation(Testing.kotestExtensions.robolectric)
testImplementation(Testing.kotest.extensions.robolectric)

[dave08]

testImplementation(Testing.kotestExtensions.wiremock)
testImplementation(Testing.kotest.extensions.wiremock)

[jmfayard]

ah I know about this one, no way around it, kotest did a breaking change in a recent version

[dave08]

Yeah, but I'm using the one under 5.x... I still didn't have the time to update. I hope this didn't upgrade me w/o knowing...?

[jmfayard]

what it was supposed to do is to inline testImplementation(Testing.kotestExtensions.robolectric)
as testImplementation("io.kotest:whateveritwas:_")
apparently that's not working
That was I would do manually if I was you

[jmfayard]

I created an issue
https://github.com/jmfayard/refreshVersions/issues/607

[dave08]

Oh... so that was supposed to be covered... thanks for opening the issue! And keep the nice work going... 😉!

[louiscad]

The exact issue is unclear.
The replacement mechanism never changes the maven coordinates, it only does straight replacements with built-in dependency notations if there is a match for the underlying maven coordinates, otherwise, it replaces with the corresponding string literal and adds comments instead.

[louiscad]

Also, please @dave08 submit issues yourself with the exact details, this channel is more a general discussion than when you have an actual issue that we prefer to have on GitHub next to any other one.

[jmfayard]

Dave, I think the reason might be that the version was changed
Please comment whether that's the case
https://github.com/jmfayard/refreshVersions/issues/607#issuecomment-1245942206