[Bug] Maintemplate.gradle needs to be merged EDM 1.2.186

[MOST2K2]

• Unity editor version: 6.3 LTS 6000.3.3f1
• External Dependency Manager version: 1.2.186
• Source you installed EDM4U: OpenUPM
• Features in External Dependency Manager in use: Android Resolver, iOS Resolver, VersionHandler
• Plugins SDK in use: Firebase, Admob, Google Analytics, Crashlytics
• Platform you are using the Unity editor on: Windows

Please help to resolve this annoying warning with every build.
Does not matter what i click.
Some other plugin writes to mainTemplate.gradle the old packagingoptions and the AndroidResolver wants to update it then, that works, but with every build it happens again.
This is the snippet:
// Android Resolver Exclusions Start
android {
packagingOptions {
exclude ('/lib/armeabi/' + '')
exclude ('/lib/mips/' + '')
exclude ('/lib/mips64/' + '')
exclude ('/lib/x86/' + '')
}
}
// Android Resolver Exclusions End

[niccolo-hare]

Hi @MOST2K2, thanks for reaching out. This seems to be intended behavior since "packagingOptions" is deprecated, and the JAR resolver is trying to resolve that in order to prevent further issues during runtime. Per my testing, I'm unable to reproduce the issue consistently. I tried building my sample app a few times and the warning only appeared for me once during the first time I built my app, unless I manually changed "packaging" to "packagingOptions" in my project's mainTemplate.gradle file each time before building.

I used the following plugins:

• EDM4U/JAR-Resolver v1.2.186
• Firebase App Core v13.6.0
• Crashlytics v13.6.0
• Analytics v13.6.0
• Admob Mobile Ads SDK v10.7.0

Just to confirm, is the above scenario similar to what you were encountering, or am I missing any additional plugins or details to reproduce the issue correctly?
Lastly, can you confirm if the "Patch mainTemplate.gradle" option is enabled in the EDM4U settings? You can do this by going to Assets>External Dependency Manager>Android Resolver>Settings.

[niccolo-hare]

Hi @MOST2K2, I tried building a sample app a few more times, it looks like disabling the "Patch mainTemplate.gradle" option prevents the warning from appearing. I didn't encounter any issues upon running my test app, so you could just try disabling it as well and see if that helps.

Other than that, I'll go ahead and close this issue since there doesn't appear to be a problem with the EDM4U. But feel free to re-open this if you're still encountering this issue.

[MOST2K2]

I have disabled now the patch mainTemplate.gradle setting, but then the build failed due to ERROR: Gradle failed to fetch dependencies. dont know why. The plugins look similar to mine. Some other android plugin is changing it to packagingOptions before the Unity resolver runs..

[niccolo-hare]

Hi @MOST2K2. Could you try the following as well:

1. Go to Edit > Preferences > External Tools.
2. Untick then tick the JDK, Android SDK, Android NDK, and Gradle checkboxes.
3. Resolve or Force Resolve.

Alternatively, you could consider using the custom Gradle files from Unity instead. I believe you'll be able to find them by going into Player Settings > Publishing Settings, then enable the following:

• Custom Main Gradle Template for mainTemplate.gradle.
• Custom Gradle Properties Template for gradleTemplate.properties.

[MOST2K2]

I did your steps 1-3 and then force resolve, the message still appears. I was hoping the second build will not show the mainTemplate.gradle merge dialog :-(
The custom Main Gradle/Gradle Properties were already enabled in my publishing settings.
The message still appears for every build.
Thanks for your support on this.

[niccolo-hare]

Hi @MOST2K2, thanks for testing this out. Upon checking, there seems to be a new update released for the EDM4U recently (v1.2.187). Just for a quick sanity check, could you try updating to this version and see if the issue goes away?
I'm guessing one of the plugins you're using is causing a conflict with the EDM4U, but I'm not quite certain which. I also tried testing again, though I'm still unable to encounter the warning without manually editing my mainTemplate.gradle file. Unfortunately, it's difficult for me to determine the cause of the error without being able to reliably reproduce the same behavior. Could you confirm if I'm missing any details or plugins? For my testing, I used the following SDKs:

• Firebase v13.7.0
• Admob v13.7.0
• Google Analytics v13.7.0
• Crashlytics v13.7.0
• EDM4U/Jar Resolver v1.2.187

Then I built my project using Unity 6.3 LTS on an Apple M1 pro.

Lastly, I would also appreciate it if you could provide us with an MCVE which can reproduce the issue consistently. This will give us a better idea of what's causing this behavior.

[MOST2K2]

I updaded EDM4U and the issue is still present sadly.
Is the installation method relevant for this issue, for example if i used the .unitypackage of the plugin or installed via EDM4U ui?
I have updated firebase to the latest 13.7.0 but always the same.
Sure i can try to upload a MCVE project, but that takes some time.

[manugildev]

There seems to be already a condition that checks if AGP is higher than 8+ and then uses the right keyword (packaging instead of packagingOptions). I wonder if for some reason it's not working as it should.

unity-jar-resolver/source/AndroidResolver/src/PlayServicesResolver.cs

Line 2357 in 38f31af

if ((new Dependency.VersionComparer()).Compare("8.0", AndroidGradlePluginVersion) >= 0) {

[MOST2K2]

It uses the right one, but some other plugin writes the old packagingOptions at first, then it detects the wrong keyword and replaces it again, with every build ;/