Wed Nov 29, 2017 1:42 am Post
Wed Nov 29, 2017 5:03 pm Post
Thu Nov 30, 2017 12:13 am Post
Thu Nov 30, 2017 11:48 am Post
Thu Nov 30, 2017 5:40 pm Post
Wed Dec 27, 2017 1:16 am Post
kewms wrote:GFF wrote:Same issue. High Sierra, Macbook Air, saved on Dropbox since I use iOS as well.
Does moving the project out of Dropbox resolve the issue? Dropbox seems to be a common thread among people having this problem.
Wed Dec 27, 2017 8:33 am Post
GFF wrote: Not using certain features is not a useful fix for me. Ill try moving backups
Thu Dec 28, 2017 9:25 pm Post
kewms wrote:GFF wrote: Not using certain features is not a useful fix for me. Ill try moving backups
Since your previous post, we 've narrowed things down quite a bit.
Placing your live projects in the same folder as your automatic backups is a bad idea for a number of reasons, and Scrivener 3 issues a warning message telling you so. Unfortunately, this message can under some circumstances fail to appear due to a Mac OS bug, causing the project to be stuck, waiting for you to clear an invisible warning message.
Meanwhile, an oversight on our part caused the default backup location to be pre-filled to point to the same location where projects were last created, leading to the aforementioned warning message.
Moving your automatic backup location to a folder other than your live projects is a good idea anyway, and will resolve this issue. The responsible bugs are also addressed in Scrivener 3.0.1, released last week.