![]() The latest version available stopped at 18 rather than 20, and that immediately before was 12 rather than 17. However, on the iMac, which had complete (and partially duplicated) earlier versions, those from 10 onwards became patchy. Versions which had been saved when editing the document on the iMac were more patchy, though, and incomplete. Some of those more recent versions (added on the MBP) had additional iCloud-based duplicates too. I then closed the document there, opened it on my MacBook Pro, and repeated this process to take the numerals up to 20.Īt the end of this, the most recent version on the MacBook Pro showed the document correctly edited, and each version back to 10 was also available. I added the numerals 1 to 9 successively, saving the document each time to generate a new version. I started doing this on my iMac, working on a document saved to the Pages folder in iCloud Drive. My stress test was to create a lot of small changes to a longer Pages document, saving a new version every few seconds. The further that your situation strays from this, the less reliable the versions feature becomes. The bottom line is that access to previous versions of a document can be reliable, provided that you’re careful and have good iCloud connectivity. To keep this simple, I have tested this feature again on two Macs, both running macOS 10.14 Mojave and the current version (7.2 5869) of Pages, connected to the same iCloud account. My aim here is to discover whether there are workarounds or mitigations. ![]() Previously I had reported that this feature, although present and recently documented by Apple in this Support Note, is currently buggy and unreliable. I have returned to the issue of working with iWork documents shared over iCloud Drive, specifically that of access to their previous versions using the Revert To / Browse All Versions… menu command.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |