error while build iOS app in Xcode : Sandbox: rsync.samba (13105) deny(1) file-write-create, Flutter failed to write to a file

Question

while building iOS app on Xcode I got these 2 errors, I tried to build the iOS on visual studio code and I got the same errors. the operating system macOS 14.0 beta. processor M1 Pro

errors messages

Could downgrading the operating system fix that issue?

Useful question, and useful answer - should be reopen

timbre timbre
– timbre timbre

2025-05-14 18:58:57 +00:00
Commented May 14 at 18:58 — timbre timbre
– timbre timbre, Commented May 14 at 18:58

TylerH · Accepted Answer · 2025-03-13 13:21:51Z

1190

In Xcode, go to your project's Build Settings menu. In the Build Options section, set the property ENABLE_USER_SCRIPT_SANDBOXING to 'No'.

edited Mar 13 at 13:21

TylerH

21.3k84 gold badges84 silver badges121 bronze badges

answered Jul 6, 2023 at 6:48

hasayakey

12.1k2 gold badges12 silver badges6 bronze badges

Sign up to request clarification or add additional context in comments.

10 Comments

Cesar Over a year ago

this is indeed the correct answer. but why is this needed at all?

jonathan3087 Over a year ago

rsync 9974 and rsync 9987 went away, but now I have errors for rsync 10090 and 10093 which say: Sandbox: rsync(10090) deny(1) file-write-create /Users/jonathan/Library/Developer/Xcode/DerivedData/Go_Cart-cfpedjquevfpxzaopshdpjedieco/Build/Products/Debug-iphoneos/XCFrameworkIntermediates/Realm/Headers

Plasma Over a year ago

I have set this to NO and same as @jonathan3087 I still have similar errors .. Sandbox: rsync(37912) deny(1) file-write-create /Users/plasma/Library/Developer/Xcode/DerivedData/RTSPtest-fjamhnfxeyhjfjabnbhpcrctfmth/Build/Products/Debug-iphoneos/XCFrameworkIntermediates/MobileVLCKit/dSYMs Sandbox: rsync(37913) deny(1) file-write-create /Users/plasma/Library/Developer/Xcode/DerivedData/RTSPtest-fjamhnfxeyhjfjabnbhpcrctfmth/Build/Products/Debug-iphoneos/XCFrameworkIntermediates/MobileVLCKit/MobileVLCKit.framework/.MobileVLCKit.izJrf5

Daniel Wu Over a year ago

@Cesar XCode 15 introduces new 'sandboxing' feature, and recommends it to us in yellow warning mark. Going along with it is detrimental to flutter development however, because 'sandboxing' limits our app's interaction with the OS and access to our storage, which is important in development stage. Sandboxing is only useful for production, IMHO, to protect end user from evil apps. I don't know what where XCode's makers thinking.

Yogesh Rathore Over a year ago

Update your Xcode project build option ENABLE_USER_SCRIPT_SANDBOXING to 'No'. this solution is working for me.

|

N.K. · Accepted Answer · 2023-09-24 15:31:58Z

111

@hasayakey 's answer worked for me, but I wanted to add some extra info about how to find this setting.

To find the 'ENABLE_USER_SCRIPT_SANDBOXING' go to the Search icon tab in the left hand panel within Xcode. Ensure you are searching within the 'Runner' workspace, configured the search to ignore text and then press enter to search with text 'ENABLE_USER_SCRIPT_SANDBOXING'.

In Xcode 14/15, the result should look like this:

Alternatively, you can navigate to this setting by going to:

Xcode > Project > Runner > Build Settings > Build Options > User Script Sandboxing (near the bottom of build options)

answered Sep 24, 2023 at 15:31

N.K.

6481 gold badge5 silver badges11 bronze badges

2 Comments

ICL1901 Over a year ago

Anyone know if the App Review folks will flag this fix?

N.K. Over a year ago

@ICL1901 I have had this setting in multiple app store releases now and it has been fine.

TylerH · Accepted Answer · 2025-03-13 13:24:16Z

14

