New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App crash with Adobe air 50.2.4 #2976
Comments
Hi @hadisn - can I check why you've closed this as completed? That's a fairly fundamental error .. if you saw it, I'm curious as to what Android OS version you were on? Plus what build type did you create (AAB vs APK, architecture version, etc)? |
I closed it because it works when I choose this Option in Android Studio: Run/Debug Configurations -> Installation Options -> Deploy: Apk from app bundle. Default is Default APK (I think before this worked by default options...) I tested it on multiple OS (Nougat 32 & 64 bit and Android 12). |
But when I test it with android studio virtual device Nexus 5 API 33 i see this error: The app doesn't support ABI architectures of the device. Device ABIs: [x86_64], app ABIs: [armeabi-v7a]. It have only armeabi-v7a version |
How are you building the APK file for your app? The default build of an APK would be to just have the armv7 i.e. armeabi-v7a, but you can configure it to include other ones if you prefer via the app descriptor Or build the bundle which should normally include all the ABIs anyway, unless you've requested it not to. Note that there was a bit of an issue with some of this stuff in 50.2.4.1 so it may be worth ensuring you're using 50.2.4.2? thanks |
@ajwfrost here is what I did: If I do all steps same but just choose AIR 50.2.4.2 there is only armeabi-v7a version. I am using 7zip to open .aab file and navigate to \app-release.aab\base\lib\ and there is only armeabi-v7a folder, but with AIR 50.2.3.6 there are folders: Note that I didn't made any changes anywhere except choosing different AIR version. I really don't understand what happening... Thank you |
Ah, right, yes if you're picking up the AndroidStudioProject and building/deploying from there, then yes it would have had a change due to a bug report where there were unnecessary ABIs being packaged up ..! So to go back to the earlier behaviour, you can add a section into your application descriptor file, within the
thanks |
This works only for AIR 50.2.3.7...not for newer versions of AIR. |
I've noticed this error when we attempt to run a debug build from the generated AndroidStudioProject on a device . I haven't investigated further but let me know if you want more information.
Seems to be related to the architecture we build the project for. |
Ah .. so it looks like there's a priorities/conflict thing going on here:
So, the change we put in to get the proper support working for Of course, Animate doesn't (yet?) have an option to build for x64, which is what would be needed here. There should be a workaround if you wanted to force it to x64: the reason the "all build types" didn't work is because the passed-in value is one of the allowed ones. So if you had:
then this would override the passed-in armv7 request and mean it could then run on the x64 emulator. I'll see again whether we can get the Adobe team to update Animate for this.... :-( |
I don't believe that Adobe will update Animate soon, but I trust that You will find solution for this sooner :). It's ok for me to keep current AIR version in my apps as long as Google don't require to update, I hope we will solve something until then. Thank you |
Hi, I have the same problem and I can't figure it out! I tried 50.2.3.8 and the latest one 50.2.4.2 |
Try AIR 50.2.3.6. |
Hey! I have the same problem with 50.2.4.2. |
Hi If you are trying to create an Android App Bundle via Animate, then it should be possible with 50.2.4.2 to add this to your XML application descriptor file:
But if you're using Animate to create an APK file, you would need to omit
If this still doesn't help, please share the debugging output from ADT when you package the application, which you can get from the AIR SDK Manager "troubleshooting" tab. thanks |
@ajwfrost I am using IntelliJ IDEA, and have added
|
Why can't you test it locally? I think the below command should work if you've got a single device (or emulator) connected?
But also - an AAB file (and an APK) is just a zip file, so you can open it up and look into it to try to find if the native libraries are there. Probably we should also add an "inspect" command to ADT to help with this :-) thanks |
I got this
|
Which version of AIR SDK is that? It's a little old..? (earlier than May 2022, from what I can see....) But with that one, you could still try:
|
is it possible to check AIR sdk version used by |
this worked, hope this time there should be no issues! |
If you did want to use the latest AIR SDK version (50.2.4.2) then there's also a patch version of adt.jar that you can apply on top of that (in the "lib" folder): https://github.com/airsdk/Adobe-Runtime-Support/files/13877375/adt.zip But we'll also try to get this out in a proper release soon.. thanks |
Looks like issue still persist in version 50.2.4.4, or I missed something? Thanks |
Looking at this thread .. I'm not sure what the action was here though..? There's still the restrictions in Animate but if the configurations are set up properly, ADT should generate what's requested? Are you able to clarify the issue you're still seeing? |
App crash
|
Okay yes, so that would normally happen if the correct version of the native library is not found in the APK file. How are you packaging up the APK or AAB file, and do you have any override settings in your "adt.cfg" file or any "buildArchitecture" flags in your app descriptor? |
In adt.cfg I have path to java, I dont have buildArchitecture flags in app descriptor, should I have? I am using adobe animate tu build android studio project, and from android studio I am building aab. |
So from what I can see:
So I think unless you override that "Create Android App Bundle" setting, ADT will just do as it's asked by Animate, which is probably the wrong thing to do! Are you able to change that setting and then check in the generated Android Studio project: Also just to check, what CPU format is the handset/simulator that you're running on? FYI we are still talking with Adobe about the Animate thing and trying to get these options built into their UI.. thanks |
Yes you are right, all 3 thing you mentioned are correct. So point is to set CreateAndroidAppBundle=true in adt.cfg? :) Now it launches app but crash because of distriqt adverts ane, I updated their ane also, need to check this detailed, I have this error:
|
I noticed that manifest file (updated via apm) now contain this few new lines:
but animate gives an error when try to build with these options:
If I remove options above I can build but app crashes... |
Is it possible to move that |
Not possible, I tried but got ton of errors... Here is same issue reported but no response from Distriqt: https://github.com/distriqt/ANE-Adverts/issues/554 |
We are looking into this one. |
Can you please try with the attached ADT jar file, you can unzip this into the "lib" folder over the 50.2.4.5 release. |
@ajwfrost Thanks for that, it correctly builds with the property tag now! |
FATAL EXCEPTION: main
The text was updated successfully, but these errors were encountered: