ajwfrost
commented
6 months ago Hi
I think the first step here would be to set up your build so that, instead of using the temp folder for the gradle build, it uses a specific location and leaves the files there afterwards. So could you please edit your ~/.airsdk/adt.cfg file to uncomment/add a line KeepAndroidStudioOutput=true (or use AIR SDK Manager and select "Keep Android Studio output")
Then after you build next, you'll find a folder hopefully alongside your SWF file called "AndroidStudioProject", and if you then open Android Studio you can select this folder to open.
If you then build within Android Studio (build menu "Make Project") it would be likely that you see the same error. Some suggestions on how to fix it are then mentioned here: https://stackoverflow.com/questions/70467985/after-upgraded-to-androidx-zip-file-already-contains-entry-androidmanifes
It's probably worth double-checking that you only have one "AndroidManifest.xml" file in the whole folder tree there... but assuming that's okay, I would suggest trying to add to your "build.gradle" file (that's under the "app" folder):
packagingOptions {
exclude 'resources.arsc'
exclude 'AndroidManifest.xml'
}which can go immediately after the android { line
If that then works:
- you can generate a signed bundle or apk file from the build menu too, in order to create something to distribute
- please let us know and we can look to incorporate those lines into the build process!
thanks
vinodh143
marchbold
Problem Description
We are encountering the below error while creating the Android package.
Zip file '/private/var/folders/1_/f9053_sd4nqgrznxqjf8dgfr0000gn/T/347f3311-5dc4-4f28-ac2e-a91f1415451d/app/build/outputs/apk/release/app-release.apk' already contains entry 'AndroidManifest.xml', cannot overwrite
We have attached the full error log with this issue. Below are the configurations we are using to create the APK:
Java Version: 11 HarmanAirSDK: 50.2.4.4 Gradle Version: 7.0 Android Target SDK: 33 Android Build Tool: 33.0.0 Build Type: release Log File: adt.log We are stuck and not able to proceed. Could you help us find a solution?