I have been following the guides to migrate from expo build to EAS.
After a long trial and error period to get everything working I’m a bit stuck at getting the EAS build server to run as expected.
Currently, when running:
eas build --platform ios --profile production
the process hangs on the following execution:
Executing expo-updates Pods/EXUpdates » [CP-User] Generate app.manifest for expo-updates
I don’t receive any errors, it just stops and hangs until it times out at 45mins.
Im running a managed workflow and uses eas-cli version eas-cli/2.1.0 darwin-x64 node-v16.15.0. Currently I’m trying to get it to work for iOS.
When trying to run it locally with the -local flag it fails due to certificates not being installed properly. But when building for simulator locally, everything builds fine, and the app runs as expected in the device simulator.
I have seen a couple of threads that have some similarities, but they always had some error to reference. I’m drawing blanks right now…
Disclaimer: I’m very much not a JS/Expo developer and have limited understanding of the npm package manager system. So no, that’s not intentional. I’ve just added the packages I require…
But it sounds bad now that you mention it (and when I see the graph)
it seems like somewhere in your app you are importing directly from the typescript library. i’d recommend finding that and removing it. it likely is taking a very long time to compile your js bundle from scratch due to having to transform all of typescript
I see. Sounds plausible as a culprit since it’s timing out without errors and building locally without time limits .
Found that one!!! line and this was the resulting graph.