Configure `AndroidManifest.xml` / `Info.plist` with the Plugin

[gmitch215]

The generated builds are great, but lack a lot of extensions necessary for proper development.

It would be really beneficial if we could be able to process AndroidManifest.xml or Info.plist manually during the build process.

Specifically:

• I have to check "None" when asked about encryption algorithms every time I upload a build to TestFlight.
• The names of the XCode output are always "app" and not the configured project name.
• I would like to have a different app logo for the play store/app store since pictures can't be transparent (see below)
• Android integrations with the phone's sensors require specific AndroidManifest.xml configurations I have to do manually every time
• Change the Certificate Bundle Identifier for the outputted XCode project that overrides the app-<build architecture>-Release identifier

On a Side Note:

• The output icon1024.png as apart of the assets can't be transparent, and it fails validation on the initial output. This should be seen as a user bug fixed with this enhancement.
• Why is there a separate Debug release type with every Release release type? They seem identical and don't serve a purpose outside of the Debug button in IntelliJ / XCode. This seems to slow down builds by 2x.
• What is the purpose of including iosX64? The only Apple products that have an X64 chip are pre-2020 MacBooks (which can simulate Arm64 iPhones anyways)

[gmitch215]

bump

[gmitch215]

@soywiz bumping again

[ygdrasil-io]

Hello, regarding X64, as far as I know, this is required. Mac does not emulate ARM64; it simulates it. Therefore, it needs the library compiled as some kind of fake iPhone to run it.

Regarding Debug/Release, I guess that it is more to avoid symbol stripping when testing, but I don't know. @soywiz ?

On the other points, they seem legitimate, but nobody has the free time to work on this. However, we are accepting PRs, and contributions are open to everyone.

[gmitch215]

Hello, regarding X64, as far as I know, this is required. Mac does not emulate ARM64; it simulates it. Therefore, it needs the library compiled as some kind of fake iPhone to run it.

Regarding Debug/Release, I guess that it is more to avoid symbol stripping when testing, but I don't know. @soywiz ?

On the other points, they seem legitimate, but nobody has the free time to work on this. However, we are accepting PRs, and contributions are open to everyone.

Cool. I figured that out later after I forgot about the issue, but thanks for the clarification.

I’ll see if I can submit a PR soon.

[soywiz]

Not sure about the Debug Release thing. I was only aware of Debug (faster compilation times and better debugging, slower at runtime) separately and Release (faster at runtime) separately.

As ygdrasil said, PRs are welcome 👍