| commit | 0d4f78c952552819753a2676b318e181004ba746 | [log] [tgz] |
|---|---|---|
| author | Xilai Zhang <xilaizhang@google.com> | Mon Mar 11 17:15:19 2024 -0700 |
| committer | GitHub <noreply@github.com> | Tue Mar 12 00:15:19 2024 +0000 |
| tree | adf2eec4743112b55ea9d876c08a373bd95b509f | |
| parent | 8ff4ca5d13e9f9eb22eaa5f2345f818553eacaf0 [diff] |
[cp-beta] fix typo in binary path (#51339) (#51342) ### Issue Link: What is the link to the issue this cherry-pick is addressing? release failure at [link](https://ci.chromium.org/ui/p/dart-internal/builders/flutter/Mac%20engine_release_builder/536/overview) ### Changelog Description: Explain this cherry pick in one line that is accessible to most Flutter developers. See [best practices](https://github.com/flutter/flutter/wiki/Hotfix-Documentation-Best-Practices) for examples Fix typo in the binary path of xcframework artifact. ### Impact Description: What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)? Does it impact development (ex. flutter doctor crashes when Android Studio is installed), or the shipping production app (the app crashes on launch) would block the release on codesign error. ### Workaround: Is there a workaround for this issue? revert the [xcframework pr](https://github.com/flutter/engine/commit/73a6e0718ec41e910073e7d4b2f21d283921fedb#diff-16e49048cfbb998545e3493d5e3148c515b02de6fb894945df457756a6d9099a) and cherry pick would also work. but we can do a fix forward. ### Risk: What is the risk level of this cherry-pick? - [ x ] Low ### Test Coverage: Are you confident that your fix is well-tested by automated tests? - [ x ] Yes ### Validation Steps: What are the steps to validate that this fix works? codesign test should pass in release workflow
Flutter is Google's SDK for crafting beautiful, fast user experiences for mobile, web, and desktop from a single codebase. Flutter works with existing code, is used by developers and organizations around the world, and is free and open source.
The Flutter Engine is a portable runtime for hosting Flutter applications. It implements Flutter's core libraries, including animation and graphics, file and network I/O, accessibility support, plugin architecture, and a Dart runtime and compile toolchain. Most developers will interact with Flutter via the Flutter Framework, which provides a modern, reactive framework, and a rich set of platform, layout and foundation widgets.
If you want to run/contribute to Flutter Web engine, more tooling can be found at felt. This is a tool written to make web engine development experience easy.
If you are new to Flutter, then you will find more general information on the Flutter project, including tutorials and samples, on our Web site at Flutter.dev. For specific information about Flutter's APIs, consider our API reference which can be found at the docs.flutter.dev.
Flutter is a fully open source project, and we welcome contributions. Information on how to get started can be found at our contributor guide.