make sure to follow these instructions: Migrating from “expo build”
as @charliecruzan mentioned, there is some useful debugging advice in the docs also.
also, if you have Xcode installed locally, you can run
expo run:ios and it will do the same sort of build process as on EAS Build and build the app for the simulator. this command generates some other files, so once you’re done investigating, just reset to the most recent commit and run
npm install again to restore your node_modules to their previous state
so I’m pretty much sure it’s not related to the code.
we’ve handled every difference we were aware of automatically where possible and otherwise clarified differences in the migrating doc. but there may be some differences between
expo build and
eas build we didn’t account for yet, and those could be impacting you. so let us know what you find from the above.
for example, maybe you’re using env vars in your app in some places. it could be that you didn’t add env vars to your build configuration on eas build (as described in the migrating doc), so when you run your app and it tries to access the env var then it crashes.