androidenv: manually (!) delete more complex version of google images
This commit was built as a revert commit followed by deletion: * Revert "androidenv: manually (!) delete oldest revision of google images". * Delete other revision. Using `systemImageType = "google_apis_playstore"` (and `abiVersion = "x86"` and `platformVersion = "28"` - that I expect resolved to `97d9d4f4a2afa8b0f5d52e90748e19c10406ca93`), the symptom is: ``` Warning: Observed package id 'system-images;android-28;google_ndk_playstore;x86' in inconsistent location '/nix/store/...-androidsdk/libexec/android-sdk/system-images/android-28/google_apis_playstore/x86' (Expected '/nix/store/...-androidsdk/libexec/android-sdk/system-images/android-28/google_ndk_playstore/x86') ... Error: Package path is not valid. Valid system image paths are: system-images;android-28;google_ndk_playstore;x86 ``` How is the actual image name `google_ndk_playstore` when the fetched image has id `google_apis_playstore`? Attempt keeping - of the two images - the one that looks simpler. For the `"28".google_apis."x86"` images, in the XML the differences are: more complex license (what is `arm-dbt`?); higher emulator. Namely: ``` <uses-license ref="android-sdk-license"/> <dependencies> <dependency path="patcher;v4"/> <dependency path="emulator"> <min-revision> <major>27</major> <minor>1</minor> <micro>7</micro> ... <uses-license ref="android-sdk-arm-dbt-license"/> <dependencies> <dependency path="patcher;v4"/> <dependency path="emulator"> <min-revision> <major>29</major> <minor>1</minor> <micro>12</micro> ``` Analogously for `"28".google_apis_playstore."x86"`.
parent
c5061889
Please register or sign in to comment