-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
create-manifest-ios.sh Bundle Expo Assets fails via on GITHUB Actions/ using Fastlane #8691
Comments
Hi @thedarkcder! What is the Github action configuration you are using? I'm not sure if you need the Expo CLI installed, because it looks like you are using the bare workflow? Or are you trying to push a new update on GH actions? |
I guess i am following advice from https://forums.expo.io/t/expo-bare-app-center-build/36472/8
a bit dirty Edit: Yes bare workflow, trying to build the bundle before deploying. Works fine on my machine but seems to have a problem on a CI machine. |
Same issue here. It seems related to expo-updates waiting for packager server which is not started during build. It is working in local only when running npm start or react-native start at the same time.
|
Can confirm I'm also running into this issue with the bare workflow on Github's macos runner. |
Any idea how to fix it? Why is this step needed at all?
|
Any ideas @byCedric ? |
We are also seeing the same errors in pipelines
after updating to Expo 38 |
I have exactly the same issue in CI.
I got below error:
For Android, I use
I got below error:
|
I ended up removing expo-updates as I was not actually using them. Obviously that fixes the issue https://github.com/expo/expo/blob/master/packages/expo-updates/README.md#removing-pre-installed-expo-updates |
It looks like the |
This is used, (if you are using bare workflow) to build the JS asset manifest. The manifest previously built using expo publish CMD. I wasn't able to identify why the built process isn't able to spawn another process as I don't have a test box. Few key points. The android build script seems to be very temperamental and doesn't always launch the metro builder. For me to get the complete c.i build working (Android +iOS ) I must start the iOS build first. This seems to work using an interactive service (local machine using a self hosted runner ) That being said I'm going to assume that the issue here is permissions to spawn a child process in a non interactive shell. If anybody ha a dedicated c.i and can share the event logs I might be able to solve it. Most likely it's a service shell permissions. |
this should be fixed in |
Latest CLi is is installed on the build server via https://github.com/expo/expo-github-action
package json
Tried removing create-manifest-ios.sh from the build phase but the app doesn't start due to it not finding the bundle.
The text was updated successfully, but these errors were encountered: