Repository navigation
Unable to run hello_services app on Android Emulator #6136
Description
Steps to Reproduce
Start a Android Emulator with Android studio 2.1.3
pick
Nexus 5X Android 6.0 x86_64 or x86
and run flutter run -v in hello_services folder
Failure [INSTALL_FAILED_NO_MATCHING_ABIS]
0 ms • Package install error: Failure [INSTALL_FAILED_NO_MATCHING_ABIS]
0 ms • 'flutter run' took 23600ms; exiting with code 1.
Flutter Doctor
[✓] Flutter (on Mac OS, channel master)
• Flutter at /usr/local/flutter/flutter
• Framework revision 7f9c8c4b3e (13 hours ago), 2016-09-28 13:09:38
• Engine revision 3551e7a48e
• Tools Dart version 1.20.0-dev.5.0
[✓] Android toolchain - develop for Android devices (Android SDK 24.0.2)
• Android SDK at /Users/jimmy/Library/Android/sdk
• Platform android-24, build-tools 24.0.2
• Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
[✓] iOS toolchain - develop for iOS devices (Xcode 8.0)
• XCode at /Applications/Xcode.app/Contents/Developer
• Xcode 8.0, Build version 8A218a
[✓] Atom - a lightweight development environment for Flutter
• flutter plugin version 0.2.5
• dartlang plugin version 0.6.39
[✓] Connected devices
• Android SDK built for x86 64 • emulator-5554 • android-x64
But I can run with real android device: Nexus 7 (2013) Android 4.4.4
which Android Emulator I can run with hello_services sample?
Activity
eseidelGoogle commentedon Sep 29, 2016
I suspect hello_services gradle files are not configured for running x86. @jason-simmons or @danrubel might know.
eseidelGoogle commentedon Sep 29, 2016
Possibly missing code here:
https://github.com/flutter/flutter/blob/master/examples/hello_services/android/buildSrc/src/main/groovy/FlutterPlugin.groovy#L56
eseidelGoogle commentedon Nov 15, 2016
@jason-simmons does hello_services support multiple architectures?
jason-simmons commentedon Nov 15, 2016
No, it only supports ARM.
We don't currently distribute the "flutter.jar" binary used by the Gradle plugin for any platform other than ARM.
eseidelGoogle commentedon Nov 15, 2016
Rolling hello_services into the default
flutter createflow and fixing issues like this is on our list for early next year. Thanks for the report!kelpenstien commentedon Nov 23, 2016
It appears to be easy enough to take the flutter.jar from under flutter/bin/cache/artifacts/engine/android-arm-release, unjar it, create a new x86 directory under the lib (a sibling to armeabi-v7a). In the x86 directory copy the libsky_shell.so, which should exist under flutter/bin/cache/artifacts/engine/android-x86. Make sure you have the right .so lib (you want it to be ELF 32-bit, Intel 80386). jar it all back up.
Then under local.properties add another entry (this is used by the code that Eric was alluding to earlier)
flutter.jar=/path/to/flutter/bin/cache/artifacts/engine/android-x86/flutter.jar
flutter build clean
flutter run
(all of the above assuming you are talking 32-bit Intel, ofcourse)
Then the sample worked - well for the most part, but that will be a subject for a different post.
FYI- i use the www.android-x86.org build in virtualbox as my emulator - I've always felt that they perform better than real emulators, unless you need sensors, location, etc - and hence the need to try and get this running on x86.
mit-mit commentedon Jan 16, 2017
@jakobr-google FYI
Update gradle example to support x86 in debug mode.
Update gradle example to support x86 in debug mode. (#7606)
github-actions commentedon Aug 31, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.