Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Android›Android — Pre-submission blockers·11 in this wave

Approve: Android pre-submission blockersTo do · blocker Provision apps/android/local.properties so the Android app can reach a backendTo do · blocker GitHub Actions is off for the whole repo — billing wall fails every job in 2sTo do · blocker Add launcher icon setDone Bump compileSdk and targetSdk to Play's current floorDone Produce and validate a real signed release AABDone Confirm Supabase session tokens are encrypted at restDone verify:one-contact-address is red on main — design/card-creation-flow.html publishes kaitlynn@tactile.to 14 timesDone Automate versionCode and versionNameDone Un-pin security-crypto from alphaDone Replace deprecated security-crypto with Android Keystore + migrate enrolled devicesTo do

Wave

Android — Pre-submission blockers

Short, hard list that blocks any Play Store submission. Do these first — they are cheap and absolute.

TacTile › Launch TacTile › Android › Android — Pre-submission blockers

7/11 done4 open3 open blockers

Selected taskclear

Bump compileSdk and targetSdk to Play's current floor

DoneOwner · Vivt_d917fcfd

Unlocks 2Produce and validate a real signed release AAB Approve: Android pre-submission blockers

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

**Bump compileSdk and targetSdk to Play's current floor** · done

Where it sits: TacTile › Launch TacTile › Android › Android — Pre-submission blockers

## Unlocks 2

- Produce and validate a real signed release AAB
- Approve: Android pre-submission blockers

## The brief on file

Viv — DONE in PR #225 (https://github.com/TacTile-dev/TacTile/pull/225), pending merge.

CORRECTED FACTS (the in-code TODO and apps/android/AGENTS.md were both wrong):
- Code was at compileSdk/targetSdk **34** (app/build.gradle.kts:49,54), while AGENTS.md:194,201 claimed 35. Doc corrected in the PR.
- The old TODO said "bump to 35 once platforms;android-35 is installed" — inverted. ~/Library/Android/sdk/platforms holds android-34 and android-36; **android-35 is the one NOT installed**.

DECISION TAKEN: targetSdk/compileSdk 36. Verified live at developer.android.com/google/play/requirements/target-sdk on 2026-08-05: today's floor is 35, but it rises to **36 on 2026-08-31** for new submissions AND updates. The extension to Nov 1 is available to already-published apps only — this app has never shipped (it is a new submission), so 35 would have expired before we could submit.

Toolchain (bumped one step at a time, building between each):
- Gradle 8.9 -> 8.11.1 (via ./gradlew wrapper, so the wrapper jar/scripts moved too)
- AGP 8.7.3 -> 8.10.0
- Kotlin 2.0.21 / KSP 2.0.21-1.0.28 / Hilt 2.52 needed NO change.

Why AGP 8.10 and not 8.9.1: Google's own docs contradict each other — the API-level table says API 36 needs AGP >= 8.9.1, the AGP 8.9 release notes say 8.9's max is API 35. 8.9 and 8.10 require the same Gradle 8.11.1, so 8.10 sidesteps the ambiguity at zero cost.

Edge-to-edge was NOT the risk the plan expected: enableEdgeToEdge() is already called at MainActivity.kt:64 and insets are handled throughout. Verified on an API 36 emulator across the screens reachable without auth.

ALSO DISCOVERED — there is no system JDK on this machine. `/usr/libexec/java_home` reports none and a bare ./gradlew dies with "Unable to locate a Java Runtime". Use Android Studio's bundled JBR 21:
  export JAVA_HOME="/Applications/Android Studio.app/Contents/jbr/Contents/Home"
This is now documented in apps/android/AGENTS.md.

Next window: API 37 (Android 17) is already released; assume Aug 2027 for the next floor rise but verify — no official Google page states it yet.

## 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 — Pre-submission blockers

Bump compileSdk and targetSdk to Play's current floor