Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Ejecutar un script con Expo cuando generas un build con EAS.

Tiempo de lectura: 2 minutos

Cuando ejecutamos un build en EAS podemos lanzar distintos hooks antes de la compilación completa, por ejemplo pruebas o modificación de archivos. Hoy vamos a aprender cómo podemos realizar este proceso.

Autobús en la noche - pexels

Expo permite ejecutar distintos hooks en el ciclo de vida del build: https://docs.expo.dev/build-reference/npm-hooks/

Para este caso vamos a utilizar justamente en el hook eas-build-post-install.

eas-build-post-install: Este hook se ejecuta después de que expo prebuild haya preparado todos los archivos, incluyendo AndroidManifest.xml, por lo que cualquier permiso añadido por otros plugins estará presente y se puede eliminar en este punto.

Crearemos el siguiente script al que llamamos hook-eas.js

Plain text
Copy to clipboard
Open code in new window
EnlighterJS 3 Syntax Highlighter
console.log("Ejecutando Hook");
console.log("Ejecutando Hook");
console.log("Ejecutando Hook");

Ahora vamos a nuestro archivo package.json y añadimos dentro de scripts

Plain text
Copy to clipboard
Open code in new window
EnlighterJS 3 Syntax Highlighter
"scripts": {
"hook-eas": "node hook-eas.js",
"eas-build-post-install": "npm run hook-eas"
},
"scripts": { "hook-eas": "node hook-eas.js", "eas-build-post-install": "npm run hook-eas" },
"scripts": {
    "hook-eas": "node hook-eas.js",
    "eas-build-post-install": "npm run hook-eas"
  },

Indicando la ruta correctamente.

Y esto eliminará ese permiso después de añadirse en tiempo de compilación.

Esto nos dá mucho juego, también podemos ejecutar nuestros scripts personalizados, ejecutar pruebas antes de realizar el build o incluso crear scripts para Android/iOS:

Plain text
Copy to clipboard
Open code in new window
EnlighterJS 3 Syntax Highlighter
if (process.env.EAS_BUILD_PLATFORM === 'android') {
console.log('Run commands for Android builds here');
} else if (process.env.EAS_BUILD_PLATFORM === 'ios') {
console.log('Run commands for iOS builds here');
}
if (process.env.EAS_BUILD_PLATFORM === 'android') { console.log('Run commands for Android builds here'); } else if (process.env.EAS_BUILD_PLATFORM === 'ios') { console.log('Run commands for iOS builds here'); }
if (process.env.EAS_BUILD_PLATFORM === 'android') {
  console.log('Run commands for Android builds here');
} else if (process.env.EAS_BUILD_PLATFORM === 'ios') {
  console.log('Run commands for iOS builds here');
}

Al ejecutar el comando:

Plain text
Copy to clipboard
Open code in new window
EnlighterJS 3 Syntax Highlighter
eas build -p android --profile production
eas build -p android --profile production
eas build -p android --profile production

Veremos en el Build Details cómo se ejecuta el Hook correcto:

Post install Hook Expo
0

Deja un comentario