- 23 Mar, 2022 13 commits
-
-
engine-flutter-autoroll authored
* a7ecc90f2 Remove usages of Android's OnSystemUiVisibilityChangeListener (flutter/engine#30931) * 3b459f014 Roll Dart SDK from e66ff9bf63b6 to b568166d86f3 (1 revision) (flutter/engine#32194) * 72583b3c7 Support software rendering when textures are used (flutter/engine#32178) * 5a319bb4d Roll Skia from c29e37ad4c68 to a11e221a13df (2 revisions) (flutter/engine#32196) * 5017b69e4 Roll Skia from a11e221a13df to 399be2e2118d (1 revision) (flutter/engine#32198) * 53175dbe1 Roll Skia from 399be2e2118d to c47a4037c4c3 (2 revisions) (flutter/engine#32200) * 8a6bd560e Roll Skia from c47a4037c4c3 to 3d7c5436dfdc (1 revision) (flutter/engine#32201) * b46f3d67a Roll Skia from 3d7c5436dfdc to c18c7cbdfe04 (2 revisions) (flutter/engine#32203) * 2fe2f3482 Roll Dart SDK from b568166d86f3 to bf0f84763376 (1 revision) (flutter/engine#32204) * e65893813 Roll Fuchsia Linux SDK from wk98y5LCG... to sMai0ocli... (flutter/engine#32205) * 9354c97dd Roll Fuchsia Mac SDK from Irj8m3Y-7... to daGNAjLwt... (flutter/engine#32207) * 9b546f242 Roll Dart SDK from bf0f84763376 to 81e385566b30 (1 revision) (flutter/engine#32208) * 6ca8335aa Roll Skia from c18c7cbdfe04 to 8bed8855ab41 (1 revision) (flutter/engine#32209) * 6bc6bc16f Roll Skia from 8bed8855ab41 to 51be21eb5aed (3 revisions) (flutter/engine#32210) * 09a74cf5b Roll Dart SDK from 81e385566b30 to b5d0b8fd4fad (1 revision) (flutter/engine#32212) * bc30c91d8 Allow surface implementations to control when the raster cache may be enabled. (flutter/engine#32213) * 68d3782cc Revert "Remove usages of Android's OnSystemUiVisibilityChangeListener (#30931)" (flutter/engine#32217) * c35336328 Roll Skia from 51be21eb5aed to 88f2ab6da0ef (1 revision) (flutter/engine#32214)
-
Darren Austin authored
-
jellynoone authored
-
Flutter GitHub Bot authored
-
Flutter GitHub Bot authored
-
Justin McCandless authored
-
engine-flutter-autoroll authored
-
Danny Tuppeny authored
* Don't terminate Dart process pids from VM Service These processes may be on another device, and in the case of attach the debugee should not be terminated anyway.
-
WenJingRui authored
-
xubaolin authored
-
Chris Bracken authored
In the run_release_test_macos integration test that verifies that a release build of an app can be launched (and quit), xcodebuild from the Xcode install on the macOS bots emits a few info messages about Simulator SDK versions that are irrelevant to the functioning of this test. Ignore these instead of failing the test if they occur. Related: https://github.com/flutter/flutter/pull/100526 Issue: https://github.com/flutter/flutter/issues/100348 (fix) Issue: https://github.com/flutter/flutter/issues/97978 (partial fix) Issue: https://github.com/flutter/flutter/issues/97977 (partial fix) Umbrella issue: https://github.com/flutter/flutter/issues/60113
-
engine-flutter-autoroll authored
-
- 22 Mar, 2022 27 commits
-
-
engine-flutter-autoroll authored
-
xubaolin authored
-
Jonah Williams authored
-
engine-flutter-autoroll authored
-
Danny Tuppeny authored
-
Chris Bracken authored
Adds a test that invokes flutter run in release mode on macOS desktop, waits for successful launch and the flutter command list, then sends the 'q' command to quit the running app. This adds an integration test for https://github.com/flutter/flutter/pull/100504. Issue: https://github.com/flutter/flutter/issues/100348 (fix) Issue: https://github.com/flutter/flutter/issues/97978 (partial fix) Issue: https://github.com/flutter/flutter/issues/97977 (partial fix) Umbrella issue: https://github.com/flutter/flutter/issues/60113
-
Kate Lovett authored
-
Jenn Magder authored
-
Darren Austin authored
-
engine-flutter-autoroll authored
-
LongCatIsLooong authored
-
Anurag Roy authored
-
Taha Tesser authored
-
engine-flutter-autoroll authored
-
Michael Goderbauer authored
-
Kate Lovett authored
-
engine-flutter-autoroll authored
-
engine-flutter-autoroll authored
-
engine-flutter-autoroll authored
-
engine-flutter-autoroll authored
-
engine-flutter-autoroll authored
-
engine-flutter-autoroll authored
-
engine-flutter-autoroll authored
-
Darren Austin authored
-
LongCatIsLooong authored
-
engine-flutter-autoroll authored
-
Chris Bracken authored
Previously, https://github.com/flutter/flutter/pull/100271 enabled building universal macOS binaries by default, but included a bug causing the arm64 App.framework to be built such that the TEXT section containing the app instructions built by gen_snapshot incorrectly contained x86_64 instructions rather than arm64 instructions. When building macOS (and iOS) apps, Flutter builds them in three components: * The Runner application: built by Xcode * The bundled App.framework: built from assembly code generated by gen_snapshot from the application's Dart sources. * The bundled FlutterMacOS.framework: built as part of the engine build and packaged by copying the distributed binary framework from our artifacts cache. Building App.framework consists of the following steps: * For each architecture, invoke gen_snapshot to generate architecture-specific assembly code, which is then built to object code and linked into an architecture-specific App.framework. * Use the `lipo` tool to generate a universal binary that includes both x86_64 and arm64 architectures. Previously, we were building architecture specific App.framework binaries. However, for all architectures we were (mistakenly) invoking the general `gen_snapshot` tool (which emitted x64 instructions, and which is now deprecated) instead of the architecture-specific `gen_snapshot_x86` and `gen_snapshot_arm64` builds which emit instructions for the correct architecture. This change introduces a small refactoring, which is to split the `getNameForDarwinArch` function into two functions: * `getDartNameForDarwinArch`: the name for the specified architecture as used in the Dart SDK, for example as the suffix of `gen_snapshot`. * `getNameForDarwinArch`: the name for the specified architecture as used in Apple tools, for example as an argument to `lipo`. For consistency, and to match developer expectations on Darwin platforms, this is also the name used in Flutter's build outputs. Issue: https://github.com/flutter/flutter/issues/100348
-