question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CPU architecture of the system image arm64-v8a not support

See original GitHub issue

Our project has only ‘armeabi-v7a’ and ‘arm64-v8a’, when I try to run uniittest:

 # Execute unit tests
      - name: Unit Test with Android Emulator Runner
        uses: ReactiveCircus/android-emulator-runner@v2.14.3
        with: 
            api-level: 30
            arch: arm64-v8a
            script: ./gradlew connectedCheck 

It gives me error:

Run ReactiveCircus/android-emulator-runner@v2.[14](https://github.com/dingyishen-amazon/amazon-chime-sdk-android/runs/5577958182?check_suite_focus=true#step:3:14).3
API level: 30
target: default
/Users/runner/Library/Android/sdk/platform-tools/adb -s emulator-5554 emu kill
error: could not connect to TCP port 5554: Connection refused
The process '/Users/runner/Library/Android/sdk/platform-tools/adb' failed with exit code 1
Error: Value for input.arch 'arm64-v8a' is unknown. Supported options: x86,x86_64.

But in your README, it said: CPU architecture of the system image - x86, x86_64 or arm64-v8a. Note that x86_64 image is only available for API 21+. arm64-v8a images require Android 4.2+ and are limited to fewer API levels (e.g. 30).

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:14 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
ychescale9commented, Mar 16, 2022

Try to add target: google_apis. Google stopped publishing system images with default target in recent API levels so the default target no longer works. Maybe we should document this as more people move to test with API 30+.

0reactions
mrk-hancommented, Oct 19, 2022

@dingyishen-amazon That is my understanding! Closing out – please reopen if necessary.

PS: To find every combo available for download, can use sdkmanager --list | grep system-images

Read more comments on GitHub >

github_iconTop Results From Across the Web

Which Android Virtual Device should be used to launch arm64 ...
The console says: PANIC: Avd's CPU Architecture 'arm64' is not supported by the QEMU2 emulator on x86_64 host. The APK was not installed...
Read more >
Support 64-bit architectures - Android Developers
Apps published on Google Play need to support 64-bit architectures. ... If you don't have any arm64-v8a or x86_64 libraries, update your build...
Read more >
Image restore: Error: the processor architecture or OS
Booting from the DVD disk I used to install w10. Getting this error: The system image restore failed. Error details: the processor architecture...
Read more >
Run ARM apps on the Android Emulator
The new Android 11 (Google APIs) x86 system image supports ARM ABIs, while the older Android Oreo system image does not ...
Read more >
Which Android virtual device is based on ARM system image?
Although not recommended due to performance issues, the Android SDK manager still provides ARM system images for the Android SDK emulator:.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found