1. 27 Oct, 2023 1 commit
    • Andrew Kolos's avatar
      give `throwsToolExit` a more useful description (#136694) · 1328997b
      Andrew Kolos authored
      Fixes https://github.com/flutter/flutter/issues/136698.
      
      Alters how `throwToolExit` creates its matcher. This results is an improved description of the matcher.
      
      The mismatch description isn't improved by this, but I writing an entirely custom matcher to fix this isn't ideal either. We can instead mitigate the issue by augmenting the `toString` implementation of `ToolExit` to include the exit code, if it is non-null.
      
      With these changes, the first few lines of output from a test would look like this:
      
      ```
      Expected: throws <Instance of 'ToolExit'> with `exitCode`: <42> and `message`: contains 'message'
        Actual: <Closure: () => Never>
         Which: threw ToolExit:<Exit code: 41232. Error: message>
      ```
      1328997b
  2. 26 Sep, 2023 1 commit
  3. 21 Sep, 2023 1 commit
  4. 10 Sep, 2023 1 commit
    • Daco Harkes's avatar
      Native assets support for MacOS and iOS (#130494) · aa36db1d
      Daco Harkes authored
      Support for FFI calls with `@Native external` functions through Native assets on MacOS and iOS. This enables bundling native code without any build-system boilerplate code.
      
      For more info see:
      
      * https://github.com/flutter/flutter/issues/129757
      
      ### Implementation details for MacOS and iOS.
      
      Dylibs are bundled by (1) making them fat binaries if multiple architectures are targeted, (2) code signing these, and (3) copying them to the frameworks folder. These steps are done manual rather than via CocoaPods. CocoaPods would have done the same steps, but (a) needs the dylibs to be there before the `xcodebuild` invocation (we could trick it, by having a minimal dylib in the place and replace it during the build process, that works), and (b) can't deal with having no dylibs to be bundled (we'd have to bundle a dummy dylib or include some dummy C code in the build file).
      
      The dylibs are build as a new target inside flutter assemble, as that is the moment we know what build-mode and architecture to target.
      
      The mapping from asset id to dylib-path is passed in to every kernel compilation path. The interesting case is hot-restart where the initial kernel file is compiled by the "inner" flutter assemble, while after hot restart the "outer" flutter run compiled kernel file is pushed to the device. Both kernel files need to contain the mapping. The "inner" flutter assemble gets its mapping from the NativeAssets target which builds the native assets. The "outer" flutter run get its mapping from a dry-run invocation. Since this hot restart can be used for multiple target devices (`flutter run -d all`) it contains the mapping for all known targets.
      
      ### Example vs template
      
      The PR includes a new template that uses the new native assets in a package and has an app importing that. Separate discussion in: https://github.com/flutter/flutter/issues/131209.
      
      ### Tests
      
      This PR adds new tests to cover the various use cases.
      
      * dev/devicelab/bin/tasks/native_assets_ios.dart
        * Runs an example app with native assets in all build modes, doing hot reload and hot restart in debug mode.
      * dev/devicelab/bin/tasks/native_assets_ios_simulator.dart
        * Runs an example app with native assets, doing hot reload and hot restart.
      * packages/flutter_tools/test/integration.shard/native_assets_test.dart
        * Runs (incl hot reload/hot restart), builds, builds frameworks for iOS, MacOS and flutter-tester.
      * packages/flutter_tools/test/general.shard/build_system/targets/native_assets_test.dart
        * Unit tests the new Target in the backend.
      * packages/flutter_tools/test/general.shard/ios/native_assets_test.dart
      * packages/flutter_tools/test/general.shard/macos/native_assets_test.dart
        * Unit tests the native assets being packaged on a iOS/MacOS build.
      
      It also extends various existing tests:
      
      * dev/devicelab/bin/tasks/module_test_ios.dart
         * Exercises the add2app scenario.
      * packages/flutter_tools/test/general.shard/features_test.dart
         * Unit test the new feature flag.
      aa36db1d
  5. 24 Aug, 2023 1 commit
  6. 10 Aug, 2023 1 commit
  7. 20 Jun, 2023 1 commit
    • Lau Ching Jun's avatar
      Use the new `getIsolatePauseEvent` method from VM service to check for pause event. (#128834) · 32917500
      Lau Ching Jun authored
      The `getIsolate` method returns the full list of libraries which can be huge for large apps. Using the more speficic API to only fetch what we need improves hot reload performance.
      
      *Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.*
      
      *List which issues are fixed by this PR. You must list at least one issue.*
      
      *If you had to change anything in the [flutter/tests] repo, include a link to the migration guide as per the [breaking change policy].*
      32917500
  8. 26 May, 2023 1 commit
  9. 24 May, 2023 1 commit
  10. 18 Apr, 2023 1 commit
  11. 28 Mar, 2023 1 commit
  12. 23 Mar, 2023 1 commit
  13. 22 Mar, 2023 1 commit
  14. 21 Mar, 2023 1 commit
  15. 20 Mar, 2023 1 commit
  16. 17 Mar, 2023 2 commits
  17. 06 Mar, 2023 1 commit
  18. 28 Feb, 2023 1 commit
  19. 27 Feb, 2023 2 commits
  20. 17 Feb, 2023 2 commits
  21. 13 Feb, 2023 1 commit
  22. 09 Feb, 2023 1 commit
  23. 06 Feb, 2023 1 commit
  24. 01 Feb, 2023 1 commit
  25. 31 Jan, 2023 1 commit
  26. 30 Jan, 2023 1 commit
  27. 27 Jan, 2023 1 commit
  28. 25 Jan, 2023 1 commit
  29. 10 Jan, 2023 1 commit
  30. 15 Dec, 2022 1 commit
  31. 02 Dec, 2022 1 commit
    • Jackson Gardner's avatar
      Platform binaries reland (#115502) · db1c3e20
      Jackson Gardner authored
      You can now specify a --local-web-sdk flag to point to a wasm_release folder. This will make it so that only artifacts that pertain to the web sdk are overridden to point to the wasm_release folder. Other artifacts (such as impellerc) will pull from the cache, or from the --local-engine path if that is specified.
      
      This also uses precompiled platform kernel files for both ddc and dart2js
      db1c3e20
  32. 13 Nov, 2022 1 commit
  33. 12 Nov, 2022 1 commit
  34. 19 Oct, 2022 1 commit
  35. 18 Oct, 2022 2 commits
  36. 31 Aug, 2022 1 commit