If you received feedback from our support team to update your ebook’s version number for Apple Books distribution, this guide is for you.
What happens in these cases is that we receive the following error message from iBooks: “Provided asset version is not greater than live version”. Then you’re asked to make the necessary corrections. This occurs when you upload a new version of your book but the version number is not increased in the updated version.
In iBooks Author, you are asked to select if your book is a new book or an update to a published book. If you choose the latter and select your book correctly, the version number should automatically be increased.
If you exported your book and it didn’t go through with the recommended Publish Workflow, you most likely missed ‘iBooks Store Options’ where the version number can be found. To fix this issue, open your file in iBooks Author and export your book again because only then will you be given the option to modify the version number. Please see the screenshots below for reference.
If you used Pages or any external tools to create your book, follow these instructions to update the version number in your book:
“You must include the following prefix attribute in the <package> element in the OPF file:
<package xmlns="http://www.idpf.org/2007/opf" unique-identifier="bookid" version="3.0"
Note: In the prefix example above, the space between ibooks: and http:// is important; it needs to be a single, regular space character and not a return, non-breaking space, or any other kind of whitespace.
The version of your book is specified within a meta element in the Package Document. Look for the line ‘meta property’ in the OPF and format is according to the example below. The meta element has a property value of "ibooks:version":
Note: If you create a new version of a book, keep in mind that the idrefs in the OPF should always refer to the same content across different versions of the book. For example, ID "html9" should refer to the same chapter in both versions of the book, even if the actual name of the HTML file or the order of the elements in the spine changed. By keeping the idrefs the same, the annotations a customer made in one version of the book will remain in the accurate section when synced to the newer version. If you do not keep the idrefs the same, the annotations may end up in the wrong area."