Debug/Build/Deploy Expo app locally without EAS/CI or Expo Go

[martin-braun]

Summary

I assume this should be a mistake. When running local builds on my own infrastructure, there is no need to ask for authentication. This is very important, because it ensures that EAS can even function in a local environment when the Expo service is not available.

Environment

  "dependencies": {
    "@expo/webpack-config": "^0.17.0",
    "expo": "~46.0.8",
    "expo-status-bar": "~1.4.0",
    "react": "18.0.0",
    "react-dom": "18.0.0",
    "react-native": "0.69.4",
    "react-native-dotenv": "^3.3.1",
    "react-native-web": "~0.18.7"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "cross-env": "^7.0.3",
    "eas-cli": "^1.0.0",
    "expo-cli": "^6.0.5",
    "npm-check-updates": "^16.0.5",
    "shx": "^0.3.4"
  },

Reproducible demo or steps to reproduce from a blank project

npx create-expo-app my-app
cd my-app
npm i eas-cli -D
eas build:configure # <- here it asks for credentials
eas build --platform android --local # <- here it asks for credentials as well

[dsokal]

Hi @martin-braun,

Could you please clarify what's the issue? Put in other words, what credentials EAS CLI is exactly expecting you to pass?

• See the guide on triggering builds from CI - https://docs.expo.dev/build/building-on-ci/
• See the guide on using local credentials - https://docs.expo.dev/app-signing/local-credentials/
• You don't need to run eas build:configure in CI, generally, this should be executed only once for the lifetime of an application.

[martin-braun]

Hi @dsokal. My goal is to be able to not use the CI of Expo altogether and just benefit from the build tools. I learned about prebuilding my projects, but trying to run my project directly from Android Studio as debug APK on my physical device gives me "Unable to load script. Make sure you're either running Metro or your bundle is packaged correctly for release".

Trying to run my project with expo run:android will result in "CommandError: Couldn't open Android app with activity "my-app://expo-development-client/?url=http%3A%2F%2F192.168.67.245%3A8081" on device "Pixel_3a".
The app might not be installed, try installing it with: npx expo run:android -d Pixel_3a"

I tried the command above to solve it, same result.

Using eas build --platform android --local will still ask me for expo.dev credentials. If I give them it will create a project on your server and link the project ID.

Look, I understand that Expo is very slick and customer-friendly with your CI tightly integrated, but a service can never remain forever. It also feels weird that I cannot opt-out of the server dependency at any time. I know that I can ditch Expo and use RN directly, but I was hoping that I can build an app with the slick Expo tool chain with peace in mind, that I can always fall back to do truly local builds without any remote dependency.

If this means that I have to eject from Expo, it defeats the purpose and I rather move to RN directly which will give me more opportunities like building for Windows and macOS.

[dsokal]

Your concerns sound reasonable. We'll try to address them soon.

[martin-braun]

@dsokal Thanks a lot. Good news though. I checked the documentations of ReactNative regarding my error above. When I run npx react-native start before debugging the APK in Android Studio, the build will work and even watch my JavaScript files for any changes. So I think I solved my issue/concern already and I want to share how local building works without the expo.dev CI being involved.

I can just run npx expo prebuild && npx react-native run-android or npx expo prebuild && npx react-native run-ios to debug without Expo Go. I can then use npx react-native bundle ... to bundle the JavaScript properly for release builds. It get's the job done.

So luckily I know that I can peacefully use Expo and its CI and have always the option to fall back to local building, as long as I keep the signing local as you mentioned.

Will my configuration be compatible with expo plugins when I decide to build locally? I.e. will expo prebuild add everything that I need to bypass Expo CI in all circumstances?

[dsokal]

I don't know if I fully understand your message but for what it's worth, you need to use react-native start because simulator/emulator builds don't bundle your JS code.
As for the other question - I think expo-cli / react-native cli should be pretty much compatible with each other.

[trevorwang]

Hi @dsokal
Is there any way to run eas build --platform android --local without expo credentials
EAS CI is great service but we don't have public network access due to company's policy

Proceeding with outdated version.

[Network] request to https://api.expo.dev/graphql failed, reason: read ECONNRESET
    Error: GraphQL request failed.