Have you tried tapping Cancel to stop and restart, or does the crash happen so fast that you don’t have time to do that?
[Edited for clarification (projects)]
Not sure this helps but anyway. I found a work-around to sync between my Mac and my iPad:
- On Mac or iPad, I close the Scrivener project after working on it.
- Sync on iPad invariably crashes during “file list” retrieval.
- On Mac, I remove a random Scrivener project from the Dropbox sync folder.
- On iPad, sync works fine now.
- On Mac, I put the removed Scrivener project back & wait until it’s Dropbox-synced.
- On iPad, sync again works fine. All projects are now synced.
I tried removing different Scrivener projects from the Dropbox sync folder—big ones, smaller ones, very small ones. Doesn’t make any difference. Sync always works after removing and putting back a project, respectively, no matter which.
But as soon as I work on any Scrivener project on my Mac or iPad, sync breaks down again and I have to repeat the above prodecure.
Cheers,
J.
iMac Retina 5K 27-inch (Late 2015) | macOS 10.14.6
iPad Pro 12.9" 3rd Gen | iPadOS 13.3
By “Scrivener doc”, do you mean a project?
(Anything else shouldn’t be in the sync folder in the first place.)
Yes of course, a meant project.
I’ll revise my original post to prevent misunderstandings.
Sometimes it happens very quickly, sometimes it takes a few seconds. To interrupt a process that is still running to start it again makes no sense to me. Either it works or it doesn’t work.
Wow, that sounds very elaborate and complicated. For me it wouldn’t be a viable process, even if it works after some trial and error. I mean, the synchronization process is either simple and fast, or it’s useless. I don’t want to fiddle around for hours to copy my project to the iPad, I want to write. I’m also writing this with the aspect in mind that everything worked fine before iPaOs 13, using the same hardware and the same apps.
I’m experiencing the same issue, as described in earlier posts. iPad Mini 2019, iOS v 13.3.
Does it suffice to have a really small, almost empty project to move out and back in?
Thomas, thanks for the screen shots. I have the same issues and a factory reset also didn’t fix the issue (didn’t take screenshots). 2019 iPad 12.9", iOS 13.3
Many thanks to those that have tried minimising the system down to a basic level and testing to see if the problem is still present. I recognise that is a lot of work to do for troubleshooting, but what you’ve found is valuable information. It seems we can safely exclude myriad and difficult to track down variables like which apps you use, system configuration settings and so on.
It perhaps doesn’t shed any more light on how we can reproduce it though, unfortunately. In fact if anything it makes it more difficult in that if any device could theoretically work until certain changes are made to it, the odds would be much higher that we could cause the problem to appear with the right combination of settings. Instead it appears that the issue is somehow tied more to some specific hardware issue—perhaps even at a level beneath model lines (since I’m fairly sure we’ve seen contradicting cases where the same generation/model produces different results). So unfortunately that is getting into an area very difficult to narrow down further.
That is likely because Scrivener doesn’t run a full file system scan if the top-level folders indicate no modification date change from the last sync. This way if you sync twice in a row, the second time you try it will simply detect nothing further needs to be done. It’s the same code that draws the icons on projects, indicating their current sync status.
But removing or adding a project to the sync folder from the Mac side makes syncing work, according to @gyokusai. Doesn’t that indicate the opposite from what you stated?
I was responding specifically to why no file list would be downloaded until projects have been modified. As I understand it, the checklist being described is a way they found to get the file list download working, and so conditions where the file list is not being generated in the first place are not relevant to whether it works or not.
Thanks for asking, I tried. Sadly, no—with a 100kb project, it didn’t work. Beats me why not, though.
I am sad that this post, after several month does not offer solutions.
I have got the problem since december
I could recover by restoring my projects one by one but the problem happened again.
I 100% agree with the symptoms described by the users.
It was working fine since several years.
Best regards
Do we know the status of this bug? I’m wanting to upgrade my ageing iPhone 6 to an iPhone 11 Pro… but that would mean going to iOS 13 and possibly encountering this bug? I use syncing quite a lot via dropbox between my iPhone and my Macbook Air… I assume syncing sounds fairly broken on iOS 13 ? therefor I’d go from a nice working fast sync on my current device to a broken one on my new iPhone or iPad running iOS 13 or iPadOS ?
Unfortunately, that was the case with me. I work with an iPad Pro (3rd generation) and everything worked great with iOs12. Since the upgrade to iOs13, syncing is no longer possible, no matter what I try. 
No, not necessarily.
I run Scrivener on an iPone 11 Pro and a 3rd generation iPad Pro and syncing never stopped working for me. It’s worked ever since I got iOS Scrivener.
For some it works, for some it doesn’t, and based on what L&L have posted in here, it seems that those with problems are a minority of the users. The only problem is that you won’t know until afterwards if it works or not.
Could you please stop saying here that the users who have the problem are a minority? I’m getting really tired of this presentation. I have the latest equipment and operating system. It worked before and with iOs13 it doesn’t anymore. If the problem is not an issue for you, and everything is working for you, be happy and don’t play down the bug here all the time. 
When others ask about this they should be given correct information, don’t you think?
The previous poster asked if it is safe to upgrade and you said ”no”, without the additional information that for a lot of users it does work. So I provided that to give the poster something to base the decision on.
Why do you prefer biased information?
I prefer above all that this problem is solved, because it hinders me in the production process. To say that the problem only affects a minority of users is biased information.