From 885338e7625a2308a7fc4eef5513cd31b56ba741 Mon Sep 17 00:00:00 2001 From: Reid Baker Date: Wed, 2 Oct 2024 15:45:09 -0400 Subject: [PATCH] Update Upgrading-Engine's-Android-API-version.md to reflect code move (#156108) these files moved during https://github.com/flutter/engine/pull/55186/files --- .../platforms/android/Upgrading-Engine's-Android-API-version.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/android/Upgrading-Engine's-Android-API-version.md b/docs/platforms/android/Upgrading-Engine's-Android-API-version.md index f70c8399cba..07c13b9351a 100644 --- a/docs/platforms/android/Upgrading-Engine's-Android-API-version.md +++ b/docs/platforms/android/Upgrading-Engine's-Android-API-version.md @@ -47,7 +47,7 @@ This list may become outdated, so be sure to change any references to the old SD 1. Locate the desired Android Virtual Device (AVD) from https://chrome-infra-packages.appspot.com/p/chromium/tools/android/avd/linux-amd64/. You should look at the most recently updated AVD and verify that it has the desired `generic_android.textpb` for the API version that you are modifying the engine to support. Then, determine its build_id number by clicking on the AVD instance you would like to use and looking for the build_id tag. -2. In each of the engine builders (at the time of writing: `ci/builders/linux_android_emulator_skia.json` & `ci/builders/linux_android_emulator.json`), find the `android_virtual_device` and `avd_cipd_version` dependency entries and update them to the versions you desire, e.g. +2. In each of the engine builders (at the time of writing: `ci/builders/standalone/linux_android_emulator_skia.json` & `ci/builders/standalone/linux_android_emulator.json`), find the `android_virtual_device` and `avd_cipd_version` dependency entries and update them to the versions you desire, e.g. ```json {