[Bug]: unable to read EPUB doc

[Asur30]

Steps to reproduce

1.switch to international reader.
2 open imported book
3.

Expected behaviour

It should show no of pages or progress completed

Actual behaviour

It is unable to read the document i imported and opened while selecting internal reader
But opens wen i select external reader and then chose myne reader.

Device name

OnePlus pad

Android version

Android 14

Myne version

3.8.0

Device logs

VID-20240522-WA0020.mp4

Additional information

No response

[starry-shivam]

@Asur30 Thanks for reporting. I think this might be happening because the internal reader parses the book based on the toc.ncx (table of contents) file located within the epub archive if it's available. If the ncx file is not present, then it will parse the book using the spine method.

What might be happening in this case is that the book contains a toc.ncx file, but it is invalid or empty, hence it was not able to parse any chapters and the book was rendered as empty. I'll try to fix this issue in the next release by checking if the toc.ncx file exists and is not empty or invalid. If it is valid, then it will be used for parsing; otherwise, it will fall back to the spine-based parsing method. While spine-based parsing is generally not as accurate in mapping chapters as toc, it's at least better than having an empty book :)

If you don't mind, can you send me that particular EPUB book via email ([email protected]) or in our Telegram group, which was causing trouble? It'll help me reproduce the problem more easily while I'm working on it and ensure that it's working as expected.

[starry-shivam]

If you don't mind, can you send me that particular EPUB book via email ([email protected]) or in our Telegram group, which was causing trouble? It'll help me reproduce the problem more easily while I'm working on it and ensure that it's working as expected.

@Asur30 Waiting for your response.

[Asur30]

Here's my issue #177 (comment) And below is the file attached with which im having the issue

…

On Mon, 3 Jun 2024, 21:27 Stɑrry Shivɑm, ***@***.***> wrote: Closed #177 <#177> as completed via #180 <#180>. — Reply to this email directly, view it on GitHub <#177 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BEAMDJQ22XHBDUKOACN5K2TZFSHAHAVCNFSM6AAAAABIDXQ2HWVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGAZDGNJZGY3DCNA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Asur30]

If you don't mind, can you send me that particular EPUB book via email ([email protected]) or in our Telegram group, which was causing trouble? It'll help me reproduce the problem more easily while I'm working on it and ensure that it's working as expected.

@Asur30 Waiting for your response.

And yeh, sorry for the late response as I was busy with my exams

[Asur30]

I just updated to the latest version and I'm still having the same issue...

May be the problem is with the EPUB file that I've sent you via email

[starry-shivam]

I initially made the fix based on a hunch because I didn't have the EPUB file, which was causing trouble, to know exactly what was going wrong. Now that I have the file, I can investigate it and fix it properly.