You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
--local-engine broken for all x86 Android devices #34279
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-team-archive/engine#9260. I've been able to work around this by locally reverting flutter-team-archive/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.
found that the libflutter.so in the apk looks like it's being selected from flutter/flutter/bin/cache instead of flutter/engine/out
Did this work before @mklim? I'm looking at flutter.gradle before my changes, and it seems the script never read libflutter.so from flutter/engine/out. Only for arm/arm64 debug.
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 -v and a minimal reproduction of the issue.
Activity
blasten commentedon Jun 12, 2019
Did this work before @mklim? I'm looking at
flutter.gradlebefore my changes, and it seems the script never readlibflutter.sofromflutter/engine/out. Only for arm/arm64 debug.flutter/packages/flutter_tools/gradle/flutter.gradle
Lines 166 to 175 in 3d09f93
blasten commentedon Jun 12, 2019
oh I see what happened, in
masterwe run that code regardless if you have a local engine passed to it.github-actions commentedon Aug 29, 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.