Install Apk

Install APK to Device

Build Folders

APK files are stored locally in these locations — never in ~/Downloads/:

• RC & Preview builds: /path/to/your/builds/
• Feature branch builds: /path/to/your/builds/Feature branch/

Scan & Table Output

On every install request, ALWAYS do the following before installing:

1. Scan both folders (and any subfolders) for all .apk files:

find "/path/to/your/builds" -name "*.apk" -type f

2. Parse each filename to determine type, version, and region:

   • RC builds: filename starts with [Company]-, contains Release and RC (e.g. App-26.21.0-2022211953-157-Release-RegionA-RC-Signed.apk)
   • Preview builds: filename starts with MyApp-, contains Debug (e.g. MyApp-26.21.0-26040118-157-RegionA-Debug-Signed.apk)
   • Feature branch builds: any .apk inside the Feature branch/ subfolder

3. Display the results in a compact table sorted in ascending order by version:

   • One row per version with four columns for each build type/region.
   • Each cell shows the shorthand the user would type to install it, or — if not available.
   • Only show the Feature Branch table if feature branch APKs exist.

RC & Preview Builds

Feature Branch Builds (only shown if feature branch APKs exist)

Shorthand Quick Install

The user will use shorthand to request installs. Match as follows:

Default rule: If the user only says a version + region without specifying R or P (e.g. 26.21 W or 26.21 C), always default to RC (R).

The user may also provide a full filename — match it against scanned results.

Install Command

Run immediately — no confirmation needed:

~/Library/Android/sdk/platform-tools/adb install "<FULL_PATH_TO_APK>"

If the app is already installed and the user is updating, use -r to replace:

~/Library/Android/sdk/platform-tools/adb install -r "<FULL_PATH_TO_APK>"

Always quote the path (filenames and folders contain spaces).

Handling Errors

Do NOT ask the user for confirmation on recoverable errors. Fix them automatically.

Examples

User says: "26.21 R W"

Action:

1. Scan folder, show table of all available builds.
2. Match 26.21 R W → find App-26.21.0-2022211953-157-Release-RegionA-RC-Signed.apk
3. Install immediately:

~/Library/Android/sdk/platform-tools/adb install "/path/to/your/builds/App-26.21.0-2022211953-157-Release-RegionA-RC-Signed.apk"

User says: "26.21 P C"

Action:

1. Scan folder, show table of all available builds.
2. Match 26.21 P C → find MyApp-26.21.0-26040118-157-RegionB-Debug-Signed.apk
3. Install immediately:

~/Library/Android/sdk/platform-tools/adb install "/path/to/your/builds/MyApp-26.21.0-26040118-157-RegionB-Debug-Signed.apk"

User says: "install feature branch EXAMPLE-PROJ-1234"

Action:

1. Scan Feature branch/ subfolder, show feature branch table.
2. Match filename containing EXAMPLE-PROJ-1234 or the card name.
3. Install immediately.

Slack Build Lookup

Slack release channels follow the naming pattern: yourapp-release-XX-XX (dashes, not dots).

Trigger

When the user mentions a version + "slack" (e.g. 26.21 slack), use the dis-slack agent to read the channel and extract build links.

Steps

1. Use the dev-integration-server MCP tools (preferred) or fall back to CLI (dis call):
   • slack_channels with {"query": "yourapp-release-XX-XX"} to find the channel ID
   • slack_history with {"channel": "<CHANNEL_ID>", "limit": 20} to get messages
2. Parse messages for build links (TestFairy URLs). iOS builds come from one message, Android from another.
3. Display the results with full build details extracted from the Slack messages:

Android Builds — #yourapp-release-26-21

Always include: version, build code, download link, and who posted it with date/time. Add a "Open in Slack" permalink at the end so the user can jump directly to the message. Do NOT include package name column or rollout schedule — keep it clean.

Example footer: Posted by John Releaser — April 8, 2026, 9:33 PM UTC | [Open in Slack](slack://channel?team=TEAM_ID&id=CHANNEL_ID&message=MESSAGE_TS)

Always use the slack:// deep link format so it opens directly in the Slack desktop app — never use https://your-org.slack.com/... browser links.

Adaptive Parsing

Build links are typically posted by devs in a consistent format. If the format changes over time, adapt by learning the new pattern from the messages.