Unable to continue with read progress - bug

Hello,
Love the app, long time user.

The past few months, when you continue reading from within the app or using the home screen widget, it takes you back to the “On My iPad” screen and displays the message “There is no internet connection”. When starting from withing the library, it restarts your progress from the beginning.

It used to work perfectly before, hopefully it can be fixed because it is very annoying, but I recognize my hardware and updates are older :smiling_face_with_tear:.

Thank you for the amazing app!

OPDS - Komga

IPad 6 - IPadOS 17.7.3

Hi @TacoBao

Thanks for reporting this bug. We’ve had reports of opening the reader from the widget not working as expected, and it will be fixed in our next release. We will soon release a testflight beta version, I will post the link here when it’s ready so you can try it out and let us know if it works for you.

What I have never seen before is the “no internet connection” error only when opening from the widget or continue reading.

In the screenshot I can see “On my iPad”, but later you mention OPDS-Kavita. Is the comic you are trying to open in Kavita (so you are streaming it) or in your iPad local library?

Hello,
Thank you for getting back to me! I’d be happy to beta this. Like the widget problem, my issue also extends to opening any comic within the app as well.

I made some gifs that will hopefully better explain and show what’s going on:
https://imgur.com/a/0xzKdRp

Issue#1 - (see gif)
When opening a comic from the widget while the app was force closed by swiping up from the “currently open apps screen” OR when the ipad has been in sleep mode for awhile (ex: overnight), the app will open to the “On My Ipad” screen even if the comic you were trying to open was from an OPDS library. In this case, Komga.

Issue#2 - (see gif)
When opening any comic, whether from “On My Ipad” or OPDS Library, you lose all read progress and it will open from the beginning of the comic.

Issue#3 - (see gif)
Same as issue 2, however it also has the same erroneous behavior while opening from the widget. Likely related to issue 2?

I hope I was as clear at explaining all this as possible! Please shoot any more questions my way if you have them. :slight_smile:
Thank you