"The document...could not be autosaved. The file has been changed by another application"

NicolaThread wrote:

It is saved on our work server,

The problem is related to the configuration of your work server. You may have to make adjustments there, if you are not allowed to store the document in iCloud, which would make collaboration and sharing easier.

SG

I am having this same issue with a macOS Ventura M2 Mac Studio using a macOS Ventura 2017 i7 iMac as a file server. I have a 2019 i9 MacBook Pro running Ventura that is not having this issue.

This issue is happening with existing documents. I can create a new document on the iMac's SMB share and save changes. But after saving and closing, I cannot save changes after subsequent opens. I get the pictured message.

If I try to save as... I get a spinning wheel until I force quit the app.

@SGIII: It's not obvious to everyone what changes that might be. Any suggestions?

It is a very annoying bug and I think there is at least a bit of responsibility for Apple to address this issue.

Easy suggestion: an item in the Pages/Numbers (etc.) Settings where you can actually disable Autosave.

As you may know, this is a user-to-user forum. You may get more insight by giving feedback directly to Apple via Numbers > Provide Numbers Feedback in your menu. My personal solution: use iCloud, for which Numbers is appears to be designed. I understand that may not be possible in some corporate environments.

SG

Surely Apple keeps an eye on these forums... But thanks for the tip. I will provide Apple with feedback.

If you (or anyone else) have/has any tips concerning a QNAP NAS and what settings might mitigate this behaviour that would be great!

We see Apple Community Specialists here, but I think your question needs expertise with NAS. You may not receive a reply when you post feedback. If you don't, then you may need to try to contact Apple Support though someone else may need to suggest how to do that for a question like this.

You are probably aware that each new release of macOS brings added attention to security. This is only a guess, but that may be why you see different behavior than before.

SG

I was getting this issue with a Mac Studio M2 Max running Ventura and with a Numbers file opened from an Intel iMac running Ventura and macOS file sharing. My Intel Ventura Macs were not having any issue.

I upgraded the Mac Studio to Sonoma and the issue is now resolved. I did this after determining the issue was also not present on a MacBook Pro M2 running Sonoma.

Seems like the file server side can't properly lock the file when it's in use, in some cases, unless it's a package. Adobe was having this issue with SMB shares as well. For a while, using AFP got around that. Seems to be better with SMB now.

FYI:

After coming across a similar issue with the same errors, user was working in Number (and Pages app had same behavior) when saving to an SMB file share.

Solution (tested and verified!) :

In Pages or Numbers application, open File menu -> Advanced -> Change File Type -> change to "Package". 

This does not seem to change the actual user experience of the file type or cause any negatives in anyway, yet resolves the issue.

Cheers!

We have the same problem. We use a Synology NAS SMB. DSM 7.1.x up to date.

What should we change to make this work ?

It was working until ventura. So it is a change in SMB of Ventura.

When we test it under macOS Monterey to the same server. It is working Fine, also using Pages version 13.0.

I have the same issue. Very frustrating indeed. Didn't used to be an issue then all of a sudden... issue. I have no fix currently.

Amen bro. This is bugging me as ****. BTW not all documents need to be shared. So I see no benefit to put it in the cloud., also iCloud would cost me an arm and a leg to hold all my documents.

Have no way of replicating that here. But if changing to Package works then that's great news!

SG