Steps

1. Open any flutter app.
2. Build the engine for android x86.
3. flutter run --local-engine=android_debug_unopt_x86 to an x86 Android device.

Result

E/flutter (10680): [ERROR:flutter/runtime/dart_vm_data.cc(19)] VM snapshot invalid and could not be inferred from settings.
E/flutter (10680): [ERROR:flutter/runtime/dart_vm.cc(241)] Could not setup VM data to bootstrap the VM from.
E/flutter (10680): [ERROR:flutter/runtime/dart_vm_lifecycle.cc(89)] Could not create Dart VM instance.
F/flutter (10680): [FATAL:flutter/shell/common/shell.cc(218)] Check failed: vm. Must be able to initialize the VM.

Cause

It seems like this is a combination of changes to how we select libflutter.so and also flutter/engine#9260. I've been able to work around this by locally reverting flutter/engine#9260. @jason-simmons found that the libflutter.so in the apk looks like it's being selected from flutter/flutter/bin/cache instead of flutter/engine/out. I'm not sure if the APK selection issue is the root cause of the VM failure or if there's some other issue here. Could potentially test for it by copying the locally built cached engine to flutter/flutter/bin/cache and seeing if the error still persists.

/cc @blasten