-
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 fails via make run-ios
but works with Xcode.app
after upgrading react-native
to 0.73.x
#18548
Comments
First thing I try is to manually execute
inside this bash script, the path to the variable This could mean that since this variable is not properly set the script execution could fail. |
The issue is indeed in this script, after adding some logs to
we can see that |
so moveOutputs () {
mkdir -p "$RCT_SCRIPT_OUTPUT_DIR"
# Copy all output to output_dir
cp -R -X "$TEMP_OUTPUT_DIR/." "$RCT_SCRIPT_OUTPUT_DIR" || exit 1
echo "$LIBRARY_NAME output has been written to $RCT_SCRIPT_OUTPUT_DIR:" >> "${SCRIPT_OUTPUT_FILE_0}" 2>&1
ls -1 "$RCT_SCRIPT_OUTPUT_DIR" >> "${SCRIPT_OUTPUT_FILE_0}" 2>&1
} and that is why when this script fails they just exit 🥲👌🏻👏🏻 |
Fixed by patching ref : 9fb9e69 |
Indeed, this was a great find. Thanks for solving this. I fixed using patch-package method. I see you use nix (we use it too, via flakes) and really wish there was a way to handle Xcode inside nix dips but Apple and it's lock-in. |
@sandipndev : we recently moved over to using .patch files instead with this PR -> #19451 We just don't use patch-package npm library, we apply the patches ourselves in a patch phase inside nix. and our patch now is also pretty similar ->
|
Problem
make run-ios
fails with :Since we do not want to rely on opening Xcode app I try running
xcodebuild
with -verbose flag like thiscd ios && xcodebuild -workspace StatusIm.xcworkspace -configuration Debug -scheme StatusIm -verbose | xcbeautify
Thats when I get more details on the failure :
My knee jerk reaction when i spotted
DerivedData
in the error message was that this issue could be cache related (but it wasn't)I ran
make xcode-clean
andmake clean
just and this issue was consistently reproducible.Notes
We had faced a similar issue in the past where the iOS side would build via
Xcode.App
but fail viaxcodebuild
CLI -> https://github.com/status-im/status-mobile/issues/15911guidelines by React Native team on how to deal with
FBReactNativeSpec
failures -> https://reactnative.dev/docs/0.71/new-architecture-troubleshooting#xcode-build-issuesblocks #16721
The text was updated successfully, but these errors were encountered: