[Bug] gradle modifications not compatible with gradle version latest Unity uses

[idamaeng]

[REQUIRED] Please fill in the following fields:

• Unity editor version: 6000.0.23f1
• External Dependency Manager version: 1.2.83
• Source you installed EDM4U: UPM (.unitypackage or Unity Package Manager)
• Features in External Dependency Manager in use: All (Android Resolver, iOS Resolver, VersionHandler, etc.)
• Plugins SDK in use: Firebase, Admob, Facebook, etc.
• Platform you are using the Unity editor on: Mac (Mac, Windows, or Linux)

[REQUIRED] Please describe the issue here:

EDM4U adds following information to mainTemplate.gradle:

// Android Resolver Exclusions Start android { packaging { exclude ('/lib/armeabi/*' + '*') exclude ('/lib/mips/*' + '*') exclude ('/lib/mips64/*' + '*') exclude ('/lib/x86/*' + '*') exclude ('/lib/x86_64/*' + '*') } } // Android Resolver Exclusions End

This is not compatible with the gradle version Untiy is using. When triggering the build process Unity is complaining about this and converts this the snippet above to:

// Android Resolver Exclusions Start android { packagingOptions { exclude ('/lib/armeabi/*' + '*') exclude ('/lib/mips/*' + '*') exclude ('/lib/mips64/*' + '*') exclude ('/lib/x86/*' + '*') exclude ('/lib/x86_64/*' + '*') } } // Android Resolver Exclusions End

Which always creates a mainTemplate.gradle.backup files cluttering my project. Please adjust the plugin to use packagingOptions instead of packaging.

Thank you

[google-oss-bot]

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

[idamaeng]

This is a screenshot of the message:

[argzdev]

Hey @idamaeng, thanks for reaching out. It seems that the latest EDM4U 1.2.183 is already using the packagingOptions keyword.

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

Lines 2354 to 2356 in 3e97c8d

	lines.Add("android {");
	lines.Add(" packagingOptions {");
	foreach (var filename in sortedExcludeFiles) {

I wonder if it's being overwritten somewhere else. I tried using any Firebase products from the Firebase Unity Quickstart to test this but so far I'm getting the expected output.

mainTemplate.gradle

// Android Resolver Exclusions Start
android {
  packagingOptions {
      exclude ('/lib/arm64-v8a/*' + '*')
      exclude ('/lib/armeabi/*' + '*')
      exclude ('/lib/mips/*' + '*')
      exclude ('/lib/mips64/*' + '*')
      exclude ('/lib/x86/*' + '*')
      exclude ('/lib/x86_64/*' + '*')
  }

In this case, could you provide me a minimal reproducible example. Or perhaps steps how you were able to reproduce this behavior so I can investigate this further? Thanks a bunch!

[google-oss-bot]

Hey @idamaeng. 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!

[Thaina]

@argzdev I think the problem is opposite

We've detected that your custom Assets/Plugins/Android\mainTemplate.gradle file is using deprecated attributes such as packagingOptions. We can fix this automatically, your current mainTemplate.gradle file will be backed up. Continue?

It seem unity 6 was telling that packagingOptions should not be used. And ths popup instead changed into just packaging