EPUB error guide
KOReader could not read one item in the EPUB reading order. Keep the file path, media type and item ID from the message so you can check that item before changing the book.
Start with
Check whether that file exists in the EPUB and can be read as the declared content type.
Different error
This message is about handling an item in the reading order. OPF_019 means the whole spine tag is missing.
Scan when
A scan can locate missing files, broken package references or parsing errors. It does not test KOReader compatibility.
Scan when the message does not name the affected path. The report shows affected paths and repair decisions. Your original EPUB stays unchanged.
Need fixed-layout, DRM, or source-file help? Check unsupported or review-first EPUB cases.
Match these report titles
Start here
The message normally includes a path and two clues in parentheses: the declared media type and manifest item ID. Keep all three.
KOReader tries to open and parse each content item in the EPUB spine. This message appears when it cannot handle one of those items. The file may be missing, unreadable, incorrectly declared or unable to parse; the message alone does not identify which cause applies.
EPUB Fixer can check the package and named content file. It may repair a verified path, manifest or supported XHTML issue when there is one clear correction. A download appears only after the repaired copy passes the structural recheck and EPUBCheck.
Copy the complete KOReader message, including the internal path, media type and item ID.
It cannot recover a missing chapter, remove DRM, decide which chapter to delete or choose the reading order. A clean EPUBCheck result does not guarantee that KOReader will display the book correctly.
1. Example report output
This illustrative example shows the clues to compare; it is not a completed user repair.
KOReader path
OEBPS/Text/chapter01.xhtml
Manifest item
id=chapter01, href=Text/chapter01.xhtml, media-type=application/xhtml+xml
Spine entry
itemref idref=chapter01 already exists.
Next check
Is the target file present and does its content parse?
Do not do this
Do not add a second spine or delete chapter01 just to suppress the message.
Follow the target file before deciding whether package repair, source recovery or reader troubleshooting is needed.
2. Next step
The same reader message can lead to different next actions.
File absent
If the file is not in the archive, download or export a complete EPUB again. A scanner cannot reconstruct the chapter.
File present
Use the scan to compare the declared path and content type, then follow the full error for the named file.
Checks pass
Retry the checked file in KOReader. If the message remains, retain the file details and reader version; EPUBCheck does not reproduce the reader's rendering.
3. Concrete path example
Compare the item ID and path rather than assuming the spine tag is missing.
<manifest> <item id="chapter01" href="Text/chapter01.xhtml" media-type="application/xhtml+xml" /> </manifest> <spine> <itemref idref="chapter01" /> </spine> Next: inspect OEBPS/Text/chapter01.xhtml itself.
The example identifies where to investigate. It does not establish that this EPUB can be automatically repaired.
Failed handling EPUB spine item 'OEBPS/Text/chapter01.xhtml' (application/xhtml+xml, chapter01).
You may see this inside a book opened in KOReader on a Kindle, Kobo, PocketBook or another supported device. It is a KOReader content-loading message, not an EPUBCheck code or a KDP upload diagnosis.
What it means
The manifest can point to a file that is absent or unreadable, or the content may not parse as the expected XHTML or SVG. An incomplete download, encryption or a reader-specific limitation can also need attention outside EPUB structure repair.
Before you edit
Use a copy of the original file. Do not delete the failing item to hide the message; that could remove a chapter from the reading order.
Where the message comes from
The importer emits this message while handling a spine content item and includes its path, media type and ID. It is distinct from a missing spine tag.
The OPF file is the EPUB's map: metadata, file list, reading order, and navigation wiring. KDP and EPUBCheck use it to decide whether the book package is coherent.
Repair example
Before: the reader names a chapter it could not handle. After a scan: use the actual missing-resource, manifest or parser finding to select the next step. If no structural issue is found, continue reader-side investigation.
Ready to retry?
The same error message can come from different files and different causes. Uploading the EPUB lets the report show the affected path or package field and whether the fix is safe to make automatically.
Upload EPUB to scanFAQ
No. KOReader can report it while reading an item from an existing spine. OPF_019 is the separate EPUBCheck message for a missing spine tag.
Do not remove it just to hide the error. The item may be a real chapter. First check the named file and its manifest reference.
No. It checks supported EPUB structure and only offers a repaired copy after revalidation. Missing content, DRM, reader bugs and rendering compatibility remain outside its repair scope.
Keep the complete message, the named file and KOReader version. Use KOReader's support workflow to investigate the remaining reader-specific behavior.
