-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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 takes too long and never finishes for 0.75.2 version #46380
Comments
|
|
@SergenSiyli sorry to hear that the build time is taking too long. Can you check a couple of things for me?
|
2-) My pod install result: |
@SergenSiyli That error is because you are not running Metro. in a separate terminal window, please run:
Then relaunch the app or press the Reload button in the tab bar of the Red screen. Build was successful if you ended up in that screen. |
I solved the problem in the first item. I got a successful build on xcode. But the application still does not build with the npx react-native run-ios command. What can I do? |
Same system (Apple M2, macOS 14.6.1) and same issue, from 0.75. |
duplicate of #46352, please focus all the comments on the previous issue. Also, we use the same command on CI to build a sample project called hello world and I tested that |
Description
I m trying to run npx react-native run-ios command. But I'm waiting too long time for build. I m still waiting 1 hours.
I think the latest version of react native has problems for ios.
I've been waiting for hours for the app to open in the simulator. I tried many option. I deleted simulator ,reset macbook and created new project. but still same ı think has problem for ios build this version 0.75.2.
⠼ Building the app.........
Steps to reproduce
npx @react-native-community/cli@latest init AwesomeProject
npx react-native run-ios
React Native Version
0.75.2
Affected Platforms
Runtime - iOS, Build - MacOS
Output of
npx react-native info
Stacktrace or Logs
Reproducer
https://github.com/SergenSiyli
Screenshots and Videos
The text was updated successfully, but these errors were encountered: