Required manifest additions change apks ABIs

[yvant]

To integrate this ANE, I had to add these lines to the manifest:

<gradleVersion>8.9</gradleVersion>
<androidGradlePluginVersion>8.7.3</androidGradlePluginVersion>
<manifestAdditions><![CDATA[<manifest android:installLocation="auto"> => <manifestAdditions><![CDATA[<manifest android:installLocation="auto" xmlns:tools="http://schemas.android.com/tools">

Because of this, the ABIs of my APKs (ARM7 & ARM8) are different and make them not publishable for Google, as seen in the screenshot.

Is it ok to remove these lines from the manifest?

[marchbold]

Apologies I missed this question. Can you elaborate on the difference and the method you are using for packaging?

Have you tried using a bundle rather than 2 separate apks?

[yvant]

No worries, I ended up removing this line / package and it went back to normal. I didn't use any specific way for compiling, the only differences are with or without these lines and adding the ANE or not.
I didn't try to switch to AAB because I'm not sure what that would change to my process / what kind of issues it could add.

[marchbold]

Generally it simplifies the upload and packaging process, delivering one bundle for all architectures but if you have a process you are comfortable with it's up to you 👍