Run e2e on Android 16

[rahul-lohra]

Goal

Run e2e on Android 17

Implementation

Run e2e on Android 17

🎨 UI Changes

None

Testing

None

Summary by CodeRabbit

• Tests
  • Updated Android end-to-end testing to run against Android API level 37.

[github-actions]

PR checklist ❌

The following issues were detected:

• Linked issue missing. Add a Linear ticket reference (e.g. AND-123, Closes AND-123, or a https://linear.app/... link) or a GitHub issue (Closes #123) to the PR description.

What we check

1. Title is concise (5–18 words) unless labeled pr:ignore-for-release.
2. At least one pr: label exists (e.g., pr:bug, pr:new-feature).
3. Sections ### Goal, ### Implementation, and ### Testing contain content. Bot-authored PRs are exempt.
4. PR description references an issue (Linear ticket like AND-123, a Linear URL, or a GitHub Closes #N). Bot-authored PRs are exempt.

[coderabbitai]

Walkthrough

The E2E compose-test workflow now runs its Android emulator at API level 37 instead of 34.

Changes

E2E emulator configuration

Layer / File(s)	Summary
Update emulator API level .github/workflows/e2e-test.yml	Sets ANDROID_API_LEVEL to 37, which is passed to the emulator runner.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• GetStream/stream-chat-android#6575: Updates the E2E workflow with additional Android API levels.

Suggested reviewers: peter-matkovski

Poem

A bunny hops where emulators gleam,
API thirty-seven joins the stream.
Compose tests run, the carrots sway,
Green checks may guide the testing day.
Hop, hop—configuration finds its way!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title says Android 16, but the change and description target Android 17, so it misstates the main update.	Update the title to match the actual change, for example: 'Run e2e on Android 17'.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The core Goal, Implementation, UI Changes, and Testing sections are present and aligned with the template.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch tests/rahullohra/android-17-e2e

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

SDK Size Comparison 📏

SDK	Before	After	Difference	Status
stream-chat-android-client	5.95 MB	5.95 MB	0.00 MB	🟢
stream-chat-android-ui-components	11.21 MB	11.21 MB	0.00 MB	🟢
stream-chat-android-compose	12.69 MB	12.69 MB	0.00 MB	🟢

[andremion]

Thanks for setting this up. The CI failures here are not test failures, the emulator never boots. Details in the inline comment.

The same issue affects the cron workflow after #6575 was merged: the android_api_level: 37 leg in e2e-test-cron.yml will fail the same way every night, and it will trigger the nightly Slack alert each time. The 36 leg is fine (platforms;android-36 and system-images;android-36;default;x86_64 both exist). Could you include the cron fix in this PR too, or in a small follow-up? Since the matrix legs need different targets, something like:

matrix:
  include:
    - android_api_level: "37.0"
      target: google_apis_ps16k
    - android_api_level: 36
    ...

and in the emulator step:

          target: ${{ matrix.target || 'default' }}

[andremion]

This is why the three Test compose shards fail in ~30s. There is no platforms;android-37 package in the SDK repository. Android 17 uses the new major.minor naming, so the available packages are platforms;android-37.0 and platforms;android-37.1.

There is a second problem behind it: the step does not set target:, so android-emulator-runner defaults to default (AOSP). No default system image exists for 37 at all. The only x86_64 images are google_apis_ps16k and google_apis_playstore_ps16k.

Could you change it to this?

env:
  ANDROID_API_LEVEL: "37.0"

and add the target to the emulator step:

          api-level: ${{ env.ANDROID_API_LEVEL }}
          target: google_apis_ps16k

That resolves to platforms;android-37.0 and system-images;android-37.0;google_apis_ps16k;x86_64, both present in the stable channel. One caveat: the 37 images are 16 KB page-size builds, so we only learn from a run whether the tests pass on them.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud