@nicholas.gizzi According to what they answered to me on Twitter, yes, your content is still there. They are hoping to release a beta package today that could potentially fix this issue.
Problems after updating to macOS Sierra 10.12.4
@Andy-B, @nicholas.gizzi, @Marwan-Darwish indeed, the issue is purely with presentation (macOS 10.12.4 throws a new unexpected wrench in the content loading process). I'm very sorry it's taking us multiple days to ship this, it's just so core to the app that I need to be absolutely sure I don't introduce new issues (and that I indeed make the error reporting at this part of the app launch / document loading more robust so you won't get similar scare of "is the content there" again).
CEO & Co-founder of Manuscripts.app Ltd
I think it would be terrific if in the future you could test Manuscripts with new beta versions of macOS which are available quite sometime before release to developers like you to prevent situations like this one.
Thanks for you efforts in quickly resolving this!
@keirwilliams absolutely, which is why a new version just to ensure compatibility with the OS would have been great
@mz2 Whats happening here. I've been unable to work for 4 days now and I'm pretty much done waiting.
I don't really care why the problem is. I can switch back to Scrivener which has never lost or corrupted my data in six years.
The update is now available here as well as the usual route as an update from the app (currently available to beta users, but assuming this checks out for beta users we will make the update urgently available to all users): https://rink.hockeyapp.net/apps/280aaebd99e1f12edc41b48d909db0c4/app_versions/201
@hubob we indeed routinely test Manuscripts with beta versions of macOS, but we simply did not catch this one as it makes itself visible in a document specific way, because the release notes for the beta versions suggested absolutely no changes to the OS provided components we rely on, and because we were very close to the release of Manuscripts 1.3 which as we've noted on the newsletter will introduce new collaborative annotation functionality. It took a moment for us to readjust our release plans in a form that is safe and unlikely to introduce new issues despite the scale of sudden changes we needed to make.
@EtherealMind I understand your frustration and I very much share it. What happened is that macOS effectively removed a very specific way of removing text from a document that's backed by the WebKit text editing system, and we needed to build a replacement for it (WebKit is embedded inside Safari, Mail, many other applications – but that component was not in many other applications using that specific facility, therefore we were affected in a form that would manifest with some document states that required this feature). This operating system change completely took us by surprise because it was not captured in the OS version specific tests we ran (to be expanded based on what we learned here), and because these changes were to my knowledge entirely undocumented.
How macOS updates have become a thing where entirely undocumented changes that affect 3rd party applications in minor version updates happen, I really don't understand (incidentally there are rather scary changes in iOS 10.3 affecting the filesystem as well that I am glad I am not building functionality against at the moment), especially as macOS 10.12.4 is in large parts a bugfix update that fixes some PDF related functionality that has adversely affected many 3rd party applications!
Goes perhaps without saying but and if you continue to be affected by any issue that causes glitches for you in macOS 10.12.4 still, please let us know asap via email@example.com, attaching an example document even if you have done so in the past. We are now ready to make very fast action beta releases, it simply took us a while to replace the functionality that macOS took away.
You may also wonder "why did Manuscripts break but this other app X which does similar things was not affected" – different apps use different sets of functionality provided by the OS out of the literally thousands (tens of thousands) of application programming interfaces that Apple provides for us 3rd party developers, and you only observe really the times when something like this goes through everyone's testing out in the open. We were unlucky and unprepared this time, and as noted above we have certainly taken the lessons here on extending the OS prerelease testing we complete, and assuming basal level undocumented changes to macOS happen now at any time without warning.
CEO & Co-founder of Manuscripts.app Ltd
@mz2 Thank you for taking the time to work on this. As most of us may feel, it was just unfortunate that it wasn't caught during the betas. However, I feel this can also be a good learning lesson for upcoming changes in MacOS. I doubt they will change quite as much as it did now because of the new file system. You did your best to get it fixed.
@mz2 Thanks for the fix.
I guess I have a number of frustrations with Manuscripts related to slow performance, and odd behaviours.
Coming from writing in plain text with markdown, to the Manuscripts web view mode is jarring. I have a strong affinity for keyboard shortcuts and high speed writing, quite often Manuscripts has odd behaviour. For example, when I reach the end of a list and want to change back to paragraph mode I expect to press CR twice - once to start a new list, second to drop into a paragraph - after all ending a list is a common activity and having to invoke ⌘↩ isn't intuitive in the workflow.
Anyway, the new update solves the problem and I'm back writing again.