Everything written this session that has not been through the device: rounds 43 to 48 (each patch adversarially verified, 43's transient-notice expectation fixed), a partial round 49, the pipeline scripts, the Android Auto design and the icon comparison mock. Also the two harness changes that were never A/B'd — adaptive waits, which may only shorten a declared wait and never lengthen it, and a ship that runs the mock walk and the deploy at the same time. The A/B and its 255-step baseline are in handoff/tools; main stays at what the phone has actually walked.
21 lines
1.3 KiB
Plaintext
21 lines
1.3 KiB
Plaintext
And in **both**, the ground. This one is not a name or a byte but a
|
|
resolution: `<background>` is a reference, so the check asks `aapt2 dump
|
|
resources` what `mipmap/ic_launcher` is at `anydpi`, reads that file's
|
|
`<background>` id, maps the id back through the table, and requires
|
|
`drawable/ic_launcher_ground`; then it follows the two `fillColor` references
|
|
the `aapt:attr` blocks became and requires concept 04's six stops in them.
|
|
That is the check that catches a **stale APK** as well as a lost overlay —
|
|
`build.sh` pipes Gradle through `| tail -20 || true` and then runs
|
|
`ls -la "$APK"`, so a Gradle run that failed leaves the previous build's file
|
|
exactly where the next step looks for it, with every PNG in it still the
|
|
falcon's. Without aapt2 on the machine this half says `NOT CHECKED` and the
|
|
rest of the script still runs.
|
|
|
|
Both `build.sh` and `dev.sh` call it, so no APK this repo makes can quietly go
|
|
back to the old artwork. It cost about a second and a half on the 107 MB debug
|
|
APK before the ground was added; the ground is one `dump resources` and three
|
|
`dump xmltree` calls on top of that, measured at 0.3 s against that same real
|
|
APK — aapt2 reads `resources.arsc` and the entries it names, never the whole
|
|
file, so the cost does not grow with the APK. The release branch reuses the
|
|
same table rather than asking aapt2 for it twice.
|