I had two targets in my project: Runner, and Flutter Assemble. I had never seen the latter before, so I switched ENABLE_USER_SCRIPT_SANDBOXING to 'No' for them both, and it worked.

edited Mar 13 at 13:24

TylerH

21.3k84 gold badges84 silver badges121 bronze badges

answered Nov 29, 2023 at 0:22

DaraJ

3,2554 gold badges39 silver badges66 bronze badges

Comments

neronovs · Accepted Answer · 2024-03-19 12:15:52Z

13

In my case, after integration of Cleverpush SDK, I got the issue.

In the iOS project, in the XCode I had to do the next steps:

Tap on 'Runner' in the tree on the left toolbar;
Select 'CleverPushNotificationServiceExtension' in the 'targets' list;
Select 'Building Settings' element on the columns;
Select 'All' & 'Combined';
Filter by 'ENABLE_USER_SCRIPT_SANDBOXING' keyword;
Set the 'User Script Sandboxing' parameter to 'No'.

answered Mar 19, 2024 at 12:15

neronovs

6048 silver badges10 bronze badges

Comments

TylerH · Accepted Answer · 2025-03-13 13:24:55Z

11

Turning it off (setting to No) doesn't fix issues for my Flutter project; I got another set of similar errors.

I got the solution following these steps:

Set "User Script Sandboxing" to "No" from Project- > Build Settings
Exit Xcode
run Flutter clean, then Flutter pub get
run pod install from the terminal (inside ios folder)

edited Mar 13 at 13:24

TylerH

21.3k84 gold badges84 silver badges121 bronze badges

answered Nov 6, 2023 at 16:17

touhid udoy

4,4703 gold badges23 silver badges34 bronze badges

Comments

TylerH · Accepted Answer · 2025-03-13 13:25:25Z

9

If you are using React Native make sure to check "User Script Sandboxing" in your Pods project (NOT ONLY the <project name> project). For me it was "Yes" by default.

edited Mar 13 at 13:25

TylerH

21.3k84 gold badges84 silver badges121 bronze badges

answered Oct 28, 2024 at 13:54

nezort11

7032 gold badges10 silver badges13 bronze badges

Comments

asifmohd · Accepted Answer · 2024-10-31 05:48:34Z

Ever since the release of a new xcodeproj ruby gem version 1.26.0 on 27th Oct 2024, we started seeing rsync.samba errors on our Xcode projects when we were building using Xcode 15.x.

The solution for this was to explicitly add a version lock to xcodeproj version 1.25.0 in our project's Gemfile.

gem 'xcodeproj', '1.25.0'

Or update to a cocoapods version > 1.16.1:

gem 'cocoapods', '>= 1.16.1'

Post this change we need to run:

bundle install to update local gems for this project.
bundle exec pod install to regenerate Pods.xcodeproj

(If you are not using Gemfile or bundler to manage gems, check the version of locally installed xcodeproj version using xcodeproj --version. And uninstall the 1.26.0 version using gem uninstall xcodeproj (This uninstallation is only required if we are unable to update to 1.16.1 cocoapod release.))

Why does this help fix the build errors?

Cocoapods internally uses the xcodeproj gem to generate a Pods.xcodeproj/project.pbxproj file.
xcodeproj 1.26.0 sets the ENABLE_USER_SCRIPT_SANDBOXING setting to YES for most of the Pod targets for Xcode 16 compatibility. (Github PR)
By downgrading to 1.25.0 we ensure that this build setting is not set to YES, which helps resolve rsync.samba build errors on Xcode 15.
NOTE: If you are already on Xcode 16, it is not recommended to lock xcodeproj gem to 1.25.0 as projects which depend on Cocoapods can start failing.

EDIT:

Cocoapods 1.16.1 release is out as well. Updating to this version should help resolve the issue as well. (Make sure to remove gem 'xcodeproj', '1.25.0' in Gemfile to install this version)

Mahinthan177 · Accepted Answer · 2025-01-29 12:42:01Z

2

Set “No” to all “User Script Sandboxing” in all targets.

answered Jan 29 at 12:42

Mahinthan177

8941 gold badge11 silver badges9 bronze badges

