Reid Baker f6bbf76524
Remove jetifier usages (#173548)
- **Remove jetifiier usages across repo**
Similar to https://github.com/flutter/flutter/pull/173459
Related to #173430

Used `grep --exclude-dir=third_party --include=gradle\.properties -rw .
-e "android.enableJetifier=true"` to find usages.

## Pre-launch Checklist

- [x] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [x] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [x] I read and followed the [Flutter Style Guide], including [Features
we expect every widget to implement].
- [x] I signed the [CLA].
- [ ] I listed at least one issue that this PR fixes in the description
above.
- [ ] I updated/added relevant documentation (doc comments with `///`).
- [ ] I added new tests to check the change I am making, or this PR is
[test-exempt].
- [x] I followed the [breaking change policy] and added [Data Driven
Fixes] where supported.
- [x] All existing and new tests are passing.
2025-08-12 21:03:55 +00:00
..
2025-08-12 21:03:55 +00:00

Tracing tests

"Application"

The lib/test.dart and lib/control.dart files in this directory are used by dev/bots/test.dart's runTracingTests function to check whether aspects of the tracing logic in the framework get compiled out in profile and release builds. They're not meant to be run directly.

The strings in these files are used in dev/bots/test.dart.

Tests

The tests in this folder must be run with flutter test --enable-vmservice, since they test that trace data is written to the timeline by connecting to the VM service.

These tests will fail if run without this flag.