Scrivener 2.4.1 Now Available (and Submitted to the MAS)

Hello all,

Scrivener 2.4.1 is now available to users who bought from us direct (or from one of our resellers such as It has also be been submitted to the Mac App Store for review so will be available there very soon (Scrivener 2.4 went live on the App Store last night, one week after it was submitted for review). Scrivener 2.4.1 is mainly a bug-fix release which addresses a few issues that arose with 2.4. It is a free update for all registered users of Scrivener 2, and we recommend that you update from whatever version of Scrivener you are using. Updates and fixes include:

  • Fixed bug whereby file references with spaces in the file path could not be opened from Scrivener’s references pane.
  • Fixed bug whereby there could be a typing lag in scaled footnotes in the inspector.
  • Improved buffer area around editor split-divider when double-clicking to make editors same width or height.
  • Fixed bug whereby clicking the “Move…” toolbar items repeatedly and quickly could cause an exception to be thrown.
  • Fixed bug whereby replacements didn’t work in e-book NCX titles.
  • “Project Properties” is now the first pane in Meta-Data Settings.
  • Fixed bug whereby Compile presets panel resizing would not resize the presets tab view.
  • Moved “Show Titles in Scrivenings” to the Format > Options menu.
  • Updated certain non-Retina toolbar items to match those used on Retina displays.
  • Forward references are now supported in autonumbering, using e.g. <$n#keyword:tag> to refer to numbers generated using <$n:keyword:tag>.
  • Fixed bug whereby exception could be thrown when typing in old script formats.
  • Scrivener no longer throws up internal error alerts by default. The error alert feature was introduced in 2.4, but there are too many harmless errors that get thrown by plugins or OS X itself which can trigger an alert message. It can be turned back on via a new “Show internal error alerts” preference, but should only be turned on if you encounter strange problems in Scrivener.
  • Fixed bug whereby footnote markers would not have a space after them in exported RTF files if the text was not left-aligned.

The 2.4 announcement can be found here:

And you can find a full list of changes here:

To download Scrivener 2.4.1, follow the instructions below - please note that the instructions differ depending on whether you bought Scrivener directly from us or from the Mac App Store. If you have any problems, please don’t hesitate to e-mail us at for further assistance.


To download Scrivener 2.4.1, either:

• Select “Check for Updates” from the “Scrivener” menu within Scrivener itself and follow the on-screen instructions;


• Go to … atform=mac and click on “Download for Mac” to download and re-install Scrivener. (Note that there are two downloads available - one for systems running OS X 10.6 and later, and another for older systems. Both versions of Scrivener have all the same features, but only the 10.6+ version supports GateKeeper and it also makes use of some newer technologies internally.)

If you have already seen the update notification and followed the on-screen instructions to update, you don’t need to do anything else.

NOTE: If you have already tried updating but ran into the eSellerate -2003 error that has affected a few users, and you didn’t manage to resolve it via our support channels for some reason, please try re-downloading, as this should now be resolved.


Scrivener 2.4.1 has been submitted to the Mac App Store for review, so should appear on the Mac App Store within the next week or two, depending on the current review waiting times (which vary). So, please keep an eye out for the update in the “Updates” pane of the Mac App Store.

App Store users who do not wish to wait can just download and run Scrivener 2.4.1 from our site for the time being. As long as you have run Scrivener from the Mac App Store at least once, the version on our site should recognise you as a registered user. (You will need to remove Scrivener from your Applications directory before you can do this, and you may be prompted to enter your admin password to do so.) When the update becomes available on the Mac App Store, you can then just delete our regular version and re-download from the Mac App Store (or you can continue using our regular version, of course).

Thanks and all the best,

If you are using Mac OS X 10.6.x, and purchased Scrivener via the Mac App Store, do not attempt to update your software at this time. There is a small glitch in the App Store delivery system that is causing the downloaded software to fail, and once you’ve downloaded the update there is no way to go back to an older version using the MAS. We are working to fix this problem post haste, and will update this message when it is safe to update.

If you have already downloaded, and are getting the error which asks you to delete the program and download again, there is no need to do that. This problem will not be fixed by downloading the software, nor by resetting preferences. If you find yourself locked out, please refer to the instructions above, for using the direct-sale version on either a temporary or permanent basis. If you are leaning toward the latter, you should review the article on migration, so that your settings and automatic backups can be placed where the direct-sale version can read them. Whether you use the direct-sale version temporarily or permanently, you can go on working in your projects as you have.

This message only pertains to those using Mac OS X 10.6. If you are running a newer version of the operating system, it is safe to update via the MAS. If you are unsure of which version of the operating system you computer uses, you can check this information by clicking on the Apple logo in the top-left corner of the screen, and selecting “About This Mac” from the menu.

Please note that I have already submitted 2.4.1 to Apple which includes the bug fix necessary to allow Scrivener to install properly on 10.6, and I have asked Apple for an expedited review, so we hope that this will be resolved soon.

My sincere apologies to our Mac App Store users on 10.6.

All the best,