i would suggest disabling flipper. the library is not the most reliable and in the best case it will double your build times. if you were using it for debugging, consider this instead https://twitter.com/notbrent/status/1575236873290919936
Seeing this error on my builds as well. I would rather not disable Flipper as a long term solution simply for the network inspection it provides. In the short term, I’ll remove it from our project. Can someone at the Expo team look into this?
this is not related to expo. this is a bug in flipper. you should reach out to the flipper team for support i personally do not recommend using flipper in its current state.
Sure, but considering we did not update our Flipper dependency and our EAS builds were working just a few weeks ago, I thought I’d bring it up with Expo in the event there was a change in the build process.
i don’t believe any changes would have caused this. this error can also be reproduced locally, completely independent of eas build (see the react-native issue and stackoverflow link i shared in EAS Build iOS failing (Flipper) - #7 by brents). it’s possible that over the past few weeks you cleared or invalidate your build cache which caused Podfile.lock to be re-generated and that may have updated a flipper transitive dependency