airsdk / Adobe-Runtime-Support

Report, track and discuss issues in Adobe AIR. Monitored by Adobe - and HARMAN - and maintained by the AIR community.
200 stars 11 forks source link

Unable to create app bundle aab/apk file using AIR SDK 33.1.1.633 -Android #1266

Open idzdigital opened 2 years ago

idzdigital commented 2 years ago

Hi, image I am using AIR SDK 33.1.1.633 for Android and min target sdk is 21 and max is 30 ,while creating app bundle from publish settings ,I am getting this error, Can you please help with this. Error creating files.Unknown error. Unexpected failure: Unable to rename lib -> jnilibs java.io.|OException: Unable to rename lib -> jnilibs at com.adobe.air.apk AABOutputStream.addCaptiveRuntimeLibs{ ‘AABOutputStream.java) at com.adobe.airapk AABOutputStream.addpplicationDescript or(AABOutputStream,java) at com.adobe.air ApplicationPackageraddSpecialiles(Applicatio nPackager.java) at com.adobe.air-ApplicationPackager.createPackage(Application Packager.java) at com.adobe.ai.apk AABPackager.createPackage(AABPackager ja va) at comadobe.air ADT.parseArgsAndGo(ADT Java} at comadobe air ADT.run(ADT java) at comadobe air ADT main(ADT,java) I have also attached adt.cfg file image below, Thanks in advance. image

ajwfrost commented 2 years ago

Per https://github.com/airsdk/Adobe-Runtime-Support/discussions/1265#discussioncomment-1478229 - something may be holding open a reference to the previous jniLibs folder which means we're not able to overwrite it (we're extracting files from other locations which means they end up in a "libs" folder automatically, but Gradle needs them to be in "jniLibs" hence the rename).

If it is a file reference that had prevented the clean-up of the earlier build, then it may cause other later problems, so we're better off just preventing this build from going ahead and notifying you so you can do the necessary clean-up...

thanks

idzdigital commented 2 years ago

hi I have tried solving using above methods, but its giving same error, also tried to build aab using adt command, but giving same error. Thanks

romaniom commented 2 years ago

hi I have tried solving using above methods, but its giving same error, also tried to build aab using adt command, but giving same error. Thanks

KeepAndroidStudioOutput=true

Hi! I had this error. I'm just doing aab without the participation of android studio.

KeepAndroidStudioOutput=true

Now I have an apk and I just change its extension manually to aab. And everything works, Google Play accepts it.

ajwfrost commented 2 years ago

So just to check: a) manual deletion of the "AndroidStudioProject" folder before building, does not solve it? b) but commenting out the "KeepAndroiStudioOutput" flag (or setting to false) does solve it?

@idzdigital I'm really curious why it's not working - maybe some file handle being left open or async command not completing! but rather than dig further, it may just be that we should directly create/copy things into 'jniLibs' rather than using 'libs' before renaming it all...

shindeharshu26 commented 2 years ago

I am getting the same issue as @idzdigital and I have also tried all the solutions mentioned above, but to no avail.

a) manual deletion of the "AndroidStudioProject" folder before building, does not solve it? I couldn't find the file "AndroidStudioProject" anywhere in my computer as I have not used the Android app studio to make any android project but have used it only to download the Android sdk which was required while making an aab file.

b) but commenting out the "KeepAndroiStudioOutput" flag (or setting to false) does solve it? I even tried this solution, but again, the same error persisted

ajwfrost commented 2 years ago

@shindeharshu26 are you able to confirm what version of the SDK you're using? The recent updates included some changes so we didn't actually need to do this renaming any more, so it should mean you don't see the error.. are you able to update?

thanks

shindeharshu26 commented 2 years ago

@ajwfrost, I am using version 33.1.1.713 of the AIR SDK and even then I am getting the same error. I am attaching an image of my adt.cfg file for reference

adt_cfg
ajwfrost commented 2 years ago

Thanks @shindeharshu26 - I've just double-checked and 33.1.1.713 does still contain the rename command from "lib" to "jniLibs", sorry I thought that had all been sorted out! We've not been unable to reproduce the problem but I think we should be able to work around it .. will perhaps upload a test build here if you're able to then confirm that it helps, that would be very useful for us! many thanks

shindeharshu26 commented 2 years ago

Okay @ajwfrost, no problem. I will test the test build when you upload it here and let you know about its working.

Thanks

ajwfrost commented 2 years ago

Hi Here you go: https://transfer.harman.com/message/cAp7CQEjo2ktNo1q34hZ1F thanks

shindeharshu26 commented 2 years ago

Hey, @ajwfrost, I replaced the adt.jar file in the AIR SDK folder with the adt.jar file you had sent and published the apk. The apk was created without the error - "Unable to rename lib -> jniLibs" and then, I just renamed the .apk extension to .aab extension manually in order to "actually" save the file as an aab file.

These were the steps that I followed. So, as I did not get the error of renaming the files again, I think that the issue might have been solved.

ajwfrost commented 2 years ago

Great, thanks - this should be in a release soon...

gametornado commented 2 years ago

Can you please send the adt.jar again? The link is no longer available.

ajwfrost commented 2 years ago

@gametornado can you use either of the below releases? These have the change in it for this one... https://airsdk.harman.com/download/33.1.1.731 https://airsdk.harman.com/download/33.1.1.743

thanks