Skip to content

Android leases that name no image tag can get a Play Store emulator #1590

Open

Description

@V3RON

Request: #1220

Problem

In the reporter's words: on a gateway whose Android workers have both google_apis and google_apis_playstore images installed, a lease without --image-tag always gets google_apis. Clients that cannot pass an image tag (for example a device picker that sends only platform and model) therefore never get an emulator with Play Store, even though the fleet has one.

They hit this testing Google Play Billing. The picker leased Pixel 9 / API 37 / google_apis, which has no com.android.vending, so no Play purchase was possible. Passing --image-tag google_apis_playstore by hand worked.

A tag alone would not have helped them. Their newest level, API 37, has no Play Store image, so a lease with no --os lands on 37 whatever the default tag is.

Who it is for

An operator who runs Android workers that have Play Store images, and whose users or agents lease through clients that cannot name an image tag: a device picker, a CI step with fixed arguments, an agent tool that sends only platform and model.

Outcome

The operator sets one worker setting, android.defaultImageTag. From then on, an Android lease that names no image tag gets an image with that tag wherever one for the machine's own CPU fits the model, at the newest API level that has one. Where none fits, the lease gets exactly what it gets today. A lease that names a tag, a baseline or a physical phone is unchanged, and so is every lease on a worker without the setting. The operator can see the setting in simlock catalog, and simlock doctor tells them when no installed image has the tag.

How it works for the user

