Generated Gradle task clears DEVELOPER_DIR, so the stable-Xcode workaround from #714 doesn't reach the Android Swift build

Abierto
#738 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
kotlin, swift

Línea de trabajo

Start in build.gradle.kts at the generated buildAndroidSwiftPackageDebug and Release tasks, then reproduce with DEVELOPER_DIR pointing to the matching Xcode and run skip export --debug --no-ios. Check that the task no longer prevents the caller's Xcode selection from reaching skip android build, and verify that the native app produces the APK and AAB.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Summary

The Gradle task that Skip generates for native (Fuse) modules, buildAndroidSwiftPackageDebug / Release in build.gradle.kts, sets environment("DEVELOPER_DIR", "") before it runs skip android build. This clears the workaround recommended in #714 (point DEVELOPER_DIR at a stable Xcode). When the machine's global Xcode (xcode-select) differs from the Xcode that matches the Swift Android SDK, skip export fails in Assemble Android app.

Environment

  • Skip 1.9.11 (plugin and CLI), skip-lib 1.4.3
  • Global Xcode (xcode-select): Xcode 27.0 (Swift 6.4)
  • DEVELOPER_DIR=/Applications/Xcode-26.6.0.app/Contents/Developer, Swift 6.3.3 toolchain, swift-6.3.3-RELEASE_android SDK
  • macOS 27, Apple Silicon

Steps

  1. Keep Xcode 27 as the global Xcode and install Xcode 26.6 next to it.
  2. export DEVELOPER_DIR=/Applications/Xcode-26.6.0.app/Contents/Developer
  3. In a native app that depends on a package whose manifest isn't cached yet (for us, swift-crypto): skip export --debug --no-ios

Result

The manifest is compiled by the 6.3.3 swiftc, but against the Xcode 27 SDK (-sdk /Applications/Xcode.app/.../MacOSX27.0.sdk), and it crashes:

error: Invalid manifest (compiled with: [".../swift-6.3.3-RELEASE.xctoolchain/usr/bin/swiftc", ... "-sdk", "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX27.0.sdk", ... ".../Packages/swift-crypto/Package.swift"])
error: compile command failed due to signal 11
<unknown>:0: error: unknown argument: '-target-arch-variant'

With the same DEVELOPER_DIR, running swift package dump-package on that package by hand works, and picks MacOSX26.5.sdk. SDKROOT doesn't help: the manifest compile still resolves the SDK through xcrun.

Workaround

Point SKIP_COMMAND_OVERRIDE, which the generated task already honours, at a wrapper that restores DEVELOPER_DIR before it runs the real skip:

#!/bin/sh
export DEVELOPER_DIR="$KALISME_DEVELOPER_DIR"
exec "$KALISME_SKIP_REEL" "$@"

With it, skip export --debug --no-ios produces the APK and AAB.

Suggestion

Keep a non-empty DEVELOPER_DIR inherited from the caller (or clear it only when it points at an Xcode whose Swift doesn't match the selected toolchain), so the workaround from #714 still holds inside Gradle.

Lenguaje dominante
Swift
Estrellas
3.3k
Forks
115
Merge medio
1 d 15 h
PR fusionados (30 d)
5

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de skiptools/skip

Todos los issues de skiptools/skip

Issues similares

Más issues de Swift

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.