ci: give the UiAutomator2 server 2 minutes to start on the Android emulator job

[plum117]

Why

2 runs of the Android emulator job failed at the session start, before any test:

WebDriverError: The instrumentation process cannot be initialized within 30000ms timeout.

(runs 38064244310 and 38064214986). The UiAutomator2 driver waits uiautomator2ServerLaunchTimeout (default 30 s) for its server, and on the busy CI runner the server sometimes needs more time. The driver message itself advises to increase this capability.

What

tests/configs/wdio.local.android.emus.web.conf.ts: 'appium:uiautomator2ServerLaunchTimeout': 120000 in CI only (process.env.CI). A normal start is not slower; only a slow start gets more time. A change to the test config only, so there is no changeset.

Test

Types and lint. The Android emulator job of this PR runs with the new capability (its path filter includes this config).

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5733a9c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[greptile-apps]

Confidence Score: 5/5

[Low impact] The PR appears safe to merge.

Summary

Gives the Android emulator’s UiAutomator2 server up to two minutes to start in CI.

• Android web sessions wait longer for UiAutomator2 on CI.

_{Reviews (1) · Last reviewed commit: "ci: give the UiAutomator2 server 2 minut..." · Reviewed by Greptile}