Comments

TylerH · Accepted Answer · 2025-03-13 13:26:16Z

2

In case ENABLE_USER_SCRIPT_SANDBOXING is already set to NO, and you are still receiving the error, then:

Close Xcode and cd ~/Library/Developer/Xcode/DerivedData in terminal
Remove directory/ies with the project names rm -rf <name>*
Delete Xcode simulators locking the disk: xcrun simctl delete unavailable
cd <project>/ios and pod install
Start Xcode again and build/archive your project

Setting permissions to 777 using chmod, is a no-no and also unnecessary.

edited Mar 13 at 13:26

TylerH

21.3k84 gold badges84 silver badges121 bronze badges

answered Jul 24, 2024 at 8:38

user25708886

314 bronze badges

Comments

desertnaut · Accepted Answer · 2024-09-27 20:58:12Z

1

A solution for someone who uses CocoaPods as Package manager: To resolve properly without set ENABLE_USER_SCRIPT_SANDBOXING = No, first you need to comment in the Podfile the command use_frameworks!, i.e. leaving it out (in this way you be able to set in Build Phases -> Link Binary with Libraries the libPods-namePod.a instead of namePod.framework) then run pod install and finally build and run.

edited Sep 27, 2024 at 20:58

desertnaut

60.8k32 gold badges155 silver badges183 bronze badges

answered Feb 17, 2024 at 16:48

Ariel Díaz

112 bronze badges

1 Comment

Vinod Supnekar Over a year ago

Worked for me, i did used Swift package manager, then shifted to Podfile due to RxSwift support, and got above issue. Tried "ENABLE_USER_SCRIPT_SANDBOXING = No" but not worked. Then Podfile "use_frameworks!" commenting worked.

desertnaut · Accepted Answer · 2024-09-27 20:57:01Z

0

//:configuration = Debug
ENABLE_USER_SCRIPT_SANDBOXING = NO

//:configuration = Release
ENABLE_USER_SCRIPT_SANDBOXING = NO

//:completeSettings = some
ENABLE_USER_SCRIPT_SANDBOXING

This method worked for me.

edited Sep 27, 2024 at 20:57

desertnaut

60.8k32 gold badges155 silver badges183 bronze badges

answered Aug 15, 2024 at 10:08

kundan Kumar

92 bronze badges

1 Comment

Jeremy Caney Over a year ago

Thank you for your interest in contributing to the Stack Overflow community. This question already has quite a few answers—including one that has been extensively validated by the community. Are you certain your approach hasn’t been given previously? If so, it would be useful to explain how your approach is different, under what circumstances your approach might be preferred, and/or why you think the previous answers aren’t sufficient. Can you kindly edit your answer to offer an explanation?

TylerH · Accepted Answer · 2025-03-13 13:19:52Z

0

In XCode 15.1 I was having same problem.

I deleted Homebrew, and then reinstalled it, reinstalled cocoapods, and then installed pods, and it worked.

edited Mar 13 at 13:19

TylerH

21.3k84 gold badges84 silver badges121 bronze badges

answered Oct 29, 2024 at 8:26

Abdul Momen

4095 silver badges13 bronze badges

1 Comment

Aji Saputra Raka Siwi Apr 2 at 13:12

How can deleting and reinstalling resolve this problem? I've just installed latest version of Xcode, CocoaPods and all Pods library, but still get error. In my case, so far set the User Script Sanboxing to NO is the solution

Collectives™ on Stack Overflow

error while build iOS app in Xcode : Sandbox: rsync.samba (13105) deny(1) file-write-create, Flutter failed to write to a file

12 Answers 12

10 Comments

2 Comments

Comments

Comments

Comments

Comments

Why does this help fix the build errors?

Comments

Comments

Comments

1 Comment

1 Comment

1 Comment

Linked

Hot Network Questions

Collectives™ on Stack Overflow

12 Answers 12

10 Comments

2 Comments

Comments

Comments

Comments

Comments

Why does this help fix the build errors?

Comments

Comments

Comments

1 Comment

1 Comment

1 Comment

Linked

Related