[Bug] Android Resolver: Resolution stuck at 100% despite no libraries was downloaded

[Watcher3056]

[REQUIRED] Please fill in the following fields:

• Unity editor version: 2021.3.13f1
• External Dependency Manager version: 1.2.175
• Source you installed EDM4U: .unitypackage
• Features in External Dependency Manager in use: Android Resolver
• Plugins SDK in use: FacebookSDK, Applsflyer, Appmetrica, Applovin MaxSDK(Mediations: Fb, Admob, Unity, IronSource, Fyber, Vungle, Pangle, Inmobi, Adcolony, HyprMx, Maio, Tapjoy, Mintegral, Yandex)
• Platform you are using the Unity editor on: Windows

[REQUIRED] Please describe the issue here:

Click Android Resolver >> Resolver or Force Resolve - it will stuck at 100% like this

Please answer the following, if applicable:

What's the issue repro rate? 100%

What happened? How can we make the problem occur? This could be a description, log/console output, etc.

If you have a downloadable sample project that reproduces the bug you're reporting, you will likely receive a faster response on your issue.

[google-oss-bot]

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

[paulinon]

Hi @Watcher3056,

Could you try if enabling both Custom Main Gradle Template and Custom Gradle Properties Template from your Player Settings > Publishing Settings makes any difference? If not, please provide a minimal, reproducible example so that we could identify the cause of this behavior.

[Watcher3056]

1 hour passed, some libraries downloaded, but not sure if process is complete. Resolver blinks with some text periodically. Process is unclear, you should fix at least this. I will check again with options you mentioned. https://user-images.githubusercontent.com/53340768/230424363-59bd0f09-20d5-4d57-89c6-be75ec94a77c.mp4

[Watcher3056]

Enabled both Custom Main Gradle Template and Custom Gradle Properties Template, now resolution seems to have no effect at all, no libraries downloaded, process completed instantly

[Watcher3056]

Tab back to project and libraries appeared somewhy.

[Watcher3056]

Its not reliable when libraries downloads or not. Please reproduce it. Need help.

[paulinon]

Hi @Watcher3056,

I see that the resolution has succeeded. Enabling both Custom Main Gradle Template and Custom Gradle Properties Template in Player Settings helps resolves the dependency conflict by simply modifying a file, which prevents resolution from taking too long.

I'll be closing this for now. Let me know if an issue arises or if this solution isn't suitable with your use case so this could be reopened.

[Watcher3056]

Hi again, sorry but in my case resolution does not seems to have effect. Plugins/Android folder has no libraries and my build crashes because of method not found exception, which is means there is no suitable library was found. I deleted libraries in Plugins/Android and tried to launch Resolve and Force Resolve - it instantly says resolution succeeded but nothing was downloaded and libraries still missing.

I found similar issue here: https://answers.unity.com/questions/1897514/android-resolve-takes-too-long-hours.html

UPD: Resolution with such settings should be instant and libraries will be not created in Plugins folder which is ok.

[paulinon]

Hi @Watcher3056,

Apologies for the radio silence here. Could you try if updating the Unity editor version (the latest LTS version as of writing is 2021.3.24f1) makes any difference? If it doesn't, it would be helpful if you provide a minimal, reproducible example as this could be used as a baseline for troubleshooting.

[google-oss-bot]

Hey @Watcher3056. 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]

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

@Watcher3056 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.