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

Un-pin security-crypto from alpha

DoneOwner · Vivt_c24d8d34

Unlocks 1Approve: 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

**Un-pin security-crypto from alpha** · done

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

## Unlocks 1

- Approve: Android pre-submission blockers

## The brief on file

Viv — CORRECTED 2026-08-05, verified in code. The premise in the original task AND in docs/proposals/session-briefs/android-presubmission.md ("there is no stable 1.1.0; the stated exit is unreachable") is FALSE.

androidx.security:security-crypto **1.1.0 stable exists**, released 2025-07-30. Verified against Google Maven metadata (https://dl.google.com/dl/android/maven2/androidx/security/security-crypto/maven-metadata.xml reports <release>1.1.0</release>) and the AndroidX security release notes. There is no newer alpha/beta/rc — 1.1.0 IS the latest of any kind.

DONE in PR #225: apps/android/gradle/libs.versions.toml:22 moved 1.1.0-alpha06 -> 1.1.0. Builds clean.

THE REAL REMAINING ISSUE (this is the follow-up work, not the version bump): 1.1.0 stable shipped with EVERY API in the library deprecated. Release-note wording is "Deprecated all APIs in favour of existing platform APIs and direct use of Android Keystore." The stable release exists only to give the deprecated API a non-alpha resting place; the library has had no commits since July 2025 and there is no successor AndroidX artifact. Google's current guidance is Android Keystore + Tink. Note the deprecation notices disagree with each other — the release note says "Android Keystore", the class Javadoc @deprecated tag says plain SharedPreferences.

Two consumers now depend on it, and they must move together, not one at a time:
  - apps/android/app/src/main/java/com/tactile/app/data/auth/EncryptedSharedPrefsDeviceTrustStore.kt:31-43
  - apps/android/app/src/main/java/com/tactile/app/data/auth/EncryptedPrefsSessionManager.kt (added in PR #225)

A Keystore rewrite needs a migration path for already-enrolled devices (device-trust tokens exist in the wild) — that is why it was NOT bundled into the pre-submission PR. Track it as its own task.

Also relevant: EncryptedSharedPreferences has known Keystore-corruption failures on some OEM devices (tink#535, issuetracker 176215143 / 272569538), and its own Javadoc warns the prefs file must not be Auto-Backup'd. The backup exclusions for both files landed in PR #225 (res/xml/backup_rules.xml + data_extraction_rules.xml).

## 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

Un-pin security-crypto from alpha