1) 'The document “*.numbers” could not be opened. ' and 2) '"untitled" can't be opened right now. Numbers couldn't read the file'

Thank you!

Thank you

Worked straight away! Thanks

Why can't I see the solution? All I see is Chad204's question, my similar issue, and two thank you's. But no solution!

NOW I see it all. Thank you!

You're welcome, good luck! :)

It did!!!, thanks a lot!!!

jamesfromweybridge wrote:

Thank you. That worked. But this shouldn't be happening so I assume it's a bug in the latest OS?

Are you actually on the latest OS? The latest MacOS is 10.14.6. The latest iOS/macOS is 13.2.3. Latest Numbers for Mac is 6.2.1. Latest Numbers for iOS/iPadOS is 5.2.1.

SG

Looks like a necessary evil to Force Quit it...

filecoordinationd(8) BSD System Manager's Manual filecoordinationd(8)

NAME

filecoordinationd -- system-wide file access coordination

SYNOPSIS

filecoordinationd

DESCRIPTION

filecoordinationd is used by the Foundation framework's NSFileCoordinator class to coordinate access to files by multiple processes, and to

message registered NSFilePresenters.

There are no configuration options to filecoordinationd. Users should not run filecoordinationd manually.

But...

Since this is all undocumented, I can only give our current understanding: There’s ubd, the process that actually talks to Apple’s cloud servers, gets update notifications, splits and transfers files, etc. librariand is the process that maintains the list of currently available files, the sync states, ongoing transfers and exposes all of this to Spotlight. And, last but not least, filecoordinationd. This is the file locking mechanism that makes sure only one app is writing on a file at a time. It’s also the system part of the previously discussed file notification system.

Now, as soon as there are deep hierarchies, lots of files and lots of changes, things start to fail. We have seen scenarios with each of the three subsystems broken, sometimes even beyond system reboots and iCloud deactivation/reactivation. Add a few hundred packages, open some of them, run background processes and start moving stuff around -- you can be sure that file coordination will break. In our experience it will just randomly stop reporting file changes. I may also happen that file accesses are never granted. Folder deletions have to be tried, aborted and retried in some cases.

https://www.macobserver.com/tmo/article ... -is-broken