Skip to content

Not able to build iOS application #2565

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

Open
master-codecync opened this issue Dec 19, 2024 · 3 comments
Open

Not able to build iOS application #2565

master-codecync opened this issue Dec 19, 2024 · 3 comments
Labels
question Further information is requested

Comments

@master-codecync
Copy link

master-codecync commented Dec 19, 2024

Ask your Question

react-native run-ios produces error in screenshot despite having the file at the mentioned path it says 'does not exist',

Anyone having same issue as this?

Screenshot 2024-12-19 at 8 30 16 pm (2)

@master-codecync master-codecync added the question Further information is requested label Dec 19, 2024
@szymonrybczak
Copy link
Collaborator

hey @master-codecync, you should install Cocoapods and then proceed with running run-ios, try running pod install inside ios/ directory

@master-codecync
Copy link
Author

Still same issue

@dasfisch
Copy link

dasfisch commented Apr 6, 2025

@szymonrybczak @master-codecync,

I found the same issue with RN v0.77.2 and @RNC/cli v15.0.1. It happens in native_app/node_modules/@react-native-community/cli-platform-apple/build/tools/getInfo.js. The offending line is const xcodebuild = _execa().default.sync('xcodebuild', ['-list', '-json', '-project', path().join(sourceDir, location.replace('group:', ''))]);. location, which comes from ref['@_location'] is a full path for me, so is sourceDir.

The file it comes from is contents.xcworkspacedata, which seems to have change the structure of a value for me, causing this same issue. Unsure where it's coming from, or if it's a side effect of another change during my upgrade process.

I am unsure how, but my best guess is the latest Xcode changed how things work. Changing the value in contents.xcworkspacedata to a relative path of the xcodeproj file did it for me, but I cannot guarantee this isn't gonna break other stuff. Works for me, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants