The wear-os-samples now demonstrate running the Wear 4 emulator (API 33) via Gradle Managed Devices ...

# compose-wear

[yschimke]

The wear-os-samples now demonstrate running the Wear 4 emulator (API 33) via Gradle Managed Devices in Github. Mostly this CL https://github.com/android/wear-os-samples/commit/12f0c378d6115e08fff453bef017b03c129f0d3a

It requires a non stable AGP, so won't suit everyone.

[yschimke]

But you will need these two edits for it to run https://github.com/android/wear-os-samples/commit/1181807eae0275f87bae8bfbdf041f8384fe3097

[yschimke]

If you are using ReactiveCircus, this is an example PR https://github.com/google/horologist/pull/1274/files

[yschimke]

- name: Run tests
        uses: reactivecircus/android-emulator-runner@v2
        with:
          api-level: 33
          target: android-wear
          profile: wearos_large_round
          channel: beta
          arch: x86_64

[florent]

What does sdkchannel=3 means?

[yschimke]

From sdkmanager

[yschimke]

--channel=<channelId>: Include packages in channels up to <channelId>.
Common channels are:
0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).

[yschimke]

I guess it should be 1, but canary picks up beta also

[Alex Vanyo]

straight to the bleeding edge