I have scapple files saved in iCloud Drive, but even when I save them over, they don’t save immediately. Since version 1.5, I’ve been having trouble with the time lag when saving over.
This phenomenon is occurring in the same way on two Macs.
From Scapple’s point of view, the file is being saved directly to your local hard drive. What happens to it after that is entirely out of our control.
FWIW, iCloud taking its own sweet time with uploads/downloads is a well-known problem across many applications, including Apple’s own.
1 Like
Thank you for your comment.
Yes, I can understand that the cause of the problem with the files on iCloud is on the Apple side. However, there are no problems with other applications (including third-party applications) that are stored in the same iCloud drive, and the latest content is overwritten and saved without any time lag.
Today, macOS was updated to 15.3.2, so I saved a Scapple file saved on the local (desktop) using the “command + S” action or from the menu, but it was not saved with the latest content.
That is not possible. An open file cannot save to a prior version of itself. It either saves or it doesn’t for whatever is hindering it—like a bug.
Please explain in a little more detail.
How specifically did you determine that the file was not saved? Did you open it on another computer? Did you close and reopen Scapple on the same computer? Did you identify the file and open it directly from Finder? Something else?
Thank you for your reply.
Did you open it on another computer?
Yes.
Did you close and reopen Scapple on the same computer?
Of course, yes.
Did you identify the file and open it directly from Finder?
Yes, I did.
As I mentioned at the beginning, when I save a file created in Scapple, there is a long time lag between the specific save action (command + S or from Menu) and the actual file being saved. So I have to take the same save action many times. For example, if I close Scapple immediately after taking the save action, there is a chance that the file will not be saved to the latest version even if it is saved locally on my Mac (i.e. not on iCloud drive), which is very scary.
It shouldn’t be possible for Scapple to close without saving the file locally. What iCloud then does with it is out of Scrivener’s control.
How big is the board in question?
What version of Scapple do you have, and with which version of Mac OS?
It shouldn’t be possible for Scapple to close without saving the file locally.
I believe that too.
However, in reality, Scapple just quits (without any warning) without saving the latest content. This is what happens locally on my Mac.
The version of Scapple is the latest 1.50 (13266). I purchased it from the App Store in September 2013.
In addition, the version of macOS is the latest 15.3.2.
I should add that I had no problems with Scapple before it was updated to version 1.50. Scapple is the application I use most often during the week, other than browser and mailer, and it is my favorite.
Please open a support ticket, here:
https://www.literatureandlatte.com/contact-us
Please include a copy of the board that demonstrates the problem.
Thanks.
I sent this problem to the “Ask Us a Question” form you mentioned.