firka/flutter
firka/flutter
5
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Disable selection of the Android ARM64 target platform based on the attached device (#14581)

Browse Source 
The current ARM64 back end generates code that crashes on some devices,
including Pixel phones.  With this change, the android-arm64 target will
not be used by "flutter run" unless explicitly requested.
This is intended as a workaround until we can roll out an engine with the
required Dart VM fix.

See https://github.com/flutter/flutter/issues/14454
This commit is contained in:
Jason Simmons 2018-02-08 17:51:20 -08:00 committed by GitHub
parent 3c9ad811f7
commit fa122f5a6b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
packages/flutter_tools/lib/src/android/android_device.dart
View File

@ -366,15 +366,11 @@ class AndroidDevice extends Device {
return new LaunchResult.failed();
}
BuildInfo buildInfo = debuggingOptions.buildInfo;
if (buildInfo.targetPlatform == null && devicePlatform == TargetPlatform.android_arm64)
buildInfo = buildInfo.withTargetPlatform(TargetPlatform.android_arm64);
if (!prebuiltApplication) {
printTrace('Building APK');
await buildApk(
target: mainPath,
buildInfo: buildInfo,
buildInfo: debuggingOptions.buildInfo,
);
// Package has been built, so we can get the updated application ID and
// activity name from the .apk.