Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Switch from Expo Go to Expo Development Builds

Abierto
  • ¿Algo no está bien?
#123 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
android, shell, typescript
Área
documentation, mobile-dev

Línea de trabajo

Start by locating the current ANDROID_SDK and Expo Go setup instructions in the system-setup repository, and compare them with the linked overlapping issue. Update the Windows, macOS, and Linux prerequisites and development workflow for Android SDK Platform 36, Expo Development Builds, and the documented environment variables; done means the setup steps consistently support SDK 57+.

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

Descripción

Some overlap with https://github.com/upleveled/system-setup/issues/13

Expo now recommends SDK 57 for new projects, but create-expo-app currently shows SDK 54 as the option for "learning with Expo Go" (we use Expo Go currently in the curriculum):

➜  p pnpm create expo-app metro-config-ts-repro --template blank-typescript
cd metro-config-ts-repro
.../mth0v9d4-220p                        |   +1 +
Packages are cloned from the content-addressable store to the virtual store.
  Content-addressable store is at: /Users/k/Library/pnpm/store/v11
  Virtual store is at:             Library/pnpm/store/v11/links
.../mth0v9d4-220p                        | Progress: resolved 1, reused 0, downloaded 1, added 1, done

Select an Expo SDK version:

› - Use arrow-keys. Return to submit.
❯ Latest (SDK 57)
  - Recommended for most projects
    For learning with Expo Go (SDK 54)
    Other SDK version…

Switch from Expo Go to Expo Development Builds, to allow usage of SDK 57+

If you use Expo Go: Consider migrating to a development builds

Source: https://expo.dev/changelog/sdk-54

This requires adding the Android build prerequisites, in particular JDK 17 and JAVA_HOME, eg. replacing the current instructions with something like:

Windows
choco install microsoft-openjdk17 androidstudio --yes
export JAVA_HOME="$(powershell.exe -NoProfile -Command '[Environment]::GetEnvironmentVariable("JAVA_HOME", "Machine")' | tr --delete '\r')"
echo 'export ANDROID_HOME=$HOME/AppData/Local/Android/Sdk' >> ~/.bash_profile
echo 'export PATH=$PATH:$ANDROID_HOME/emulator:$ANDROID_HOME/platform-tools' >> ~/.bash_profile
source ~/.bash_profile
macOS
brew install --cask zulu@17 android-studio
echo 'export JAVA_HOME=/Library/Java/JavaVirtualMachines/zulu-17.jdk/Contents/Home' >> ~/`[[ $SHELL == *"zsh" ]] && echo '.zshenv' || echo '.bash_profile'`
echo 'export ANDROID_HOME=$HOME/Library/Android/sdk' >> ~/`[[ $SHELL == *"zsh" ]] && echo '.zshenv' || echo '.bash_profile'`
echo 'export PATH=$PATH:$ANDROID_HOME/emulator:$ANDROID_HOME/platform-tools' >> ~/`[[ $SHELL == *"zsh" ]] && echo '.zshenv' || echo '.bash_profile'`
source ~/`[[ $SHELL == *"zsh" ]] && echo '.zshenv' || echo '.bash_profile'`
Linux
sudo apt install --yes openjdk-17-jdk
sudo snap install android-studio --classic
echo "export JAVA_HOME=/usr/lib/jvm/java-17-openjdk-$(dpkg --print-architecture)" >> ~/`[[ $SHELL == *"zsh" ]] && echo '.zshenv' || echo '.bashrc'`
echo 'export ANDROID_HOME=$HOME/Android/Sdk' >> ~/`[[ $SHELL == *"zsh" ]] && echo '.zshenv' || echo '.bashrc'`
echo 'export PATH=$PATH:$ANDROID_HOME/emulator:$ANDROID_HOME/platform-tools' >> ~/`[[ $SHELL == *"zsh" ]] && echo '.zshenv' || echo '.bashrc'`
source ~/`[[ $SHELL == *"zsh" ]] && echo '.zshenv' || echo '.bashrc'`

Other changes needed:

  1. Replace the existing ANDROID_SDK environment variable with the standard ANDROID_HOME.
  2. Update the Android Studio setup to install Android SDK Platform 36.
  3. Switch the Expo test/setup from Expo Go to expo-dev-client, using pnpm expo run:android for the initial native build and pnpm expo start for normal development afterward.
Lenguaje dominante
Sin datos de lenguaje
Estrellas
30
Forks
18
Merge medio
22 min
PR fusionados (30 d)
1

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 upleveled/system-setup

Todos los issues de upleveled/system-setup

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.