Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to build my project on EAS, met with unhelpful error "spawn pod ENOENT"

See original GitHub issue

Summary

Not sure if this is the right place for this, but there is no clear support channel for EAS (I have been a paying customer on 2 different projects throughout the entire early beta before the recent pricing changes).

Right now, when I try the following command:

eas build -p iOS

The build fails on EAS, all I get is an unhelpful error that says “spawn pod ENOENT” for both pods and the build: CleanShot 2021-12-03 at 11 33 29@2x

Here is the build URL:

https://expo.dev/accounts/bridgeapp/projects/bridgecrypto/builds/39267dea-efc9-454c-ae1e-1e0e3511ed03

~The weird thing is, expo prebuild works just fine so I’m not sure what I can do to debug this further.~

cc: @quinlanj

Environment

  EAS CLI 0.38.3 environment info:
    System:
      OS: macOS 12.0.1
      Shell: 5.8 - /bin/zsh
    Binaries:
      Node: 14.18.1 - ~/.volta/tools/image/node/14.18.1/bin/node
      Yarn: 1.22.17 - ~/.volta/tools/image/yarn/1.22.17/bin/yarn
      npm: 6.14.15 - ~/.volta/tools/image/node/14.18.1/bin/npm
    Utilities:
      Git: 2.30.1 - /usr/bin/git

Error output

Install Pods

Installing pods
spawn pod ENOENT

Fail Build

Build failed
spawn pod ENOENT

Reproducible demo or steps to reproduce from a blank project

I’m not sure how I would go about putting this, happens specifically on our project/account which you can find using this build URL:

https://expo.dev/accounts/bridgeapp/projects/bridgecrypto/builds/39267dea-efc9-454c-ae1e-1e0e3511ed03

Issue Analytics

State:
Created 2 years ago
Comments:23 (12 by maintainers)

Top GitHub Comments

3reactions

brentvatnecommented, Dec 3, 2021

@harrisrobin - we’re removing react-native.config.js from the expo-dev-client config plugin - https://github.com/expo/expo/pull/15380

1reaction

brentvatnecommented, Dec 6, 2021

Yeah I do, whenever I need to debug why my build fails on EAS and I don’t get a clear error, it’s easier for me to run expo prebuild and open the app in Xcode myself.

that’s fine! you should do that. run expo prebuild --clean to avoid re-applying plugins on a dirty project. also, you do get the full logs if you scroll to the bottom of the build page and download xcode logs. they’re often 10mb+ so we don’t show them inline and instead show an abridged version