managed workflow
lwhite@LarrysMBP16 aurus-lab-app % eas -v
eas-cli/0.52.0 darwin-x64 node-v16.15.0
“react-native”: “0.68.2”,
Well I had a single working build but now I get an ipa I have to make a zip which I can extract but the resulting ipa says it needs to be upgraded to work with the simulator
I must admit so far I am not in love with the new build system.
Is there a comprehensive migration guide from classic builds?
there is a bit of work initially to get moved over but expo build is far more limited and inflexible in comparison
as for running your build in simulator: Building for iOS simulators - Expo Documentation
this is my eas.json and I get something unusable
{
"build": {
"development": {
"developmentClient": true,
"distribution": "internal",
"ios": {
"simulator": true,
"image":"latest"
}
},
"preview": {
"distribution": "internal"
},
"production": {}
},
"cli": {
"version": ">= 0.52.0"
}
}
can you provide a link to the build page and also some more information on what exactly you’re seeing? the only builds i see associated with the pelicaneng account are for production
Build - Build Details — 8786a799-c6b1-42d1-84d7-a7d9a4d5ab3e — myzrl-lab-app — Expo
Download (which is an ipa and I change it to zip to unpack)
Simulator:
that is a production build, you need to use the simulator profile if you want to build for the simulator. eas build -p ios --profile simulator
notice the “production” profile on that build page and the “iOS App Store build” heading:
simulator build pages will look more like this:
ok reconfigured and I will try it
