Develop Reference

Android Emulator's ABI list is empty

I was able to successfully run an ARM APK on the following Android 12 (API 31) emulator and today I noticed that it has ABI List that includes both x86 and ARM:
At the same time, I was unable to run my ARM APK on Android 13 (API 33) emulator and got INSTALL_FAILED_NO_MATCHING_ABIS error. That emulator has empty ABI List:
What does this mean? Does it mean that something is wrong with my Android Studio installation?
My Android Studio version:

I can't install from Delphi 10.3.3 Android 32/64 on Android 11 device

I can't install a Delphi 10.3.3 Android 32/64-bit app on an Android 11 device.
I'm getting this error:
Performing Streamed Install.
adb: failed to install H:\Mis documentos\Embarcadero\Studio\Projects\x2\Android64\Debug\TabbedwithNavigation\bin\TabbedwithNavigation.apk: Failure [INSTALL_FAILED_INVALID_APK: Scanning Failed.: Package /data/app/~~DFtbsqRNmIVX6qX7FlFJWg==/com.embarcadero.TabbedwithNavigation-0B50fmmgUibrpy3czY56dg==/base.apk code is missing]
My configuration is:
Delphi 10.3.3
SDK android 25.2.5 32/64-bit (android 26) stock
Android SDK 26.1.1 32/64-bit (Android 29)
In all cases, I receive the same error.
I'm doing:
\File\New\Multi-device application-Delphi
Select Tabbed
Run with debug

Installation failed on deploying Xamarin.Forms APK to customer’s devices

I am experiencing an issue of installation of Xamarin.Forms Aapp into customer’s Android devices;
APK installation failed on Android devices under Android 9.0
I developed a Xamarin.Forms app with Visual Studio 2019 and set target android versions as the followings;
Compile Using Android Version (Target Framework) - 9.0
Target Android Version - 9.0
Minimum Android Version - 5.0
I set android options as the followings and built release mode, archived and signed output APK.
Use Share Runtime - off
Bundle assemblies into native code - on
aapt2 - on
Multi-Dex- On
Dex Compiler - D8
Code Shrinker - None
Enable developer instrumentation (debugging and profiling) - on
AOT - On
LLVM Optimization Compiler - On
Enable Startup Tracing - On
The output APK was installed well on my test Android 5.0.1 device.
However, it was not installed at other android devices under Android 9.0. It was installed well on Android 9.0 devices.
I found that my test Android 5.0.1 device had Xamarin.Android API-28 Support module, because I had executed debug mode before. When I removed it, I could reproduce the issue – installation of my app has failed.
My app uses some APIs of Android 7.0 and 9.0, but I added checking Android versions and so it works on Android 5.0.1 as well as Android 6/7/8/9.
I suspect that Xamarin.Android API-28 Support module may be required to install my app.
However, it is no sense that users installs Xamarin.Android API-28 Support module first, and I cannot find the APK file of Xamarin.Android API-28 Support module.
How can I make my app installed to Android 5.0.1 and higher without installation issues?

NDK Debug for Nexus 9 arm64-v8a build not working for eclipse

I keep getting the following error:
[2015-01-23 19:27:47 - NativeTestApp] Unable to find a compatible ABI
[2015-01-23 19:27:47 - NativeTestApp] ABI's supported by the application: armeabi
[2015-01-23 19:27:47 - NativeTestApp] ABI's supported by the device: arm64-v8a, null
when my Application.mk is empty. When I have an Application.mk and I set APP_ABI to arm64-v8a, all it says is:
[2015-01-23 19:33:27 - NativeTestApp] Unknown Application ABI:
[2015-01-23 19:33:27 - NativeTestApp] arm64-v8a
[2015-01-23 19:33:27 - NativeTestApp] Unable to detect application ABI's
Seems to me like the application wants to compile armeabi but the target is arm64. It works fine when not running as native debug.

The issue was an inherent bug with ndk-r10d and previous versions. This has been fixed with ndk-r10e, although it still does not work with eclipse since eclipse has its own ndk plugins. Google apparently intends on having ndk-gdb compatibility with the next Android Studio release.
EDIT: Sources:
https://developer.android.com/ndk/downloads/index.html#rel
"Fixed ndk-gdb for 64-bit ABIs. (Issue 118300)".

Native C/C++ debugging on 64-bit CPU equipped devices is not supported by the latest official version of ADT plugin for Eclipse (23.0.7).
I managed to update the sources to get the NDK debugging work on arm64-v8a (Nexus 9).
Try out this patched version: https://github.com/khaledev/ADT

How Do You Configure IBM Worklight Studio to Build for ARM and MIPS devices?

I'm using Worklight Studio Developer Edition plugin for the Eclipse IDE Juno JAVA EE to test building hybrid apps and I'm trying to build and deploy to an Android MIPS based device. ARM devices and emulators work fine but the MIPS device will not install.
I receive the following errors from the console and logcat.
[2013-03-05 00:27:36 - Project1App1Android] Installation failed due to invalid APK file!
[2013-03-05 00:27:36 - Project1App1Android] Please check logcat output for more details.
[2013-03-05 00:27:36 - Project1App1Android] Launch canceled!
03-05 00:28:18.607: W/PackageManager(90): Native ABI mismatch from package file
I think the problem is the build is not including MIPS support for older device SDKs like Froyo 2.2.1 which is on the devce I'm having problems with. How can I configure Worklight to build for ARM and older MIPS? I have the MDS Eclipse plugin for PhoneGap installed as well and it builds and deploys to the same MIPS device without any problems.

Android applications are built and run with help of Android Development Tools. The unified support for all processor architectures is included in Release 21 of Android SDK. You can read the announcement here: Official Android SDK, Installation instructions

This is outside of the Worklight scope. You should open the Android SDK Manager, and make sure to install any support by Google related to MIPS and/or ARM.
The generated .apk is generated via Google's Android Developer Tools.