Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Android›Android — Build & release·15 in this wave

Submit Android build for reviewTo do · blocker Approve: Android releaseTo do · blocker Seed a demo account — it blocks BOTH the Play screenshots and Caitlin's QA passBlocked · blocker Produce phone + tablet Play screenshotsBlocked Complete the Play Data Safety formIn progress Full device test pass on a physical Android phoneTo do Full device test pass on a physical Android tabletTo do Play Store review pre-flightIn progress Android CI + release automation (the wave goal had no task for it)Done Play feature graphic (1024x500) — hard submission requirement, nobody has filed itDone Public data-deletion page — Play requires it reachable WITHOUT sign-in (verified 307 today)Done The Android tier can be GREEN on a tree that does not clean-build — Hilt errors hide behind stale codegenTo do Write Play Store listing copyIn progress Play 7"/10" tablet screenshots — after the tablet adaptation landsTo do AssetsViewModelFailureTest flakes ~3% — cause not identified, symptom guarded not fixedTo do

Wave

Android — Build & release

No CI, no Play metadata, no release automation exist today. iOS has working Fastlane; Android has nothing.

TacTile › Launch TacTile › Android › Android — Build & release

3/15 done12 open3 open blockers

Selected taskclear

AssetsViewModelFailureTest flakes ~3% — cause not identified, symptom guarded not fixed

To doOwner · ait_8e98d0f0

No dependencies in this wave — nothing gates it, and nothing waits on it.

Show the prompt

You are Viv, the agent for the TacTile lane of Command.

Open the lane and work there:

```bash
cd ~/Command/tactile && claude
```

Read that lane's CLAUDE.md and lane.json before you touch anything — they
carry your identity, your scope, and the hazards specific to this lane.
Read state from the hub (https://internal.tactile.to) or ask. Never guess at it.

## The task

**AssetsViewModelFailureTest flakes ~3% — cause not identified, symptom guarded not fixed** · to do

Where it sits: TacTile › Launch TacTile › Android › Android — Build & release

## The brief on file

RE-FILED 2026-08-13 from t_bf47d7c7, which was titled "Android CI + release automation (the wave goal had no task for it)" and tracked none of that. Both things that title named are separately DONE — t_5569f354 (run Android unit tests in CI) and t_7e3aef8b (Android release automation). The row had been repurposed to track this flake, but `task_update` exposes no `title` field, so five rounds of readers saw a title describing finished work. t_bf47d7c7 is closed as SUPERSEDED; its content is here.

MEASURED, round 20 (Android session): 1 failure in 33 forced runs, ~3%, 0 invalid. Guarded in PR #401 → 48444bdb — explicitly a guard, NOT a fix.

TWO THINGS THE OLD RECORD GOT WRONG, both corrected here:
1. It named the wrong test method.
2. The symptom it recorded is the DOWNSTREAM one. `setUp` throws at `Dispatchers.setMain`; `@After` then trips the unset `lateinit` and piles a second, louder exception on top. The loud one is not the cause.

WHAT IS STILL UNKNOWN — this is the whole task. Gradle's console prints only exception type and line; the message lives in the XML, and 25 further forced iterations did not reproduce it to read. There is a STRUCTURAL SUSPECT, offered as a hypothesis and nothing more: all 8 tests in the class use `runTest {}` without being handed the setUp dispatcher. The round-20 session deliberately did not ship on it, which was the right call — do not ship a speculative fix either.

HOW TO WORK IT: capture the XML, not the console. `app/build/test-results/testDebugUnitTest/*.xml` carries the message the console drops. Loop the single class with `--rerun-tasks --no-build-cache` until one fails, then read the XML.

NOTE the tier itself was fixed separately in #402 → e45f9271 (twelve source-scanning Test tasks did not declare the scanned text as an input, so a bytecode-invariant edit cache-hit a stale verdict). That is a sibling of this row, not this row.

## How to work this

- Do the work, don't just plan it. If the fix is obvious and safe, make it.
- Surface anything needing Matthew's sign-off instead of deciding it yourself.
- Short replies. Lead with the answer, then stop.
- Finish by saying what changed, what you verified, and what you'd do next.

To doIn progressDoneBlockedPick a wave on the left · tap a task to expand it

Lanes

Android — Build & release

AssetsViewModelFailureTest flakes ~3% — cause not identified, symptom guarded not fixed