flowchart TD
  A[Client: lease Android, no --image-tag] --> B{Worker has android.defaultImageTag?}
  B -- no --> T[Today's pick]
  B -- yes --> C{An image with that tag, for this machine's CPU, fits the model at a level the request allows?}
  C -- yes --> D[Newest such level, that tag]
  C -- no --> T
  D --> G[Granted: the grant names the tag]
  T --> G2[Granted as today]
  E[Operator: typo in the tag] --> F[simlock doctor: advisory default-image-tag-not-installed]
Loading

Worker images: API 29, 33, 35, 36 and 37 google_apis; API 36 google_apis_playstore (x86_64).

Before:

$ simlock lease --platform android --device "Pixel 9" --json | jq '.device.spec'
{ "platform": "android", "model": "Pixel 9", "osVersion": "37", "physical": false }

After, with "android": { "defaultImageTag": "google_apis_playstore" } in the worker's config:

$ simlock lease --platform android --device "Pixel 9" --json | jq '.device.spec'
{ "platform": "android", "model": "Pixel 9", "osVersion": "36", "imageTag": "google_apis_playstore", "physical": false }

$ simlock lease --platform android --device "Pixel 9" --os 37 --json | jq '.device.spec'
{ "platform": "android", "model": "Pixel 9", "osVersion": "37", "physical": false }

$ simlock catalog --platform android
Platform: android
  Runtimes: 29, 33, 35, 36, 37 (default: 37)
  Default image tag: google_apis_playstore
  Models:
  ...
  Images (runtime, tag, ABI):
    29 google_apis x86_64
    ...

$ simlock doctor          # with "google_apis_playstor" (a typo) in config
Warning [android] default-image-tag-not-installed: android.defaultImageTag is "google_apis_playstor", but no installed system image for this machine's CPU (x86_64) has that tag (installed for x86_64: google_apis, google_apis_playstore). Android leases that name no image tag get the image they would get without it.

A bad value stops the config load:

$ simlock daemon start
Invalid config value for "android.defaultImageTag": expected an image tag: 1 to 64 letters, digits, '_', '.' or '-'

Examples

Worker images as above. "Tagless" means the request names no --image-tag. Today's results come from a run of the Android catalog's resolveSpec on main at 5e639b4 with these images. The After column is for a worker with android.defaultImageTag: google_apis_playstore.

Request Today After
Pixel 9 37, no tag 36, google_apis_playstore
Pixel 9 --os 37 37, no tag 37, no tag (no Play Store image at 37)
Pixel 9 --os 36 36, no tag 36, google_apis_playstore
Pixel 9 --os ">=35" 37, no tag 36, google_apis_playstore
Pixel 9 --os ">=37" 37, no tag 37, no tag
--class phone (first phone model Pixel 9) Pixel 9, 37, no tag Pixel 9, 36, google_apis_playstore
Pixel 6 (takes no Play Store images) 37, no tag 37, no tag
Medium Tablet 37, no tag 36, google_apis_playstore
Television (1080p), no TV image installed fails RUNTIME_MISSING: it needs a TV image the same failure
Pixel 9 --os 38 --allow-download (38 not installed) downloads 38 google_apis, then 38, no tag the same
Pixel 9 --image-tag google_apis 37, google_apis 37, google_apis
Pixel 9 --image-tag google_apis_playstore --os 37 fails RUNTIME_MISSING the same failure
--baseline pay (saved on 37, no tag) the baseline's spec the baseline's spec
--physical an enrolled phone an enrolled phone
iOS, any request as today as today
Any request, setting unset as today as today
Worker on arm64 whose only google_apis_playstore image is x86_64; Pixel 9 37 google_apis arm64 (host CPU first) the same; doctor advisory
Setting "google_apis_playstor" (no such image) — every tagless lease as today; doctor advisory
Setting "play store" or "" — config load fails

What could go wrong

  • Tagless Android leases on a worker with the setting can get an older API level than before. That is the point of the setting, but a user who expected the newest level would notice. They can pass --os. Likely, and documented.
  • A warm device made before the setting (no tag) no longer serves those leases, so the first leases after the change wait for a boot. Likely once, then gone as idle devices age out.
  • A worker with images of the tag for two CPUs at different levels (say a host-CPU one at 35 and another CPU's at 36): a tagless --os ">=35" or class request picks 36 from the catalog, which counts every CPU, the driver refuses it, and the lease falls back to today's pick instead of 35 with the tag. A tagless request with no --os and a model still gets 35 with the tag. Rare: it needs a foreign-CPU image installed on purpose.
  • Through a gateway, the gateway counts images of every CPU too. On a worker whose only image of the tag is for another CPU, it looks for a warm tagged device the worker never makes, and ranks by free capacity instead. The lease is still served.
  • Through a gateway, for a model that takes no Play Store image, the gateway may look for a warm Play Store device it will never find, and pick a worker by free capacity instead of by a warm device. The lease is still served. Rare.
  • A typo in the setting, or a tag installed only for another CPU, gives today's images. doctor reports both.
  • Play Store images are production builds: adb root and adb remount are refused on them. A test that relies on root on a tagless lease breaks on a worker with the setting, until it names --image-tag google_apis. Likely for some users; the docs say so.

Words used

  • image tag: the kind of Android system image, the folder name under the SDK's system-images/android-<level>/, e.g. google_apis, google_apis_playstore, default.
  • tagless request: a lease request that names no --image-tag (imageTag over the API), e.g. simlock lease --platform android --device "Pixel 9".
  • fits: an image fits a model when the model's profile accepts it: its API range, its kind (phone, TV, Wear) and whether it takes Play Store or tablet images. Pixel 6 takes no Play Store images.
  • fall back: when the default tag cannot be met, the request runs again exactly as it came, as on a worker without the setting.
  • host CPU (ABI): the CPU type an image is built for, x86_64 or arm64-v8a. An emulator boots an image for the machine's own CPU.
  • warm device: an idle emulator that is already booted, so a lease gets it at once.
  • advisory: a simlock doctor finding that reports something worth knowing and never stops the worker or blocks a lease.

Non-goals

  • A default API level (android.defaultOsVersion). The level already follows the tag, and --os stays per lease.
  • A default per model or per class. One tag per worker.
  • An ordered list of fallback tags. The fallback is always today's pick.
  • Downloading an image of the default tag. Downloads still install only google_apis (ADR 0025 §4).
  • A fleet-wide setting on the gateway. Each worker sets its own.
  • Listing image tags in the catalog for pickers to offer. The catalog already lists every installed image's tag (simlock catalog --platform android, MCP list_devices).
  • Re-tagging, retiring or rebuilding devices made before the setting.
  • iOS.

Completion conditions

  • On a worker with API 36 google_apis_playstore, API 37 google_apis and android.defaultImageTag: google_apis_playstore, simlock lease --platform android --device "Pixel 9" grants a Pixel 9 on API 36 whose spec names google_apis_playstore.
  • On the same worker, --os 37 grants API 37 with no tag, and a Pixel 6 lease grants what it grants without the setting.
  • On a worker without the setting, every lease in the Examples table gets its Today result.
  • A request that names --image-tag, a baseline or --physical gets the same result with and without the setting.
  • A configured warm target for Pixel 9 with no tag, on that worker, keeps a Pixel 9 on API 36 with google_apis_playstore warm.
  • Through a gateway, a tagless Pixel 9 lease goes to the worker that has a ready Pixel 9 on 36 with google_apis_playstore when another worker has only free capacity.
  • simlock catalog --platform android prints Default image tag: google_apis_playstore on that worker, and no such line on a worker without the setting. Through a gateway it prints the line only when every Android worker reports the same tag.
  • simlock doctor reports default-image-tag-not-installed when no installed image for the machine's CPU has the tag, and nothing for the setting when one does or the setting is unset.
  • On an arm64 worker whose only image with the tag is x86_64, a tagless lease gets what it gets without the setting.
  • A value that is not an image tag stops the config load with the message in I1.

Open questions

Decisions

  • ADR 0078 — An Android worker tries its default image tag first, and a lease falls back to none (PR docs(adr): propose 0078, an Android worker tries its default image tag first and falls back to none (#1590) #1591): the setting, the try-then-fall-back rule, the tag outranking the newest level, the catalog field and the doctor advisory.
  • ADR 0007 — A lease request chooses the device mode: the precedent. A worker default is applied in one place in leasing (§2), and a gateway reads it from the worker's catalog (ADR 0066 §5).
  • ADR 0025 — Android profiles and fit: §4's level and image order is what the fallback returns to; ADR 0078 narrows it for a worker with the setting.
  • ADR 0015 — A lease request is a set of constraints: §5's rule that a tagged request counts only runtimes where the catalog lists an image of that tag is what the tagged attempt uses; §7, the grant names the device's tag.
  • Decided in the session: the setting is a worker setting, read per worker by a gateway, because a worker used without a gateway must get it too (maintainer).
  • Decided in the session: a default that cannot be met falls back to today's pick, because failing would break every lease for a model that takes no Play Store image (maintainer).
  • Decided in the session: with no --os the tag outranks the newest level, because otherwise the reporter's case stays unfixed (maintainer).
  • Decided in the session: no default API level, because the level follows the tag (maintainer).
  • Decided in the session: doctor reports an advisory for a tag no installed image has, and the worker still starts, because removing an image with sdkmanager must not stop a worker (maintainer).
  • Decided in the session: the tagged attempt never downloads, and the fallback may, because an image tag never downloads today and the fallback is today's request.
  • Decided in the session: the fallback runs on a missing-runtime refusal only; any other refusal of the tagged attempt (an unknown model, a bad request) is the request's answer, because the untagged attempt would refuse the same way.
  • Decided in the session: the class model choice is unchanged; the tagged attempt picks the first preferred model that pairs with a tagged level, as a tagged class request does today, because one rule for tagged requests keeps the gateway and the worker in step.
  • Decided in the session: the lease record keeps what the request named (no tag); the device's spec and the grant name the tag, because ADR 0015 §7 has the grant name the device and the request stays the caller's.
  • Decided in the session: the setting is read at start; a change needs a restart, like ios.defaultMode.
  • Decided in the session: a gateway treats a worker whose catalog has no defaultImageTag as having none, so an older worker routes as today.
  • Decided in the session: simlock catalog prints the default tag only when it is set, and its JSON carries defaultImageTag only then.
  • Decided in the session: the default takes only an image for the machine's own CPU; one for another CPU counts as no image, for the fallback and for doctor, because such an emulator does not boot (maintainer). An explicit --image-tag keeps today's order.
  • Decided in the session: a gateway's merged catalog carries defaultImageTag only when every Android worker reports the same one, as defaultRuntime (maintainer).
  • Decided in the session: the protocol's min stays where it is for both bumps; an absent field is the compatibility path, so an older worker or gateway keeps working.

Behaviours

Id Behaviour (invoker, action, what it sees) Seam Cases Task
B1 A caller leases Android with no tag on a worker with android.defaultImageTag; the grant is the newest level a tagged request would get, and its spec names the tag createLeasing (src/leasing/create-leasing.ts) request, fake Android driver with images 36 google_apis_playstore and 37 google_apis exact model, no OS → 36 tagged; --os 36 → 36 tagged; range >=35 → 36 tagged; class phone → first phone model, 36 tagged; an idle ready device of the tagged spec is granted before a new one is made T1
B2 The same caller, when the tagged attempt is refused as a missing runtime, gets exactly what the request gets without the setting createLeasing request, fake Android driver --os 37 (no tagged image at 37) → 37 untagged; range >=37 → 37 untagged; the driver refuses the tagged resolve as a misfit (Pixel 6) → untagged; no image at all fits → the untagged attempt's own RUNTIME_MISSING; --os 38 --allow-download → no install for the tagged attempt, then the untagged attempt installs 38 as today; the driver refuses the tagged attempt because its only tagged image is for another CPU → untagged; the tagged attempt refuses UNKNOWN_MODEL → UNKNOWN_MODEL, no second attempt. The fake driver (src/core/fake-driver.ts) gets an option to refuse a tagged resolve for a named model T1
B3 A request the setting does not apply to is unchanged createLeasing request names imageTag: google_apis → 37 google_apis; names a baseline → the baseline's spec; physical → an enrolled phone; iOS → unchanged; setting unset → every B1 case gets its untagged result T1
B4 The warm pool resolves a configured target with no tag to the spec a tagless lease would get createLeasing ports.warmPoolDemand.resolve Pixel 9 target, setting set → 36 tagged; setting set, Pixel 6 target (tagged resolve refused) → untagged; setting unset → untagged T1
B10 The Android driver, asked to resolve a request carrying the default tag, takes only an image of that tag for the host CPU Catalog.resolveSpec (src/drivers/android/catalog.ts) over the memory SDK (test-catalog.ts) host-CPU image of the tag at 36 → 36 tagged; only a foreign-CPU image of the tag → AndroidImageTagMissingError (a RuntimeMissingError, downloadable: false); both CPUs at 36 → the host-CPU one; the same request as an explicit tag (no defaultTag) with only a foreign-CPU image → that image, as today T1
B5 An operator starts a worker with android.defaultImageTag; a valid tag loads and config.get shows it, a bad one stops the load with I1's message loadConfig (src/core/config.ts:113); config.get output schema google_apis_playstore → loads, config.get carries it; absent → loads, absent from config.get; "", "play store", a 65-character tag, a number → refused with I1's message T1
B6 A client reads catalog.get from a worker; the Android entry names the default tag when the setting is set Dispatcher catalog.get (src/daemon/dispatcher-status.ts) set → defaultImageTag: "google_apis_playstore" on the Android entry, none on the iOS entry; unset → no field; the field passes the platform catalog schema and is bounded like an image tag T2
B7 A gateway ranks workers for a tagless Android lease by warm devices of the spec each worker would give it gateway routing select (src/gateway/routing/) over worker views worker A has a ready Pixel 9 36 tagged and a default, worker B only free capacity → A; worker A's ready device is untagged 37 and its default is set → no warm hit on A; a worker with no defaultImageTag in its catalog → warm hit by the untagged spec, as today; request with imageTag → as today; assess answers the same with and without the field T2
B8 An operator runs simlock catalog --platform android CLI catalog command (src/cli/commands/catalog.ts) set → Default image tag: <tag> line after the Runtimes line; unset → no line; --json → defaultImageTag only when set T2
B11 A client reads catalog.get from a gateway; the merged Android entry names the default tag only when every Android worker in the merge reports the same one gateway catalog.get (src/gateway/aggregate.ts renderPlatform) over worker views two workers with google_apis_playstore → the field; one with it and one without → none; two different tags → none; one worker with it → the field; no Android worker → no Android entry T2
B9 An operator runs simlock doctor on a worker with the setting; when no installed system image has the tag, it lists the advisory default-image-tag-not-installed with I5's message AndroidDriver.advisories (src/drivers/android/index.ts) over the memory SDK, and core doctor's driver-advisory collection (doctor-advisories.test.ts already proves the collection) tag installed for the host CPU at some level → no advisory; tag installed only for another CPU → advisory; no image has it → advisory naming the tag, the host CPU and its installed tags, sorted, once each; no system image for the host CPU → advisory with none; setting unset → no advisory; doctor --fix acts on none T3

Stored state

Id What and where Created, changed, deleted by Listed or swept by A restart mid-step leaves Schema step Task Used by
S1 android.defaultImageTag in the worker's config.json the operator; read at daemon start config.get; simlock config — (read once at start) none T1 T2, T3

The device's spec already stores an image tag (devices table, image_tag in src/drivers/android/source-data.ts:151 for the seed), and learned warm kinds already key on it (ADR 0038). This feature writes the default tag into those existing columns through the normal grant and learning paths; it adds no column.

Interfaces

Id What Shape and bounds Errors and limits Where Task Used by
I1 Config key android.defaultImageTag optional string, 1 to 64 characters, [A-Za-z0-9_.-] (the bounds of imageTagSchema, src/contract/device-schemas.ts:91); unset by default. config.get's android section declares it as imageTagSchema.optional(): bumps the protocol by one; min stays, since an absent field is the compatibility path a bad value: Invalid config value for "android.defaultImageTag": expected an image tag: 1 to 64 letters, digits, '_', '.' or '-' (ConfigError, the daemon does not start) src/core/config-validators.ts, config-types.ts, config-defaults.ts, src/contract/config-schemas.ts T1 T2, T3
I2 Leasing option defaultImageTags Readonly<Partial<Record<Platform, string>>>, beside defaultModes in createLeasing's options and AcquisitionSpecResolverOptions; the daemon fills { android: config.android.defaultImageTag } when set — src/leasing/create-leasing.ts, src/leasing/acquisition-spec-resolver.ts, src/daemon/worker-composition.ts T1 —
I3 The tagged attempt in AcquisitionSpecResolver.resolveSpec for a request with platform set to a platform in I2, no imageTag, no baseline, not physical: resolve { ...request, imageTag: <default> } with allowDownload: false, its exact request to the driver carrying defaultTag: true (I7); on a RuntimeMissingError, resolve request as it came with its own options. checkedSpec compares the resolved tag with the attempt's request. The warm pool's resolve goes through the same method only a RuntimeMissingError of the tagged attempt is dropped; any other error of it reaches the caller as it is, with no second attempt; the untagged attempt's errors reach the caller unchanged src/leasing/acquisition-spec-resolver.ts:56-88 T1 T2 (the gateway mirrors its runtime rule in I4)
I4 Catalog field defaultImageTag on the Android entry of catalog.get optional, imageTagSchema; set by the worker's dispatcher from S1, as defaultMode is for iOS; bumps the protocol by one, min stays. A gateway's merged entry carries it only when every Android worker in the merge reports the same value (agreedDefault, as defaultRuntime). A gateway, for a tagless, non-baseline, virtual Android request on a worker whose entry has it, builds deviceFit's requirement for { ...request, imageTag } when the catalog has a serving model under that tag, else for the request as it came an older worker sends none: no default src/contract/status-schemas.ts:307, src/daemon/dispatcher-status.ts:14, src/gateway/aggregate.ts:365, src/gateway/routing/request-match.ts:79 T2 —
I5 Android driver option defaultImageTag and advisory default-image-tag-not-installed optional string on AndroidDriver.create's options, carried from config by a new DriverDiscoveryContext.androidDefaultImageTag that worker-composition.ts fills; advisories() adds one { code: "default-image-tag-not-installed", message } when no installed system image for the host CPU has that tag message: android.defaultImageTag is "<tag>", but no installed system image for this machine's CPU (<abi>) has that tag (installed for <abi>: <tags>). Android leases that name no image tag get the image they would get without it. <abi> is the driver's host ABI; <tags> is the host-CPU images' tags, sorted, once each, joined by , , or none src/drivers/android/index.ts:712, src/daemon/driver-discovery.ts:63-87,270-275, src/daemon/worker-composition.ts:208-227 T3 —
I7 ExactDeviceRequest.defaultTag optional true, set only by I3's tagged attempt, never from the wire; DeviceRequest omits it as it omits model, so no stored request, warm target or lease record carries it; the Android driver then takes only an image of the tag for its host ABI and refuses with AndroidImageTagMissingError (downloadable: false) when there is none; other drivers ignore it as AndroidImageTagMissingError's messages today src/core/driver.ts:26-41, src/drivers/android/catalog.ts:93-115,167-185, src/drivers/android/system-images.ts:403-439 T1 —
I6 simlock catalog line Default image tag: <tag> after the Runtimes line of the Android block, through escapeControl; --json carries the entry as catalog.get answers it — src/cli/commands/catalog.ts:41-77 T2 —

Existing code

Commit 5e639b4.

Searches: rg -n -i "imageTag|image_tag|image-tag" src -g '!*.test.ts' (about 50 files, the ones that read or route a tag opened below); rg -n google_apis src -g '!*.test.ts' (5 non-test hits: system-images.ts:98,147,414,416, image-fit.ts:13); rg -n defaultMode src -g '!*.test.ts' (the iOS precedent, 20 hits); rg -n resolveSpec src/leasing src/core -g '!*test*' (the one leasing caller, lease-acquisition-coordinator.ts:222); rg -n "advisories\(" src/drivers src/core; rg -n "agreedDefault|renderPlatform" src/gateway; rg -n "AndroidDriver.create" src/daemon; a probe run of Catalog.resolveSpec on the reporter's images (the Examples' Today column).

Id Code (path:line) Today With this feature Handled by
X1 src/leasing/acquisition-spec-resolver.ts:66-88 resolveSpec applies the worker's default mode, builds the target (exact, class or range) and resolves it once the tagged attempt, then the untagged one (I3) T1, B1, B2
X2 src/leasing/acquisition-spec-resolver.ts:328-335 checkedSpec throws when the resolved tag differs from the request's compares with the attempt's request, so a tagged attempt may return the default tag T1, B1
X3 src/leasing/acquisition-spec-resolver.ts:280-300 resolve the warm pool's targets resolve through resolveSpec with downloads off unchanged; follows the default through X1 T1, B4
X4 src/leasing/acquisition-requests.ts:50-64 matchingRuntimes a tagged request counts only runtimes where the catalog lists an image of the tag used as is by the tagged attempt's class and range targets T1, B1 (counts every CPU: the gap under What could go wrong)
X5 src/drivers/android/catalog.ts:93-115 resolveSpec, :167-185 #taggedApiLevel; src/drivers/android/system-images.ts:403-412 #matchingImage (tagged: host ABI first, else any ABI) tagged: newest level with a fitting image of the tag, any ABI, else AndroidImageTagMissingError or a misfit RuntimeMissingError; untagged: newest fitting level with defaultTag (I7), counts only host-ABI images of the tag; its refusals of the tagged attempt trigger the fallback; an explicit tag is unchanged T1, B2, B10
X6 src/drivers/android/system-images.ts:403-418 #matchingImage untagged: host google_apis, then host, then google_apis, then any unchanged; the fallback's image order —
X7 src/core/domain.ts:268-280 fits the image tag is equal or both absent unchanged; an untagged idle device no longer serves a request whose tagged attempt resolved (What could go wrong) T1, B1
X8 src/daemon/worker-composition.ts:764-770 deviceModeWiring passes defaultModes: { ios } to leasing also passes defaultImageTags (I2) and the driver option (I5) T1, T3
X9 src/core/config-validators.ts:260-263, src/core/config-types.ts:170-172, src/core/config-defaults.ts:153, src/contract/config-schemas.ts:155 android holds defaultModels and driver keys adds defaultImageTag (I1) T1, B5
X10 src/daemon/dispatcher-status.ts:14-23 catalogGet adds defaultMode to the iOS entry adds defaultImageTag to the Android entry when set (I4) T2, B6
X11 src/contract/status-schemas.ts:307 platform catalog schema declares defaultMode optional declares defaultImageTag optional (I4) T2, B6
X12 src/gateway/routing/request-match.ts:79-100 deviceFit, :156-161 pairedRuntimesOf builds the warm-hit requirement from the request's own tag from the effective tag (I4) T2, B7
X13 src/gateway/routing/stages/warm-hit.ts:6-28, src/gateway/routing/serviceability.ts warm hit by deviceFit; serviceability counts runtimes of any tag for a tagless request warm hit follows X12; serviceability unchanged, since the fallback is always today's answer T2, B7
X14 src/cli/commands/catalog.ts:41-77 prints runtimes with the default runtime, then images adds I6's line T2, B8
X15 src/drivers/android/index.ts:712-722 advisories physical advisories and device-profile-hidden adds default-image-tag-not-installed (I5) T3, B9
X16 src/agent-device/front/allocate.ts:126 forwards imageTag only when the client sent one unchanged: an agent-device or picker lease with no tag gets the worker's default T1, B1
X17 src/mcp/server.ts:209 lease tool description "On Android, imageTag picks the system image type" adds that with none, the worker's default image tag is used where it fits T1
X18 website/src/content/docs/docs/using-devices/choosing-a-device.mdx:146-155, website/src/content/docs/docs/reference/configuration.mdx:210 "Without --image-tag, you get the google_apis image..." names the worker setting, its fallback and the host-CPU rule, that Play Store images refuse adb root, and --image-tag google_apis for a lease that needs it; the configuration table gets the key T1
X20 src/gateway/aggregate.ts:365-414 renderPlatform rebuilds each merged entry field by field; keeps defaultRuntime only when every worker agrees; drops defaultMode carries defaultImageTag the same way (I4) T2, B11
X21 src/daemon/driver-discovery.ts:63-87 DriverDiscoveryContext, :265-294 discoverAndroidDriver builds AndroidDriver from the context; the driver's config holds only its definition keys carries the default tag to the driver (I5) T3, B9
X22 src/core/fake-driver.ts:265-313 resolveSpec a tagged resolve checks only that an image of the tag exists at the level, for any model an option to refuse a tagged resolve for a named model, for B2's misfit and foreign-CPU cases T1, B2
X19 website/src/content/docs/docs/gateway/routing.mdx, website/src/content/docs/docs/worker/runtimes-and-images.mdx:34, website/src/content/docs/docs/worker/troubleshooting.mdx routing by warm devices; the catalog output; doctor findings the per-worker default in routing, the catalog line and the gateway's agreed default (T2); the advisory and its fix (T3) T2, T3

Tasks

Written after the design is checked and approved.

Written by an agent.

Activity

  1. added
    feature:specSpec in progress, business and technical together.
    on Nov 16, 2026
  2. V3RON commented on Nov 16, 2026

    @V3RON
    ContributorAuthor

    Design posted: every business section, Decisions (ADR 0078 in PR #1591), Behaviours B1–B9, Stored state S1, Interfaces I1–I6 and Existing code X1–X19. Tasks follow after the design check and approval.

    Written by an agent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature:specSpec in progress, business and technical together.platform:androidAndroid emulators or devices

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions