-
Notifications
You must be signed in to change notification settings - Fork 987
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
iOS build failing with 'main.jsbundle does not exist' #11961
Comments
I tried purging the Jenkins workspaces with:
But it didn't help: https://ci.status.im/job/status-react/job/nightly/1909/ |
This error was mentioned in one comment in the PR that implemented use of |
According to the logs this is the script that failed:
And when I check it's contents I see this:
#!/bin/sh
set -o errexit
export NODE_BINARY="node"
export NODE_ARGS=" --max-old-space-size=16384 "
bash -x ../node_modules/react-native/scripts/react-native-xcode.sh 2>&1 > ./react-native-xcode.log Which is simply this:
|
I tried building locally with
|
I fixed piping of logs into diff --git a/ios/StatusIm.xcodeproj/project.pbxproj b/ios/StatusIm.xcodeproj/project.pbxproj
index f61fb41de..39ac5c0eb 100644
--- a/ios/StatusIm.xcodeproj/project.pbxproj
+++ b/ios/StatusIm.xcodeproj/project.pbxproj
@@ -523,7 +523,7 @@
);
runOnlyForDeploymentPostprocessing = 0;
shellPath = /bin/sh;
- shellScript = "set -o errexit\nexport NODE_BINARY=\"node\"\nexport NODE_ARGS=\" --max-old-space-size=16384 \"\n\nbash -x ../node_modules/react-native/scripts/react-native-xcode.sh 2>&1 > ./react-native-xcode.log\n";
+ shellScript = "set -o errexit\nexport NODE_BINARY=\"node\"\nexport NODE_ARGS=\" --max-old-space-size=16384 \"\n\nbash -x ../node_modules/react-native/scripts/react-native-xcode.sh > ./react-native-xcode.log 2>&1";
};
1997449D1D0A7BEAADD6CEC8 /* [CP] Embed Pods Frameworks */ = {
isa = PBXShellScriptBuildPhase; And I got back this:
https://ci.status.im/job/status-react/job/combined/job/mobile-ios/8856 |
This is the script that is being called: |
This issue seems to be exactly the same thing, and This comment - facebook/react-native#31094 (comment) - indicates that the issue might be related to |
As per usual, it makes no fucking sense. But I'm gonna try some other things first. |
Lol, I fixed it by doing:
|
But the normal nightly failed... |
I don't know why either, but it seems like upgrading Fastlane - and some other gems - worked: #11967 But only for a manual nightly build: https://ci.status.im/job/status-react/job/combined/job/mobile-ios/8863 Makes no sense to me. |
A second manual nightly build on the same commit failed: https://ci.status.im/job/status-react/job/manual/132/ So I think the first one worked only because it accidentally ran on a host on which had |
I tried running the |
By doing dirty import Server from 'metro/src/Server'; |
And this appears to be the constructor of the server: |
This line: const metroBundle = await output.build(metroServer, requestOptions); https://github.com/facebook/metro/blob/v0.64.0/packages/metro/src/index.js#L316 |
As far as I can tell there's multiple async functions run by that Node process, and one of them exits with code 0, and kills the Metro bundle process before it finishes. I base that on different number of |
Now it seems to be hanging on this call: |
Now the behavior has changed on
And now it's getting stuck for no good reason, instead of exiting with |
And now the nightly build worked even though I didn't change anything in the repo: I swear. I hate iOS so much. So much. |
And now I'm unable to reproduce the issue, either for the PR or the nightly build. This is so dumb. |
And now it's fucked again: https://ci.status.im/job/status-react/job/nightly/1913/ |
Oh wait, but the error is different:
Looks like #11951 now... |
I'm not actually sure I fixed this permanently, but at least after merging #11967 the nightly build worked: |
The iOS nightly builds have been broken for several days because of:
Specifically
main.jsbundle does not exist
.This started happening on the 3rd of April: https://ci.status.im/job/status-react/job/nightly/1903/
The text was updated successfully, but these errors were encountered: