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:
Related
Hi i'm really struggling to get the Android emulator running on my Mac. What are the steps I need to take to get this working?
I've got Visual Studio 2019 on MacOS Catalina
This is on a new blank Xamarin Forms project
I've tried to go Tools > Device Manager > New Device.
Pixel 3 XL , x86_64, Q 10.
I keep getting this message:
Android emulator component is incomplete therefore the device Pixel 3 XL Q 10.0 - API 29 could not be created. Do you want us to reinstall the Android Emulator?
I've clicked the button to reinstall the android emulator but it doesnt work.
Also tried with OS 8.1 and setting processor as x86 - all the combinations give a similar error messages
When i go to Tools > SDK Manager, the following are ticked:
Android 10.0 - Q
Android SDK Platform 29
Intel x86 Atom_64 System Image
Google APIs Intel x86 Atom_64 System Image
Google APIs Intel x86 Atom System Image
Similar for 9.0, 8.1, 7.1, 7.0, 6.0
Version details
- Version is 8.6.2 (build 6)
Android SDK Manager
Version: 16.6.0.50
Hash: 5901879
Branch: remotes/origin/d16-6
Build date: 2020-04-30 04:01:22 UTC
Android Device Manager
Version: 16.6.0.95
Hash: 45d17b5
Branch: remotes/origin/d16-6
Build date: 2020-04-30 04:01:42 UTC
Xamarin.Android
Version: 10.3.1.4 (Visual Studio Community)
Commit: xamarin-android/d16-6/3a10de9
Android SDK: /Users/user/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
6.0 (API level 23)
7.1 (API level 25)
8.0 (API level 26)
8.1 (API level 27)
I ended up downloading Android Studio, then running the installers from there and then finally went back to VS Mac and installed an emulator device - that seemed to work.
I am able to solve the issue by creating an XML file named entitlements.xml with the following content:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>com.apple.security.hypervisor</key>
<true/>
</dict>
</plist>
Then run the following command
codesign -s - --entitlements entitlements.xml --force /Users/macbookpro/Library/Developer/Xamarin/android-sdk-macosx/emulator/qemu/darwin-x86_64/qemu-system-x86_64
to identify your Android SDK installed folder use Visual Studio> Tools > SDK Manager then check the Android SDK path
I am new in the Xamarin.Forms world and the mobile development and I am trying to understand how the framework mvvmcross works. To do it I have taken the example app TipCalc. I am getting a problem when I start this app on a virtual emulator with Visual Studio 2017. I am getting the following error: "TipCalc.Forms has stopped".
Emulator configuration:
Android_Accelerated_x86_Oreo (Android 8.1 - API 27) 1GB
I have following components installed:
Android SDK Platform 27 and Google Play/APIs Intel x86 Atom System Image are installed.
Android SDK Tools 26.1.1 and Android Emulator are also installed. NDK is not installed. I am getting an error without any detail when I try to install it.
My development environment:
Windows 10 Home
Processor: Intel Core i7-7500U - RAM 8 GB 64Bit-OS
Any idea why it doesn't work? Build and deploy works fine (deployment takes a long).
I newly installed Android SDK (
Android 6.0 (Marshmallow)
Google APIs
Android SDK Platform 23
Intel x86 Atom_64 System Image 23
Google APIs Intel x86 Atom_64 System Image 23
Android SDK Platform 26
Google APIs Intel x86 Atom_64 System Image 26
) and NodeJS 8.11.3, JDK 8.0, Python 2.
I used genymotion simulator for run android app.
when i run the app ( react-native run-android ) it's start and show this error-
i tried 2,3 times newly but got this error every time. how can i fix this?
why recent versions make this type errors?
I have installed the recent Qt 5.1 SDK and Android NDK r8e also platform-tools for API level 10 and 17. When I now try to deploy my application to the Android device (or simulator) I always get the error
Unable to start 'org.qtproject.example.testandroid'.
adb gives me something like
W/PackageManager( 1481): Check ABI compatibility
W/NativeHelper( 1481): Native ABI mismatch from package file
E/PackageManager( 1481): INSTALL_FAILED_CPU_ABI_INCOMPATIBLE
W/PackageManager( 1481): Package couldn't be installed in
The target device is either a Gingerbread Android phone or a simulator with API level 10.
How can I resolve this error? Seems like this is ARMv6 phone and it uses a ARMv7 compiler. I'm running the tools on Linux.
I'm a Google TV developer, and today, shortly after the android sdk 14 was released, I updated everything, from the android sdk to the eclipse ADT. Since then, I can't create a Google TV virtual device. I came to the point where I completely deleted everything and tried to do a fresh install. Here is what happens:
With a fresh download of the android sdk with only Android 3.1 and the Google TV add-on:
$ android list targets
Available Android targets:
----------
id: 1 or "android-12"
Name: Android 3.1
Type: Platform
API level: 12
Revision: 3
Skins: WXGA (default)
ABIs : armeabi
----------
id: 2 or "Google Inc.:Google TV Addon:12"
Name: Google TV Addon
Type: Add-On
Vendor: Google Inc.
Revision: 2
Based on Android 3.1 (API level 12)
Skins: WXGA, 1080p-overscan, 1080p, 720p (default), 720p-overscan
ABIs : x86
$ android create avd -n GTV -t 2
Auto-selecting single ABI x86
Exception in thread "main" java.lang.IllegalArgumentException: ABI Type x86 is unknown for target Standard Android platform 3.1
at com.android.sdklib.internal.avd.AvdManager.getImageRelativePath(AvdManager.java:885)
at com.android.sdklib.internal.avd.AvdManager.setImagePathProperties(AvdManager.java:1637)
at com.android.sdklib.internal.avd.AvdManager.createAvd(AvdManager.java:571)
at com.android.sdkmanager.Main.createAvd(Main.java:1110)
at com.android.sdkmanager.Main.doAction(Main.java:253)
at com.android.sdkmanager.Main.run(Main.java:119)
at com.android.sdkmanager.Main.main(Main.java:102)
Can someone give me a hint on what am I doing wrong?? Or is it a Google problem?
You might try this workaround:
inside of ~/.android/avd/your_avd_name.avd/ create a file 'config.ini'
config.ini should look like:
hw.lcd.density=213
hw.keyboard.charmap=Emulator
skin.name=720.p
skin.path=add-ons/addon-google_tv-google_inc_-12/skins/720p
hw.cpu.arch=x86
abi.type=x86
vm.heapSize=256
hw.ramSize=1024
disk.dataPartition.size=128
image.sysdir.2=platforms/android-12/images/
image.sysdir.1=add-ons/addon-google_tv-google_inc_-12/images/x86/
Update
By default, the android tool creates the AVD directory inside ~/.android/avd/ (on Linux/Mac), C:\Documents and Settings\.android\ on Windows XP, and C:\Users\.android\ on Windows 7 and Vista. If you want to use a custom location for the AVD directory, you can do so by using the -p option when you create the AVD:
http://developer.android.com/tools/devices/managing-avds-cmdline.html