Samba SMB shares are read only now in Files on iOS 14.5

Hello jerem65,

My workaround might work for you in case Apple does not fix the bug in the foreseeable future.

1. Install samba-vfs-modules

( sudo apt install samba-vfs-modules )

2 I have added the following 3 options into the [global] section into /etc/samba/smb.conf :

fruit:nfs_aces = no

fruit:aapl = yes

vfs objects = catia fruit streams_xattr

3 sudo service smbd restart

(load the new config)

Please read the relevant documentation before using this in a production environment.

I've got the same, or a similar, problem.

Prior to iOS 14.5 I accessed my Samba server (embodied using DD-WRT firmware, build 44772 11.11.2020, on a Linksys EA6700 platform) routinely using the Files app.

Since upgrading, access has been unsuccessful with the Files app. At present, with iOS 14.6, I can see the files in their directories but am unable to read or write. Meanwhile, the same Samba server continues to function with my Win7 and Win10 machines, unimpeded.

I don't have any more information to share, other than I'm frustrated with iOS and Apple.

Last comment for today:

It looks like extended attributes checks might fail this one:

testfile:com.apple.lastuseddate#PS

SMBD returns:

NT_STATUS_OBJECT_NAME_NOT_FOUND

If I read the logs correctly Files app then deletes the file off the server.

But tests using the Mail app showed that the same failed, but the Mail app does not delete the file.

So from my limited research it seems that the Files app deletes the file because it cannot read extended attributes.

Mail app also checks, but doesn't delete the file?

Hope someone figures this out. I don't want to use a 3rd party app.

Hello dirk_niblick,

It would appear that you are no longer able to write files to your external server. Take a look at the following information.

It is possible that the permissions have somehow been changed on the server. You do mention that they are showing "Read-Only". Before changing the permissions, just as a precaution, be sure that all the data contained on the drive is backed up somewhere else.

Here is how to change permissions: Change permissions for files, folders, or disks on Mac - Apple Support

Have a good day.

I have the same problem when I try to save photos. Popup error is "The operation couldn't be completed. Operation canceled". And about a month ago, everything worked flawlessly. So this is a bummer.

And it gets more interesting:

• I cannot save any photos from the iPhone Photos App to the SMB shared folder within the Files App,
• BUT I can save photos and text from my Notes App to the SMB shared folder within the Files App,
• And I can also read and delete files in the SMB shared folder using the Files App.

And vice versa:

• I cannot save any photos from the Files App's SMB shared folder to my iPhone Photos App. That save option is not there anymore!

This is not a simple all or none access rights issue. Seems to be somehow various Apps have been given/revoked different access privileges since one of the recent iOS updates.

This happens on iPhone 12, iPad 6 and iPhone 8 on iOS 14.6 - where all of them were working fine on one of the prior iOS's.

I started having this problem since upgrading to iOS14.5 as well

I have 3 more iPhones that are still on iOS 14.4 and they all continue to work as usual.

As a workaround, I have switched to using a third party app Documents by Readdle. I will go back to using Files when Apple fixes the problem.

Hello,

The only thing I can add from looking at my SMB logs is that it seems that the Files app is adding trailing forward slash "/" to the file name.

It seems the files app is then checking if the file was successfully written and cannot find the file, deleting the file straight after.

Other Apple apps are working.

I haven't quite dived into this, though.

A Windows 10 share works just fine with the Files app, so maybe a config change for SMB might allow a workaround?!

Fingers crossed - I am really reliant on that feature.

Can't edit my reply.

Hello,

I have the same issue with Files app and the error The operation couldn't be completed. Operation canceled.

Saving files from the Mail app works just fine.

The only thing I can add from looking at my SMB logs is that it seems that the Files app is adding trailing forward slash "/" to the file name.

Transfer of the file seems to be successful and a delete request is then transmitted.

My guess:

It seems the files app is then checking if the file was successfully written and cannot find the file, deleting the file straight after.

I haven't quite dived into this, though.Just looked at it for 30 minutes.

A Windows 10 share works just fine with the Files app, so maybe it's the combination of Files app and smbd? So if we are lucky a config change for SMB might allow a workaround?!

Fingers crossed - I am really reliant on that feature.

To test a theory just ran "while :; do cp testfile testfile-copy ; done" on the server ( infinite loop to copy "testfile" -> "testfile2"

and got a copy of the file I copied in the Files app.

The original "testfile" still gets deleted and the error message (...transfer canceled) still shows up.

So really, Files App seems to do a check that fails and deletes the file after a successful transfer.

Any suggestions?

OK - issue seems to be resolved by using

"vfs fruit" (part of samba-vfs-modules in a debian/ubuntu install)

I hope that is enough information to google the instructions.

See this answer for a sample config.

https://stackoverflow.com/questions/58496277/samba-4-10-server-config-using-module-vfs-fruit-changes-file-creation-mask-fo#58518622

Appreciate the detailed info and effort you put into it - Thank you. Clearly this is an iOS issue specific to "Save to Files" selection/function from only some apps that started since iOS 14.5 where it worked fine prior. To that point, if you "Copy & Paste" a file into the Files app in iOS, it works fine. Also it works fine in some iOS apps (Mail) but not others (Photos).

The suggestion you listed is a [complex] workaround to a bug which most users will not be able to perform - myself included where I have an external USB drive connected to my basic home router that uses Samba to share, and I don't even know where to begin to find/edit the config file.

As users, we prefer a fix to core of the problem which should be addressed by Apple. And I agree with you that I too do not wish to use a 3rd party app in place of the Files app (tried few and didn't like them at all).