Try to detect Gradle error messages that hint at AndroidX problems, and
warn in the logs about the potential problem and point to documentation
on how to fix the issue.
Unfortunately the Gradle errors based on this root issue are varied and
project dependent. It's probably better to still leave the message
intact in case the problem is unrelated.
Also filters out the plugin warning message pending in
flutter/plugins#1138. It's still valuable to add that for people on
previous versions of Flutter, but this link should override that message
for anyone on an up to date version of Flutter.
#27106
This adds a keycode generator that incorporates input from the Chromium and Android source trees, as well as some local tables, to generate static constants for the LogicalKeyboardKey and PhysicalKeyboardKey classes, as well as mappings from each of the platforms we support so far (currently only Android and Fuchsia).
This code generator parses the input files, generates an intermediate data structure (`key_data.json`) that is checked in, and then generates the Dart sources for these classes and some static maps that will also be checked in (but are not included in this PR).
The idea is that these codes don't change often, and so we don't need to generate them on every build, but we would like to be able to update them easily in the future if new data becomes available. If the existing data disappears or becomes unusable, we can maintain the checked-in data structure by hand if necessary, and still be able to generate the code.
This PR only contains the code generator, not the classes themselves. In another follow-on PR, I'll run the generator and check in the output of the generator.
Before this, we had several places where an isReleaseMode was defined, all with the same definition. This just makes it more broadly visible to allow our users to use it, as well as creating debug and profile versions, and adding a device lab test for it.
Since this is a const value, this makes it possible for a developer to easily mark blocks that can be removed at AOT compile time.
* Don't send accept/reject if compilation never started.
Ensure that we wait for reject's response since that is async operation.
Fixes https://github.com/flutter/flutter/issues/27120.
* Fix analysis errors
* Rename flag. Ensure we raise it on first compilation too.
This status shows for the duration of the run, not just while starting. It looks kinda weird in the editors to show a progress bar for "Starting Xcode build" and then removing it once it completes.
It appears that the encoding Apple is using to ensure their syslog
conforms with the syslog requirement for seven-bit ASCII encoding (see:
RFC 5424) is `vis`.
Details: https://www.freebsd.org/cgi/man.cgi?query=vis&sektion=3
* Revert "Make UriMapper and StdoutHandler public and add test cases (#26932)"
This reverts commit 6cf554b0c414097ce473a6f37bb1a4d5104df3c0.
* Revert "Update packages (#27046)"
This reverts commit 496c57386bb2e51d0153358d6c29ebd6a5a25ecd.
* Revert "roll engine for TODAY bug (#27049)"
This reverts commit 5ae6346f1d46af0f7cc30e9fcbd985e3242c9c76.
* Revert "Warn when building on master channel (#25007)"
This reverts commit dd65a54628159af18c0ab04d4868456526fa91e5.
* Revert "Add experimentalBuildEnabled flag and initial shim for build_runner (#26989)"
This reverts commit 1237ee8f63995e1bdddd651e6d28daf6ab145f3d.
* Revert "Experimental flags for hot reloads, fixed (#27043)"
This reverts commit 2c05d08f0ca1301616220b656dce70839419493c.
