1. 03 Nov, 2023 4 commits
  2. 02 Nov, 2023 2 commits
  3. 01 Nov, 2023 2 commits
  4. 31 Oct, 2023 1 commit
  5. 27 Oct, 2023 1 commit
    • David Iglesias's avatar
      [web] Add 'nonce' prop to flutter.js loadEntrypoint (#137204) · 15ccf24d
      David Iglesias authored
      ## Description
      
      This PR adds a `nonce` parameter to flutter.js' `loadEntrypoint` method.
      
      When set, loadEntrypoint will add a `nonce` attribute to the `main.dart.js` script tag, which allows Flutter to run in environments slightly more restricted by CSP; those that don't add `'self'` as a valid source for `script-src`.
      
      ----
      
      ### CSP directive
      
      After this change, the CSP directive for a Flutter Web index.html can be:
      
      ```
      script-src 'nonce-YOUR_NONCE_VALUE' 'wasm-unsafe-eval';
      font-src https://fonts.gstatic.com;
      style-src 'nonce-YOUR_NONCE_VALUE';
      ```
      
      When CSP is set via a `meta` tag (like in the test accompanying this change), and to use a service worker, the CSP needs an additional directive: [`worker-src 'self';`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/worker-src)
      
      When CSP set via response headers, the CSP that applies to `flutter_service_worker.js` is determined by its response headers. See **Web Workers API > [Content security policy](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers#content_security_policy)** in MDN.)
      
      ----
      
      ### Initialization
      
      If the CSP is set to disallow `script-src 'self'`, a nonce needs to also be passed to `loadEntrypoint`:
      
      ```javascript
        _flutter.loader.loadEntrypoint({
          nonce: 'SOME_NONCE',
          onEntrypointLoaded: (engineInitializer) async {
            const appRunner = await engineInitializer.initializeEngine({
              nonce: 'SOME_NONCE',
            });
            appRunner.runApp();
          },
        });
      ```
      
      (`nonce` shows twice for now, because the entrypoint loader script doesn't have direct access to the `initializeEngine` call.)
      
      ----
      
      ## Tests
      
      * Added a smoke test to ensure an app configured as described above starts.
      
      ## Issues
      
      * Fixes https://github.com/flutter/flutter/issues/126977
      15ccf24d
  6. 25 Oct, 2023 2 commits
  7. 24 Oct, 2023 1 commit
  8. 23 Oct, 2023 2 commits
  9. 20 Oct, 2023 1 commit
  10. 19 Oct, 2023 1 commit
  11. 12 Oct, 2023 1 commit
  12. 11 Oct, 2023 1 commit
  13. 29 Sep, 2023 1 commit
  14. 28 Sep, 2023 2 commits
  15. 21 Sep, 2023 1 commit
  16. 20 Sep, 2023 3 commits
  17. 15 Sep, 2023 1 commit
  18. 14 Sep, 2023 1 commit
  19. 13 Sep, 2023 1 commit
  20. 12 Sep, 2023 1 commit
  21. 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
  22. 31 Aug, 2023 1 commit
  23. 29 Aug, 2023 1 commit
  24. 25 Aug, 2023 1 commit
  25. 21 Aug, 2023 1 commit
  26. 17 Aug, 2023 2 commits
  27. 16 Aug, 2023 1 commit
  28. 15 Aug, 2023 1 commit
  29. 10 Aug, 2023 1 commit
    • pdblasi-google's avatar
      Adds SemanticsNode Finders for searching the semantics tree (#127137) · 5df1c996
      pdblasi-google authored
      * Pulled `FinderBase` out of `Finder`
        * `FinderBase` can be used for any object, not just elements
        * Terminology was updated to be more "find" related
      * Re-implemented `Finder` using `FinderBase<Element>`
        * Backwards compatibility maintained with `_LegacyFinderMixin`
      * Introduced base classes for SemanticsNode finders
      * Introduced basic SemanticsNode finders through `find.semantics`
      * Updated some relevant matchers to make use of the more generic `FinderBase`
      
      Closes #123634
      Closes #115874
      5df1c996