Run explicit checks and interpret their results.
1. Variant awareness
Choose the intended module, flavor and build type. A passing debug build does not prove that release signing, shrinking or production configuration works.
2. Exit codes and logs
Preserve command exit status when capturing logs. A pipeline that prints output successfully can conceal a failed build unless its failure semantics are handled deliberately.
3. Incremental diagnosis
Read the first actionable error and isolate the failing task. Repeatedly cleaning caches without evidence can waste time and obscure the actual cause.
Worked scenario
A unit-test task fails while log capture succeeds. The workflow must report the failed test, not the successful file write.
Apply it
Run a targeted build and test command, capture their output and verify the final status reflects each failure.
Check your understanding
A failed check cannot be reported as a successful workflow. Explain the decision and show evidence from your implementation or design. If you cannot demonstrate it yet, revisit the relevant section before continuing.