Skip to content

Android: configurable default image tag (e.g. google_apis_playstore) for leases that do not name one #1220

Open

Description

@che1404

Problem

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 (docs: "Simlock uses the google_apis image for the machine's CPU when it is installed"). Clients that cannot pass an image tag — for example a device picker UI that only sends platform/model — therefore never get an emulator with Play Store, even though the fleet has one.

We hit this testing Google Play Billing (a one-time product purchase through RevenueCat): the picker leased Pixel 9 / API 37 / google_apis without com.android.vending, so no Play purchase was possible. agent-device open --platform android --os 36 --image-tag google_apis_playstore through the proxy worked and gave an emulator with Play Store.

Request

A gateway or worker setting for the default Android image tag (and optionally API level) used when a lease does not name one, for example:

{ "android": { "defaultImageTag": "google_apis_playstore" } }

Alternatively, expose the available image tags in the catalog in a way device-picker clients can offer as a choice per lease.

Environment

simlock 0.4.0 (gateway + workers), agent-device 0.21.35 proxy. Images on the Android worker: API 29/33/35/36 google_apis, API 36 google_apis_playstore (x86_64), API 37 google_apis.

Activity

  1. added
    request:newInbox. Never picked up, body never edited.
    on Nov 5, 2026
  2. V3RON commented on Nov 16, 2026

    @V3RON
    Contributor

    Being specified in #1590. This issue stays open until that feature ships.

    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

    platform:androidAndroid emulators or devicesrequest:newInbox. Never picked up, body never edited.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions