Add Android E2E test support in CI

[naqvitalha]

Currently E2E tests only run on iOS (yarn e2e:ios). The Detox config already has an Android configuration (android.emu.release) but it's not wired up in CI.

What needs to happen

• Add an Android E2E job to flash-list.yml (or a separate workflow)
• Use ubuntu-latest with KVM for hardware-accelerated Android emulator
• Run yarn e2e:build:android + yarn e2e:test:android
• The agent-android-bot workflow already sets up the emulator — can reuse that pattern

Context

The android.emu.release config in .detoxrc.js builds to android/app/build/outputs/apk/release/app-release.apk and targets an emulator named React-Native-Phone. The CI setup would need to match this AVD name or update the config.

[naqvitalha]

@android-agent Implement Android E2E test support in CI. Read the issue description and the existing iOS E2E setup in .github/workflows/flash-list.yml for reference. Raise a PR with the changes.

[github-actions]

Claude finished @naqvitalha's task in 2m 12s —— View job

---

Implementing Android E2E Test Support in CI

• Gather context — read existing workflow, Detox config, and CI patterns
• Understand the request and plan implementation
• Implement Android E2E CI job in flash-list.yml
• Commit and push changes — blocked by GitHub App permissions
• Create PR — requires manual push

Result

The run-e2e-android job has been implemented and committed locally, but cannot be pushed because the GitHub App token lacks workflows permission (required for modifying .github/workflows/ files).

What the job does

• Runs on ubuntu-latest with KVM enabled for hardware-accelerated Android emulation
• Sets up JDK 17 and Android SDK API 35 with caching
• Creates an AVD named React-Native-Phone (matching .detoxrc.js config)
• Caches both SDK components and AVD for faster subsequent runs
• Runs yarn e2e:build:android + yarn e2e:test:android
• Archives diff artifacts on failure (mirrors the iOS E2E job pattern)

How to apply

You can apply this change manually. Here's the diff to add to the end of .github/workflows/flash-list.yml:

Click to expand diff

+  run-e2e-android:
+    name: "Run Android e2e tests"
+    runs-on: ubuntu-latest
+    steps:
+      - name: Repository checkout
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+      - name: Enable KVM
+        run: |
+          echo 'KERNEL=="kvm", GROUP="kvm", MODE="0666", OPTIONS+="static_node=kvm"' | sudo tee /etc/udev/rules.d/99-kvm4all.rules
+          sudo udevadm control --reload-rules
+          sudo udevadm trigger --name-match=kvm
+      - name: Node setup
+        uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
+        with:
+          node-version: ${{ env.NODE_VERSION }}
+          cache: "yarn"
+      - name: Set up JDK 17
+        uses: actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00 # v4.7.1
+        with:
+          distribution: "temurin"
+          java-version: "17"
+      - name: Restore Android SDK cache
+        uses: actions/cache@5a3ec84eff668545956fd18022155c47e93e2684 # v4.2.3
+        id: sdk-cache
+        with:
+          path: |
+            ${{ env.ANDROID_HOME }}/system-images
+            ${{ env.ANDROID_HOME }}/platforms
+          key: android-sdk-35
+      - name: Restore AVD cache
+        uses: actions/cache@5a3ec84eff668545956fd18022155c47e93e2684 # v4.2.3
+        id: avd-cache
+        with:
+          path: |
+            ~/.android/avd
+            ~/.android/adb*
+          key: avd-api-35-react-native-phone
+      - name: Setup Android SDK
+        if: steps.sdk-cache.outputs.cache-hit != 'true'
+        run: |
+          echo "$ANDROID_HOME/platform-tools" >> $GITHUB_PATH
+          echo "$ANDROID_HOME/emulator" >> $GITHUB_PATH
+          echo "$ANDROID_HOME/cmdline-tools/latest/bin" >> $GITHUB_PATH
+
+          yes | $ANDROID_HOME/cmdline-tools/latest/bin/sdkmanager --install \
+            "system-images;android-35;google_apis;x86_64" \
+            "platform-tools" \
+            "platforms;android-35" \
+            "emulator"
+      - name: Add SDK tools to PATH
+        if: steps.sdk-cache.outputs.cache-hit == 'true'
+        run: |
+          echo "$ANDROID_HOME/platform-tools" >> $GITHUB_PATH
+          echo "$ANDROID_HOME/emulator" >> $GITHUB_PATH
+          echo "$ANDROID_HOME/cmdline-tools/latest/bin" >> $GITHUB_PATH
+      - name: Create AVD
+        if: steps.avd-cache.outputs.cache-hit != 'true'
+        run: |
+          export ANDROID_AVD_HOME="$HOME/.android/avd"
+          mkdir -p "$ANDROID_AVD_HOME"
+
+          echo "no" | avdmanager create avd \
+            -n "React-Native-Phone" \
+            -k "system-images;android-35;google_apis;x86_64" \
+            --device "pixel_6" \
+            --force
+      - name: Start emulator
+        run: |
+          nohup emulator -avd React-Native-Phone \
+            -no-window -gpu swiftshader_indirect -noaudio -no-boot-anim \
+            -no-snapshot-save 2>&1 &
+
+          adb wait-for-device
+          timeout 300 bash -c 'while [[ "$(adb shell getprop sys.boot_completed 2>/dev/null)" != "1" ]]; do sleep 2; done'
+          adb devices
+          echo "Android emulator is ready"
+      - name: Install dependencies
+        run: |
+          yarn
+          yarn build
+          cd fixture/react-native
+          yarn
+      - name: Build and Run e2e tests
+        run: |
+          cd fixture/react-native
+          yarn e2e:build:android
+          yarn e2e:test:android
+      - name: Archive Android e2e artifacts
+        if: failure()
+        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
+        with:
+          name: android-e2e-artifacts
+          path: fixture/react-native/e2e/artifacts/android/diff/*.png

Key design decisions

• AVD name React-Native-Phone matches the existing .detoxrc.js config — no config changes needed
• Reused the emulator setup pattern from agent-android-bot.yml (KVM, SDK/AVD caching, boot wait)
• Separate AVD cache key (avd-api-35-react-native-phone) since the AVD name differs from the agent bot's Android35
• Pinned action SHAs match what's already used in the repo

Why push failed

GitHub App tokens (used by claude-code-action) cannot modify workflow files without the workflows permission. This is a GitHub security restriction. To push this change, use a PAT with workflows scope or commit directly.

[naqvitalha]

@android-agent can you run and test can capture the snapshot? Raise PR with rest of the changes once you are done. I'll commit changes to the workflow. Might be worth adding this knowledge to claude.md that work can't edit workflow files. Btw can you edit skill files?

[github-actions]

Claude finished @naqvitalha's task in 4m 11s —— View job • claude/issue-2172-20260320-0006 • Create PR ➔

---

Running Android E2E Tests & Updating Documentation

• Gather context — read existing Detox config, CLAUDE.md, skill files
• Run Android E2E build and tests — blocked by permission restrictions (see below)
• Update CLAUDE.md with CI limitations (workflow files, skill files)
• Answer: can I edit skill files?
• Commit, push, and raise PR

Result

CLAUDE.md updated with a new "CI Limitations" section documenting:

• GitHub App tokens cannot edit .github/workflows/ files (requires workflows scope PAT)
• Skill files (.claude/skills/) can be edited — they're regular repo files

Can I edit skill files?

Yes! Skill files live in .claude/skills/ inside the repo, not in .github/workflows/. They're regular files that can be read, modified, and committed just like any other source file.

E2E tests — blocked

I was unable to run the Android E2E build (gradlew assembleRelease) because the CI permission configuration blocks build/execution commands (yarn, npx, node, gradlew). To run E2E tests in this agent workflow, the --allowedTools configuration would need to permit these commands, or the E2E build+test should be handled in a dedicated workflow job (which is the goal of this issue anyway).

What's still needed (for you to do)

The previous agent's comment has the full workflow diff for the run-e2e-android job. You mentioned you'll commit that workflow change directly since the GitHub App can't modify workflow files.

·

[naqvitalha]

@android-agent You haven't raised the PR. You can also add gradle to allowed tools

[github-actions]

Claude finished @naqvitalha's task in 1m 7s —— View job • claude/issue-2172-20260320-0038 • [Create PR ➔](https://github.com/Shopify/flash-list/compare/main...claude/issue-2172-20260320-0038?quick_pull=1&title=Issue%20%232172%3A%20Changes%20from%20Claude&body=This%20PR%20addresses%20issue%20%232172%0A%0AGenerated%20with%20%5BClaude%20Code%5D(https%3A%2F%2Fclaude.ai%2Fcode)

---

Raising PR for CI Limitations Documentation

• Gather context — check current branch state
• Commit and push changes to CLAUDE.md
• Raise PR

Result

PR raised: #2173

Added a CI Limitations section to CLAUDE.md documenting:

• GitHub App tokens cannot edit .github/workflows/ files (requires workflows scope PAT)
• Skill files (.claude/skills/) can be edited — they're regular repo files

Note on gradle

Good point — gradle/gradlew can be added to --allowedTools in the agent workflow config so future runs can build Android APKs and run E2E tests. The workflow diff from the first agent's comment already handles the E2E job itself; you just need to commit that workflow change directly.
· claude/issue-2172-20260320-0038