(Partial crosspost from the Mac Power Users forum) As one should say when things do not work, one should also praise things that do. I had been really disappointed by the handling of the iOS 13 sync issues with Scrivener (even though it was an Apple issue, I really got the feeling the problem was no...
Haven't most people moved on to viable workarounds? Well, this user is only one (Blessed Be The Holy Stats) but I, for one, have entirely given up on iOS Scrivener and will give up on Scrivener entirely by the end of my project. Instead of spending my valuable time to work around the bug and risk m...
(Regarding the conversion to 64-bit: this is not as simple as you suggest, DevinGanger. Many APIs became deprecated and some apps needed a complete rewrite. Which some devs have done, and others have, indeed, not, leaving the app users stranded. It was mostly a reply to lunk's argument which is not,...
Lunk, when Catalina stopped supporting 32-bit apps, devs did not throw their hands in despair saying they do not work anymore. They had to ship updated apps. So if Scrivener is relying on methods that are slowly becoming unreliable, the app needs to be updated in a way that will work.
If Scrivener has to use complex workarounds to have sync work on iOS, to the point where it cannot work reliably for everyone, then it is certainly time to change the sync model. This faithful users can certainly understand and wait. If all we hear is "we can't reproduce the issue, so meh"...
It's a Scrivener issue is sync becomes unreliable because the app has to use workarounds in order to make its sync work on its complicated file format. That's calling for things to ultimately break – and they did. All the flaunted power of the app is of no use if it cannot be used. Users not on this...
I'm in the same situation as Margrad and frankly find your answer, Katherine, difficult to swallow. Scrivener is marketed as a powerhouse . We as users are willing to go through the sync hoops in exchange for the additional power the app brings, especially because it allows for complex projects (you...
@lunk : My scenario had gone badly from day 1 with the Scrivener sync. For a long time I wasn’t able to use the iOS app, had to reimport all files in a new project that then worked for a while. Since iOS 13, Scrivener has not worked on any of my devices and I have decided that sometime next year I w...
sync does not work anymore on Scrivener on iOS. Yes it does, for many users. I haven’t had the slightest problem. Well, not everybody is as lucky as you are, and there seems to be "many" users on this thread for whom it does not work, or only after much fiddling. @Amber: Yeah, I may have ...
Thank you Amber, but that is not really an acceptable response. That means that, barring convoluted workarounds, sync does not work anymore on Scrivener on iOS, making the app pretty much useless. The problem has been dragging on for some time now, it can accepted that it takes time to solve, but th...
In all this discussion of workarounds, it should be worth noting we are soon in the year 2020 and sync problems like this belong in the year 2010. I do get that the Scrivener file format is complex, tracks many different things which make sync a little more complicated, but I hope the devs are getti...
Heard from users of IA Writer, Paper and Procreate that this might be a Dropbox bug which has been fixed since by the devs of those apps… :? Could maybe the LnL team send just an email off to those guys to ascertain whether it's the same issue? I have the 12.9 iPad Pro 3rd-gen and my projects defin...
I've stopped myself from responding to this incredibly condescending message for several days... You are not the only one having had that feeling. LnL, you really give the impression that we are pestering you with our sync problems. Oh, there are workarounds, try them and see what sticks? This is m...