Skip to content
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

Unable to finish IOS bundle only. #2252

Closed
rashidbilgrami opened this issue Feb 25, 2024 · 4 comments
Closed

Unable to finish IOS bundle only. #2252

rashidbilgrami opened this issue Feb 25, 2024 · 4 comments
Labels
needs review Issue is ready to be reviewed by a maintainer

Comments

@rashidbilgrami
Copy link

rashidbilgrami commented Feb 25, 2024

Build/Submit details page URL

https://expo.dev/accounts/rashidbilgrami/projects/MAKCO/builds/590a3572-3319-48a2-ac84-f44a083b4635

Summary

I am using Windows 10, VS Code, and expo to build my app. I have used eas build --platform ios and I got the error on IS build which is listed below. Note (The Android setup was created successfully and running well)

Managed or bare?

Managed

Environment

expo-env-info 1.2.0 environment info:
System:
OS: Windows 10 10.0.19045
Binaries:
Node: 18.2.0 - C:\Program Files\nodejs\node.EXE
npm: 10.2.4 - D:\Software Installation\nodejs\npm.CMD
Watchman: 20231008.002904.0 - C:\ProgramData\chocolatey\bin\watchman.EXE
npmPackages:
expo: ~50.0.7 => 50.0.7
react: 18.2.0 => 18.2.0
react-native: 0.73.4 => 0.73.4
Expo Workflow: managed

Error output

Error
❌ error: EMFILE: too many open files, open '/var/folders/p2/2788nfhd7xq3pnnk81v00sf00000gn/T/metro-cache/23/3cebb16a1fc862eae5a66e0c1e2bdd74cde6abc8fe2d2102149a2f83c63a8db04db3e5'

▸ ARCHIVE FAILED
▸ The following build commands failed:
▸ PhaseScriptExecution Bundle\ React\ Native\ code\ and\ images /Users/expo/Library/Developer/Xcode/DerivedData/MAKCO-aviodkdgldlyytchkkbsbnekvgwu/Build/Intermediates.noindex/ArchiveIntermediates/MAKCO/IntermediateBuildFilesPath/MAKCO.build/Release-iphoneos/MAKCO.build/Script-00DD1BFF1BD5951E006B06BC.sh (in target 'MAKCO' from project 'MAKCO')
▸ (1 failure)
ARCHIVE FAILED
The following build commands failed:
PhaseScriptExecution Bundle\ React\ Native\ code\ and\ images /Users/expo/Library/Developer/Xcode/DerivedData/MAKCO-aviodkdgldlyytchkkbsbnekvgwu/Build/Intermediates.noindex/ArchiveIntermediates/MAKCO/IntermediateBuildFilesPath/MAKCO.build/Release-iphoneos/MAKCO.build/Script-00DD1BFF1BD5951E006B06BC.sh (in target 'MAKCO' from project 'MAKCO')
(1 failure)

Reproducible demo or steps to reproduce from a blank project

The code is for some important project if you want i will send you the zip file but here is the url for the git library

@rashidbilgrami rashidbilgrami added the needs review Issue is ready to be reviewed by a maintainer label Feb 25, 2024
@ferasdiab
Copy link

Did you found any solution?

@rashidbilgrami
Copy link
Author

Did you found any solution?

Nop but i am trying to figure out by deploying fresh empty project let see where to get error

@rashidbilgrami
Copy link
Author

Did you found any solution?

I have recreated a new fresh project and tried to create a package and it was successfully created an IOS package.

After installing the packages one by one and testing the IOS package I found the problem in the following packages

"deprecated-react-native-prop-types": "^5.0.0",
"patch-package": "^8.0.0",

I have no idea why I installed it even though I don't require the properties of any of my components. Any I found that this "deprecated-react-native-prop-types": "^5.0.0", required Patch-Pacakge, and patch pacakge is not supporting the expo version that I have.

So I exclude these libraries or Package and boom!!! finally, I got the IOS package.

** NOTE **
This is not necessary that you have the same library or package file issues. You have to check one by one and check which package is creating a problem.

In my case, the same issue arrived in the local machine but when I cleared the cache the app worked well IOS compiled with npx expo-doctor and the doctor threw this error while the Android has a different approach which is why the Android app was created successfully.

@szdziedzic
Copy link
Member

Thanks for solving it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs review Issue is ready to be reviewed by a maintainer
Projects
None yet
Development

No branches or pull requests

3 participants