[skill-runner] Skill runner report: update-androidsdk-packages
Los mantenedores suelen responder en 1 día
@jonathanpeppers ya está trabajando en esto.
Desde el 4/11/2026.
- #13388 de @copilot-swe-agent — abierto
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 18/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- android, csharp
- Área
- build-system, mobile
Línea de trabajo
The failing check is the Gradle assembleDebug run of a temporary Android library, which errors on conflicting ANDROID_HOME and ANDROID_SDK_ROOT values. The validation path involves src/androidsdk/androidsdk.csproj and _ValidateAndroidSdkLicenses, with the SDK catalog in _PlatformPackage. Done means the SDK environment is consistent, the Gradle check passes, and the skill is rerun and validated.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Skill run: update-androidsdk-packages
Run outcome: Failed — the required Gradle compatibility check encountered conflicting Android SDK environment variables. No commit or PR was created. Candidate catalog edits remain uncommitted in the workflow checkout.
Platform catalog check: No newer stable platform level exists upstream beyond 37.2, the highest API level already in _PlatformPackage. Platform 37.2 has a newer revision (r02); that is an existing-platform refresh, not a new API level.
Candidate changes
- Emulator 37.2.12 → 37.2.13, archive build 16428233 → 16740729; SHA-256 hashes computed with the bundled helper for Linux x64, Windows x64, macOS x64, and macOS arm64, validating each download against the manifest SHA-1 and size. The higher emulator 37.3.6 is on
channel-2and was not selected; 37.2.13 is onchannel-0. - Platform 37.2 r01 → r02; SHA-256 computed with the bundled helper and manifest verification.
- Other catalog families match the published pins. Command-line tools remain at 23.0 / 16111833_latest; no new macOS-arm64 archive variant was added.
- NDK pins and package entries were left unchanged. Platform API set/count (27 entries), distinct sources for every shipped stable platform, and archive/hash-specific extraction outputs were preserved.
Validation
Passed:
TMPDIR=/tmp/gh-aw/agent/ dotnet build build-tools/Xamarin.Android.Tools.BootstrapTasks/Xamarin.Android.Tools.BootstrapTasks.csproj -v:minimal
TMPDIR=/tmp/gh-aw/agent/ dotnet restore src/androidsdk/androidsdk.csproj
TMPDIR=/tmp/gh-aw/agent/ dotnet build src/androidsdk/androidsdk.csproj --no-restore -v:minimal -p:AndroidToolchainDirectory=/tmp/gh-aw/agent/android-toolchain -p:AndroidToolchainCacheDirectory=/tmp/gh-aw/agent/android-archives -p:AndroidSdkDirectory=/tmp/gh-aw/agent/android-toolchain/sdk -p:AndroidNdkDirectory=/tmp/gh-aw/agent/android-toolchain/ndk
The prerequisite build and full current-host SDK build completed with zero warnings and zero errors. XML parsing, git diff --check, and catalog invariants passed.
Production _ValidateAndroidSdkLicenses checks also passed: absent license/marker creates the pinned fingerprint and marker; a pre-existing unrelated valid fingerprint is preserved; malformed content is rejected without modifying the license file or creating the marker. Source inspection confirms cross-process locking and atomic replacement, with no Android CLI invoked for acceptance.
Failed:
TMPDIR=/tmp/gh-aw/agent/ JAVA_HOME=/tmp/gh-aw/agent/android-toolchain/jdk-25 ANDROID_HOME=/tmp/gh-aw/agent/android-toolchain/sdk GRADLE_USER_HOME=/tmp/gh-aw/agent/gradle-user-home build-tools/gradle/gradlew --no-daemon --console=plain -p /tmp/gh-aw/agent/sdk-license-check assembleDebug
The temporary Android library used Android Gradle Plugin 9.5.0, Build Tools 37.0.0, and platform android-37.2. Gradle exited with:
Could not determine the dependencies of task ':extractDebugAnnotations'.
Several environment variables and/or system properties contain different paths to the SDK.
Please correct and use only one way to inject the SDK location.
It is recommended to use ANDROID_HOME as other methods are deprecated.
ANDROID_HOME selected the task-local SDK while inherited ANDROID_SDK_ROOT selected a different SDK. Gradle recognition of the Build Tools/platform licenses therefore remains unverified. Per the workflow instructions, execution stopped rather than committing or opening a PR after failed validation.
Follow-up
Ensure the validation process has a single consistent SDK location (prefer ANDROID_HOME; remove the conflicting deprecated ANDROID_SDK_ROOT setting), then rerun the skill and all required validation. Task-created SDK, archive, Gradle, and compatibility-project artifacts were removed.
The mandatory open-PR check completed using REST pages 1 and 2 (38 PRs, then an empty page); no exact-title [skill-runner] update-androidsdk-packages match was found.
Workflow run: https://github.com/dotnet/android/actions/runs/41382761920
Generated by Skill Runner · copilot · gpt61 · 44.6 AIC · ⌖ 9.61 AIC · ⊞ 23.5K · ◷
- expires on Dec 2, 2026, 3:32 AM UTC
- Lenguaje dominante
- C#
- Estrellas
- 2.1k
- Forks
- 579
- Merge medio
- 1 d 19 h
- PR fusionados (30 d)
- 275
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de dotnet/android
-
Area: App+Library Build
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
EditText.getText() isn't boundAbiertoArea: Mono.Android
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
dotnet/android#9192 · 4 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
needs-triage
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
Los mantenedores suelen responder en 1 día
-
Area: Mono.Bindings needs-triage
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
Los mantenedores suelen responder en 1 día
-
[generator] Investigate deferred-constructor capability scanning with shallow reference importsAbiertoneeds-triage
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
Los mantenedores suelen responder en 1 día
Todos los issues de dotnet/android
Issues similares
-
needs-triage
Dificultad 1/5 1-3 horas Aptitud para principiantes 76/100
Azure/azure-sdk-for-net#64658 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
dotnet/aspnetcore#70370 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
NethermindEth/nethermind#15684 ·
Los mantenedores suelen responder en 1 día
-
area/ai-assistant squad/flyt
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
Altinn/altinn-studio#21798 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
SubtitleEdit/subtitleedit#16699 ·
Los mantenedores suelen responder en 1 día