googlesamples / googlesamples/unity-jar-resolver

[Android] (Force) Resolve doesn't refresh the dependncies.

Open
#312 4 comments 0 reactions 0 assignees View on GitHub
type: feature request
Dominant language
C#
Stars
1.5k
Forks
371
Avg merge
14h 21m
Merged PRs (30d)
3

Description

When (force) resolving the Android dependencies, the (global) gradle cache is being used and not refreshed.

I've come across this issue when we've rebuilt one of our own in-house android plugins and changed the dependency of this plugin, without bumping the version of this plugin.
I'm aware it's not a good practice, to not bump the version, but this can also occur in SNAPSHOT builds, which wouldn't change versions and actually serve the purpose of being (re)built many times over.

Gradle has support to refresh the dependencies when adding the argument `--refresh-dependencies`, perhaps this argument should be added when (force) resolving for android?
(I think this can be accomplished by changing https://github.com/googlesamples/unity-jar-resolver/blob/master/source/PlayServicesResolver/src/GradleResolver.cs#L498 and use `"--refresh-dependencies"` instead of `null`)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.