1:14pm -0000 12/04/25 John Ralls <[email protected]> wrote: >This discussion seems germane: https://discussions.apple.com/thread/6637807
>Sync delay might account for the problem too: GnuCash renames the existing >file and writes a new one on each save. If iCloud hasn’t performed the rename >or doesn’t recognize it then it will treat the new file as a duplicate and >assign a serial number. It seems like a pretty common problem based on the >number of threads on discussions.apple.com <http://discussions.apple.com/>. I perform syncing with clients in MEGA and DropBox. I use Windows and Linux. The sync clients know about some, but not all, lock and temporary files that might cause trouble if they still exist during a future session. I got into the habit of exiting the sync clients before editing a file, closing the file, then reopening the appropriate sync client. When there is nothing to sync, the clients are exited. GnuCash is hardly the only application maintaing versions by renaming an existing version with a date stamp in the file name, then saving with the generic name. I do this manually when working on documents in which I must retain an interim version. Sometimes the sync client reports a conflict but it nearly never happens if the sync clients is closed during edits. It is in the nature of sync clients and this is how I work around. Not applicable to GnuCash but with DropBox, its older versions gave me grief with respect to renames, so I had to rename on the cloud file, then sync. No idea if existing before editing the books then restarting syncing after saving and exiting GnuCash would help with iCloud. My reply is very late. _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
