Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Particular libraries are getting downgraded #118

Open
extmkv opened this issue Sep 14, 2023 · 4 comments
Open

Particular libraries are getting downgraded #118

extmkv opened this issue Sep 14, 2023 · 4 comments

Comments

@extmkv
Copy link

extmkv commented Sep 14, 2023

Describe the issue
Particular libraries are getting downgraded, even if on the TOML it says there's a new update available.
Attached you can see the libraries that are being downgraded.

com.google.android.play:core always downgraded to 1.8.0 from 1.10.3
ok.squareup.okhttp3:okhttp downgraded to 4.9.2 from 4.11.0

Stacktrace
Please run Gradle with the --stacktrace option and share the output in case of a Gradle error.
Screenshot 2023-09-14 at 10 29 08
Screenshot 2023-09-14 at 10 35 02

@hvisser
Copy link
Contributor

hvisser commented Sep 14, 2023

This has been mentioned a couple of times, for example here: #116

Can you try if running the task with --refresh-dependencies helps? I suspect this is some kind of sorting issue in the dependency versions plugin, but I'm not sure. If you have a project that you can provide that reproduces this consistently, that would be great.

This plugin uses the report from the dependency versions plugin, and if that report "downgrades" the dependency, it wil reflect in the TOML file. If you can provide the report.json that would be helpful too, as it lists what the current versions are according to that plugin.

@hvisser
Copy link
Contributor

hvisser commented Dec 22, 2023

The 0.8.2 release has a new way of resolving dependencies, which might fix this problem too (see #125 for more details). Would be great if you could try it on your project!

@beshoy-samy
Copy link

Hey coming back to this even with the current version 0.8.4 issue is still happening

@hvisser
Copy link
Contributor

hvisser commented Apr 18, 2024

@beshoy-samy did you enable the new resolver? Like mentioned in #125? If you want me to take a look, please provide a minimal project as an example that reproduces the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants