In general, follow https://docs.expo.dev/, below are some quick references.
We are using eas-development builds - read more here https://docs.expo.dev/develop/development-builds/introduction/
Quick reference:
# you'll want eas-cli installed globally
# install local packages
yarn
# local development once you have build installed and are changing only javascript
yarn start
# list existing builds (most of the time, you'll install the latest matching from here)
east build:list
# Android emulator or device build
eas build --profile development --platform android
# iOs simulator build
eas build --profile development-simulator --platform ios
# iOs device build
eas build --profile development --platform ios
# register new iOs device
eas device:createFollow https://docs.expo.dev/deploy/build-project/
Quick reference:
eas build --platform all
# optionally, by platform
eas build --platform android
eas build --platform ios
https://docs.expo.dev/deploy/submit-to-app-stores/
eas submit -p android
https://docs.expo.dev/deploy/submit-to-app-stores/
eas submit -p ios
Public ones available in the final frontend package go to .env prefixed with EXPO_PUBLIC_. Access them using environment.ts. Secrets go to Expo secrets (and are afterwards available in app.config.js - and probably elsewhere - as environment variables) - see Expo secrets docs.
You can create the usual array of .env files (.env.local, .env.development). Expect for .env*.local, the are all committed to git.