DEV Community: Felipe Zuluaga

Publicar en la App Store desde Windows con Expo y EAS (y el error de los saltos de línea)

Felipe Zuluaga — Mon, 19 Oct 2026 18:55:03 +0000

Programo en Windows y quería llevar mi app de React Native + Expo a la App Store. ¿Se puede sin un Mac? Sí, pero con trampas. Este es el resumen del proceso y de los errores reales que me aparecieron.

Si prefieres verlo en pantalla, aquí está el video completo (con capítulos):

https://youtu.be/7aK1r9mw7Fs

Qué puedes (y qué no) hacer desde Windows

Sí: escribir el código, configurar app.config.js, compilar en la nube con EAS Build, subir con EAS Submit y probar en un iPhone real con TestFlight.

No: usar el simulador de iOS (solo existe en macOS) ni ejecutar npx expo prebuild -p ios (en Windows borra tu carpeta ios/). Alternativas: Appetize.io o un Mac en la nube. Yo usé un Mac prestado solo para el simulador.

Antes de compilar

Necesitas el Apple Developer Program: unos 99 USD al año.
En App Store Connect creas la app con nombre, idioma, bundle ID y SKU (un código interno que no se puede cambiar). El nombre que quería ya estaba ocupado, así que ten alternativas.
En app.config.js:

ios: {
  bundleIdentifier: "com.tuempresa.tuapp",
  buildNumber: "36",       // un entero que SIEMPRE sube
  supportsTablet: false,   // solo iPhone: sin capturas de iPad
}

Los errores del Mac (para probar en el simulador)

Node incompatible (expected >= 20.19.4): nvm install 20.19.4 && nvm use 20.19.4.
"Can't determine id of Simulator app": xcode-select apuntaba a un Xcode sin Simulator.app.
IPHONEOS_DEPLOYMENT_TARGET is set to 12.0: un config plugin que sube todos los pods a iOS 15.1 en el post_install (sobrevive a prebuild).

Compilar y subir

npm install -g eas-cli
eas login
eas build -p ios --profile production
eas submit -p ios --latest

En la primera build, EAS te pide el Apple ID (con doble factor) y genera por ti los certificados y los provisioning profiles: responde Sí. Con eas submit, elige App Manager para la API Key (suficiente para publicar). Luego Apple procesa el binario, normalmente en 5–10 minutos, y la build aparece en TestFlight.

El error que no esperaba: `\r: command not found`

Mi build de iOS falló con un mensaje genérico:

The "Run fastlane" step failed with an unknown error.

El error real estaba en los Xcode logs:

Script '[Expo] Configure project' failed
.../ios/Pods/../.xcode.env: line 5: \r: command not found
** ARCHIVE FAILED **

La causa:

ios/.xcode.env es un script de bash que Xcode ejecuta al compilar.
En Windows, git tiene core.autocrlf=true: el repo guarda LF, pero al hacer checkout los convierte a CRLF.
eas build sube los archivos tal como están en tu disco, no como están en git.
Bash no entiende el \r y la build falla.

Cómo detectarlo:

git ls-files --eol | grep "w/crlf"

La solución: un .gitattributes en la raíz que fuerce LF.

* text=auto eol=lf
*.bat text eol=crlf
*.cmd text eol=crlf
*.png binary
*.ttf binary

Después borra y restaura con git checkout los archivos que estaban en CRLF, ejecuta git add --renormalize ., haz commit y lanza la build de nuevo.

Lecciones: el error útil siempre está en los Xcode logs, eas build usa tu copia local, y si compilas iOS desde Windows, pon eol=lf desde el día 1.

Antes de enviar a revisión

Completa la ficha (capturas, descripción, textos), comprueba que las páginas que enlazas funcionen, elige la compilación que ya probaste en TestFlight y configura la clasificación por edades con lo que de verdad contiene tu app: Apple lo valida y puede rechazarte si no coincide.

La primera revisión puede tardar hasta una semana. Todavía estoy esperando el resultado, y lo contaré.

Resumen de comandos

nvm install 20.19.4 && nvm use 20.19.4
npm install -g eas-cli
eas login
eas build -p ios --profile production
eas submit -p ios --latest

