Xcode build Share extension error for react native.
Sandbox: bash(72986) deny(1) file-write-data /Users/XXX/ios/Pods/resources-to-copy-XXXShareExtension.txt
I have tried to rebuild many times and still get an error........
Add a comment
|
5 Answers
update your Xcode project build option 'ENABLE_USER_SCRIPT_SANDBOXING' to 'No'.
5 Comments
BoyePanthera
This seem to be the only solution when React native ios build script runs into perssion to read and write file issues.
Talha
It didnot work for me.
Raoul Scalise
if this is already enabled, 1 - close xcode, 2 - run "rm -rf ~/Library/Developer/Xcode/DerivedData" , 3 - remove the pod causing the problem, 4 - run "pod install", 5 - add again the pod , 6 - run "pod install", 7 open the xcworkspace
vijaivir
This works for me as well, but is it safe? Shouldn't this setting always be enabled?
Erich García
Damn Bro! What a great Fix!
This solution works also for ionic projects for the error: deny(1) file-read-data
update your Xcode project build option 'ENABLE_USER_SCRIPT_SANDBOXING' to 'No'.
2 Comments
Jake
Lifesaver. This was driving me crazy.
Dibakar mandal
This worked for me. TYSM
Sandbox: swiftlint(33399) deny(1) file-read-data /Users/Your Name/Your Projects/Pods/SwiftLint/swiftlint - Xcode 15 Xcode 15.1
This error indicates that SwiftLint does not have permissions to read the specified file. To resolve such an error, you can follow these steps:
- Check the file permissions in the Terminal using the following command:
ls -l /Users/Your Name/Your Projects/Pods/SwiftLint/swiftlint
If the file has limited permissions or lacks read permission, you may need to adjust the permissions.
- Update the Sandboxing Option:
Navigate to Targets -> Project -> Build Settings -> Choose (All and Combined) -> User Script Sandboxing. Change the option from "Yes" to "No".
OR
Search 'ENABLE_USER_SCRIPT_SANDBOXING'
1 Comment
id1149103410
Find 'ENABLE_USER_SCRIPT_SANDBOXING' and set NO is easier.
If you are facing this CI pipeline issue with React Native recently, it is due to the Xcodeproj gem update to 1.26.0. As a patch, pin the gem version to <1.26.0 to resolve it.
1 Comment
cristiano2lopes
This seems like a temporary fix, relevant issue: github.com/CocoaPods/Xcodeproj/issues/989
There were two User Script Sandboxing settings, one on the target and one on the app. I had to set both to No.
1 Comment
mphair
This should be a comment on the accepted answer. But it provides more information and is potentially useful to someone. If/when you have enough rep, please come back and move this to a comment.