A customer says my app doesn’t run on Marshmallow. I don’t have a device running marshmallow. I am trying to install the app to an emulator but am running into INSTALL_FAILED_NO_MATCHING_ABIS error. I get this error with the original apk, and if I build with the latest daily build of corona. Any ideas or workarounds besides finding a physical Marshmallow device?
Hi bangerlm,
As we detailed in our blog post on Android Studio support,
- Since Corona is built with the ARMv7 architecture in mind, be sure to only use system images with ABI: armeabi-v7a.
That being said, when you set up your Android emulator, be sure to use a System Image with ABI “armeabi-v7a”.
Thank you! I had not seen that article. That did the trick.
Unfortunately the ARMv7 emulator is so slow as to be useless. The x86 emulators work great, but they’re not compatible with Corona builds. I’ll just stick to actual devices.
You can use the ARMv7 emulator for smaller projects, but once you get to the size of a real app, it’s definitely “so slow as to be useless”. Depending on how your big app is structured, you may be able to isolate a piece of it into something that can be tested in the emulator.
We definitely don’t advocate emulator testing as a replacement for testing on an actual device, but it is handy for situations like bangerlm’s.
Yes, it took almost an hour for the emulator to startup and get the app loaded, but I was able to verify that my app did run, and was able to do a rudimentary run through to verify.
Hi bangerlm,
As we detailed in our blog post on Android Studio support,
- Since Corona is built with the ARMv7 architecture in mind, be sure to only use system images with ABI: armeabi-v7a.
That being said, when you set up your Android emulator, be sure to use a System Image with ABI “armeabi-v7a”.
Thank you! I had not seen that article. That did the trick.
Unfortunately the ARMv7 emulator is so slow as to be useless. The x86 emulators work great, but they’re not compatible with Corona builds. I’ll just stick to actual devices.
You can use the ARMv7 emulator for smaller projects, but once you get to the size of a real app, it’s definitely “so slow as to be useless”. Depending on how your big app is structured, you may be able to isolate a piece of it into something that can be tested in the emulator.
We definitely don’t advocate emulator testing as a replacement for testing on an actual device, but it is handy for situations like bangerlm’s.
Yes, it took almost an hour for the emulator to startup and get the app loaded, but I was able to verify that my app did run, and was able to do a rudimentary run through to verify.