¿Te topaste con algún error distinto? Cuéntamelo en los comentarios. Y si te sirvió, sígueme para ver cómo termina la revisión de Apple.

App Video: react-native-video VS expo-video

Felipe Zuluaga — Tue, 11 Mar 2025 14:49:01 +0000

Are you building an app with React Native and wondering which library to use for video integration?

As of today, you'll find several libraries or dependencies to handle videos in React Native. In this case, I bring you two of the most used and arguably the best options available.

Why do I say they are among the best? Besides their functionality, they have active maintenance and well-documented guides that make integration smoother. But which one should you choose? Here are some pros and cons of each, along with some conclusions.

🔹 react-native-video

https://docs.thewidlarzgroup.com/react-native-video/
This is a widely used external library for playing videos in native React Native apps.

✅ Pros:

Supports multiple video formats (MP4, MOV, etc.).
Provides advanced video control (playback, buffering, speed, subtitles, etc.).
Integrates well with react-native-video-controls for custom playback buttons.
Supports HLS and DASH streaming.
Better performance on native devices since it uses Android’s ExoPlayer and iOS’s AVPlayer.

❌ Cons:

Requires manual installation and linking in non-autolinked projects (if using react-native-cli).
Needs additional configuration for fullscreen on iOS.
Not compatible with Expo Go unless you use expo-dev-client or eject to a bare workflow.

🔹 expo-video

https://docs.expo.dev/versions/latest/sdk/video/
This is an Expo component based on expo-av that simplifies video playback in Expo Managed projects.

✅ Pros:

Easy to use in Expo, with no additional installation required.
Simple handling of playback, controls, and video state.
Natively integrated with Expo, requiring no extra configuration for iOS or Android.

❌ Cons:

Less customizable than react-native-video.
Limited format support compared to react-native-video.
Does not support subtitles natively.
May have performance issues with long videos or streaming.
The reason for researching which of these two libraries to use was to determine which one performs better in fullscreen mode and autoplay. So, based on that, here’s my conclusion:

🎥 Which works better for fullscreen and autoplay?

🔹 For fullscreen:

react-native-video is more powerful and customizable but requires extra setup on iOS.
expo-video works well in fullscreen but is less flexible.

🔹 For autoplay:

Both support autoplay, but react-native-video offers better control over buffering and video loading.

💡 Conclusion:

If you're using Expo Managed, expo-video is the easiest and fastest to set up.
If you need more control, better performance, and fullscreen compatibility, react-native-video is the best option. 🚀

8 tips that will help you stop being a junior programmer.

Felipe Zuluaga — Tue, 04 Mar 2025 21:12:29 +0000

Do you want to stop being a junior, I leave you these 8 tips to start improving your seniority level.

1. Use extensions in the editor:

Modern text editors or development environments (IDEs) allow the installation and configuration of multiple extensions that can help you improve your development time and help you have cleaner code.

2. Look in the right places:

There are forum platforms or blogs focused on development issues where doubts, errors or solutions are published, some of these are Stack Overflow and Medium.

3. Develop in English:

Currently, most companies dedicated to software development manage all their projects in English, so it is ideal that you get used to doing your personal projects in this language, so you could also share your project with other people.

4. A good statement says more than a thousand comments:

Use clear and specific names in your variables and functions so you don’t have to use comments explaining what the function does or what the variable stores example, userName, getUserData among others.

5. Join communities and participate:

On Facebook there are groups focused on programming in general or on specific languages, joining them will help you learn more, answer questions and make yourself known. Giving you the possibility of finding job offers focused on your knowledge.

6. If you have problems with a library, look for the answer directly in the documentation:

If you have an error in an installed library, go directly to its documentation and make sure you have followed the installation steps correctly, or in some cases the documentation itself indicates possible errors and how to fix them. In addition, in some cases the library has a public repository on Github and here the users of this library share the errors they have found and in some cases answer how to fix it.

7. Practice:

Start your own projects, they don’t have to be complex applications, the ideal is that you program and start implementing good practices.
It is also ideal that you publish your projects on GitHub, so you can start showing your knowledge to other people.

8. Avoid repeating code:

9. Subscribe to my networks.

Do not forget to subscribe and follow me on my social networks where I share content of interest to developers.

Youtube
Instagram