Exporting to .mobi doesn't work anymore (3.2 + Big Sur)

Scrivener Scrivener for macOS
1

Hi,
I tried to search the forum, but couldn’t find anything that mention a fix (I tried rebooting as suggested in one post).

Since the upgrade to 3.2 and Big Sur, I can’t export to .mobi anymore. I get this :

Warning(inputpreprocessor):W29004: Forcefully closed opened Tag:


  • in file: /private/var/folders/db/9gdttf7x5l55lgq4qymw27zw0000gn/T/EBOOK_TEMP/PartieUneMobi/contents.xhtml line: 0000037
    Info(prcgen):I1002: Parsing files 0000008

    Which I think means it doesn’t like some of the text which is center aligned, and this :

    Warning(prcgen):W30009: Epub navigation file does not follow the specification. Please refer to Kindle Publishing Guidelines about usage of EPUB3 Navigation support. Tag should have value in file: /private/var/folders/db/9gdttf7x5l55lgq4qymw27zw0000gn/T/EBOOK_TEMP/PartieUneMobi/contents.xhtml line: 13
    Error(prcgen):E24012: Epub Navigation file could not be built.

    I can export to .epub and open the file to Kindle Previewer 3 in order to convert it, but it would be much more convenient to be able to do it directly in Scrivener like before…

    If anyone has an answer, I’d gladly take it, thanks!
    • 2

    I don’t know if you’re aware, but Amazon recently told us to use ePub, not Mobi for Kindle Create.

    I realise you may have other reasons for wanting Mobi, but it’s starting to look like Amazon are going to drop the requirement.

    3

    yes, I’ve seen that, but it seems that for now, Kindle still require .mobi
    I send my book to a friend for beta-reading and she needs to import the .epub to Calibre to be able to import it on Kindle with a .mobi extension…

    4

    It looks to me as though Mobi export is indeed working, as you are getting error log details coming from the converter itself. If it were not running, the error would be different, and coming from Scrivener instead.

    These seem to be indicating formatting errors of some sort with the content itself, something about how the content was set up or formatted isn’t converting cleanly. Since the errors appear to be coming from your table of contents (see the ‘contents.xhtml’ file?) then you should probably review the instructions in Chapter 21 on how to correctly format an ebook ToC. The rules are quite picky, and in fact your ePub file is probably invalid as well, but Calibre is being more permissive (and possibly even fixing the problem automatically) than Amazon’s conversion tool.

    5

    Thanks,
    I will look at the chapter, but the weird thing is that I didn’t change anything about the TOC, except, maybe, what we did together on the CSS with the hidden-page tweak, here: https://forum.literatureandlatte.com/t/how-to-stop-a-scene-showing-up-in-my-toc/44036/1

    Could this cause that?

    6

    Nah, the CSS shouldn’t have anything to do with those kinds of errors. Those are all HTML issues.

    Best to tick the option in the compile options area to export source files, and have a look at what’s going on in line 13 of the contents.xhtml file. At the least that should point you to the line in Scrivener, even if the HTML you’re looking at is unfamiliar.