googlesamples / unity-jar-resolver

Unity plugin which resolves Android & iOS dependencies and performs version management
Other
1.25k stars 343 forks source link

AndroidResolverDependencies.xml files section is empty #522

Closed alienniki closed 2 years ago

alienniki commented 2 years ago

[REQUIRED] Please fill in the following fields:

[REQUIRED] Please describe the issue here:

Project build from Jenkins. Settings: GvhProjectSettings mainTemplate.gradle MainTemplate gradle Dependencies in repo: AndroidResolverDependencies-repo Files aar in repo: Aar-repo After build: AndroidResolverDependencies files section is empty

In build dir many Cached repo folders Build-dir-ater Build-dir-ater2 Build-dir-ater3 Build-dir-ater4

all folders with no files

If a delete resolved dependencies and Force resolve from Unity and run build, i got success build. If i clone sources from repo and run build, i got failed. Automatic resolve from build not worked correctly.

Logs when invalid build: Gradle Faild

Please answer the following, if applicable:

What's the issue repro rate? 100%

What happened? How can we make the problem occur? Log is big, I can provide the necessary parts

google-oss-bot commented 2 years ago

This issue does not seem to follow the issue template. Make sure you provide all the required information.

paulinon commented 2 years ago

Hi @alienniki,

Thanks for reporting this. In order to identify what's causing this behavior, could you provide a minimal, reproducible example of your implementation along with the complete steps to replicate the issue?

google-oss-bot commented 2 years ago

Hey @alienniki. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

google-oss-bot commented 2 years ago

Since there haven't been any recent updates here, I am going to close this issue.

@alienniki if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.