[Bug] Unity removes namespace in custom main gradle template

[derwaldgeist]

• Unity editor version: 2022.3.62f1
• External Dependency Manager version: 1.2.176
• Source you installed EDM4U: .unitypackage (IIRC)
• Features in External Dependency Manager in use: Android Resolver, iOS Resolver
• Plugins SDK in use: Facebook
• Platform you are using the Unity editor on: Mac

I have a custom Gradle template that contains this line:

namespace "com.unity3d.player"

in this section:

// Android Resolver Exclusions Start
android {
	namespace "com.unity3d.player"
  packagingOptions {
      exclude ('/lib/armeabi/*' + '*')
      exclude ('/lib/mips/*' + '*')
      exclude ('/lib/mips64/*' + '*')
      exclude ('/lib/x86/*' + '*')
      exclude ('/lib/x86_64/*' + '*')
  }
}
// Android Resolver Exclusions End

Everytime I do the first Android build, Unity or Android resolver removes this namespace. Which then causes the gradle build to fail. If I re-add this line and start another build, everything runs through smoothly.

What is the reason for this behavior, and how can I resolve this?

What's the issue repro rate? 100%

[niccolo-hare]

Hi @derwaldgeist, thanks for reaching out. I tried setting up a sample app to take a look at the behavior, but I couldn't reproduce it. Could you try updating your EDM4U and Firebase SDK version(s) to the latest available and see if that helps resolve the issue?

Otherwise, I'm not quite sure what's causing the issue. Any chance you could share an MCVE so we can investigate this further?

[derwaldgeist]

@niccolo-hare Thanks for the feedback. I'm not using the Firebase SDK, just push notifications.

I now moved this line

namespace "com.unity3d.player"

out of the // Android Resolver Exclusions Start block, and this worked.

However, you can't place it anywhere. If I moved in a separate block before

// Android Resolver Exclusions Start

I ended up with two "Exclusions" blocks. One where it originally was, and a new one at the top of the file.

I had to place it in the android block at the very end of the file. This worked.

[niccolo-hare]

Thanks for the clarification, @derwaldgeist . I was able to reproduce this by using the "Reimport All" button under the Assets tab. Not sure why this happens, so I'll be checking with our engineers and will get back to you when I have more information.

In the meantime, I think you can continue using the other android block as a workaround.

[derwaldgeist]

Thanks for the feedback @niccolo-hare.

Yes, this only happens on the initial initialization, e.g., if you removed the contents of the /Library folder. We do this regularly before we create production builds, since we had cases earlier that files were missing in them, like addressables used for i18n.

And yes, the workaround works. I assume that the "namespace" was actually not placed in that section by the Android resolver itself but Unity, maybe in some update.

[niccolo-hare]

Hi @derwaldgeist , thanks for the confirmation. I discussed this with our engineers, and it looks like this is working as intended. I believe the idea behind the "// Android Resolver Exclusions..." block is that the resolver uses it to add or remove the parts inside them as needed. So if you have something that you would like to preserve, you need to put it outside of this block.

Hope that clears things up. I'll go ahead and close this thread for now, but if you'd like us to reopen the thread or if there's anything else you'd like us to look into please let us know. Thanks!