If you have looked at our support web page this week, or read Keith's message in the forum and the festive newsletter, you will have seen that our Customer Support is closed over the Christmas and New Year period. Although we may get a chance to check emails occasionally during the holiday, we will do our best to reply to all e-mails as soon as possible after we get back in January. If you have an urgent problem involving data loss, or a major issue that is time-critical, there is a link on our support page at http://www.literatureandlatte.com/support.php that will enable you to submit an urgent message. We can’t promise a response in any particular timeframe, but we will try to prioritise genuinely urgent messages.
For anyone hoping they’ll get their book finished by this time next year, the concept of writing an entire Novel-in-a-Day is enough to prompt a swift lie-down in a darkened room. But on October 25th this year, that’s exactly what a bunch of L&L staff and forum members did - one novel, one day. Finished. Complete.
UPDATE 20/03/13: Scrivener is now back up for sale on the Mac App Store, and runs fine on 10.6.8. Thanks to all our Mac App Store users who have been very understanding about the issues we faced.
UPDATE 20/03/13: Scrivener is now back up for sale on the Mac App Store, and is once more running fine on 10.6.8. Thanks to all our Mac App Store users who have been very understanding about the issues we faced.
UPDATE: Scrivener 2.3.1 is now available on the Mac App Store. We resolved the issues mentioned below and our icon designer worked overtime to get the new, larger icon ready, and Apple hurried 2.3.1 through the review process within a few hours of submitting the updated version. Fingers crossed our App Store users won't have such long delays again and that this was a one off.
Given that we're receiving emails, tweets and forum postings daily asking when the iPad and iPhone versions of Scrivener will be released, I thought it only polite to give everyone a quick update on where things stand. (For those of you who prefer brevity, the content of this post can be summarised thus: Not for a good while yet, sorry!)