ebook disappears from list

[JunkyardCat]

so i have the book open and just multitask in and out of the app. then one time my ebook disappeared from the list. this hasnt happened in the past before. not sure if this is a one time thjng or not. im using 2.2.9 version

when i tried to import the book again it gives me an error
Error importing xxxxxinsertbooknamexxxx Failed to execute 'transaction' on 'IDBDatabase': One of the specified object stores was not found.

[arianneorpilla]

I've never seen this before, will have to see and play around and get some practical use time with TTU within the app to see if I cause this or if it's caused by TTU itself.

Though if TTU itself loads, I reckon this issue is not really my jurisdiction. If you can catch the error happening again and give some more details or a screenshot by chance, I can give this a more thorough investigation.

[JunkyardCat]

@lrorpilla
i opened ttu but it just says "Loading..."

when i import an ebook the message i mentioned earlier appears

[vgf89]

My ebook list actually got completely wiped today too after imported and tried opening a couple of epubs. I was able to reimport them and found my place in them again, but yikes, I do not want that to happen when I'm far into a book...

[arianneorpilla]

Hi @JunkyardCat, I changed the cache mode of the WebView to always load if available even if expired. I actually have never been able to reproduce this issue, but I'd like to encourage you to try and see if you ever run into this issue again with the new cache mode.

This build includes a work in progress 2.4.0 (only supporting Japanese at the moment) that includes an overhaul of the dictionary system and should be much, much faster than the current system, supports wildcard searching (? or ？ for one character, * or ※ (こめ) for zero to any characters) but will require a fresh installation. You can get the build here.

[0805w4o0980]

Had the exact same problem as @JunkyardCat, downloaded 2.4.0 and it seems to be fixed. Also, it is indeed much, much faster!

[arianneorpilla]

I'm very happy to hear that the new schema has made a huge difference, I might write a blog post at some point detailing the the tricks and tribulations taken for it to finally get to where it is now.

I'm fearful for this issue in particular that the reader database having issues is something that happens with time in some devices, so I'll continue to keep a watchful eye on this in case there are reports about it again.

[arianneorpilla]

2.4 is out of preview, but I am happy to hear from anyone who might still be experiencing this issue.

[0805w4o0980]

same problem occured again unfortunately, everything was fine for the two weeks I've had 2.4 but today all ebooks I had disappeared, and If I try to import them again I get the same "Failed to execute 'transaction' on 'IDBDatabase': One of the specified object stores was not found."

[arianneorpilla]

The problem here is that IndexedDB is clearing on its own and there is no way to turn on the Persistent Storage option in the Reader Settings as there is no equivalent of "bookmarking" the page for an Android WebView versus simply bookmarking on Chrome. This is a really frustrating oversight by Chromium.

I don't personally experience this issue, but I barely use any of the storage on my phone so that's probably why I've never encountered this. I will continue to investigate what I can do about this. I can probably just distribute the app with a cloud sync option that the web-hosted ッツ offers, and that would circumvent having to use local storage but I would really like to figure this out somehow.

I'd like the app to work really well just locally and worst comes to worst this might need taking a hard rework on my own fork to change how the reader persists data.

[arianneorpilla]

@0805w4o0980
I am trying to get the information that I need in order to fix this issue, in the meantime, might I ask how much free space you have on your device? My hypothesis is that this issue happens if you're pressed for storage, as I never get this issue and I have lots of free space, but I could be wrong. Any info would help (how many books you imported, device info, etc.)

[0805w4o0980]

@lrorpilla I have 62 Gb free, but come to think of it, I just downloaded 30 gb worth of content and that's when the issue occured, it seems your hypothesis is correct.

[arianneorpilla]

If you can show that this issue is indeed happening because of lower storage and demonstrate cause and effect, (either with a video or so) then I will take a look.

If you can show from two separate fresh installations, one with low storage and one with high storage, that this issue occurs, then that would probably confirm it. Otherwise, it's honestly difficult for me to take action on this issue because it's really hard for me to replicate unfortunately. I will see if I can bloat my own storage and if this happens.

[arianneorpilla]

I think my approach to this issue will be to manually backup IndexedDB on my end and if ever this issue occurs, I can restore from a backup.

Still haven't personally experienced this on my devices but I think it's a feasible strategy. Am on hiatus at the moment but I'll note it down for the future.

[vgf89]

So I lost my books again. However I now can't add any books. I updated jidoujisho and when I try to add a book I get this. I'm on version 2.8.3 right now.

[arianneorpilla]

Only a fresh install will fix once you get the above message, I personally still have never experienced getting my books wiped so it's hard for me to debug and fix.

[brishtibheja]

This has happened to me two times now. I open a book in ttu reader and keep the app open in the background and do something else in another app, and then all the ttu data gets wiped out for some reason.

[arianneorpilla]

I have never had this issue happen to me. Either your device encounters this problem or you don't, really.

I don't have a solution at present but this is something that I am always keeping in mind.

[arianneorpilla]

@Katsumi-III
Please keep discussions of this issue here. I haven't encountered this issue and my suspicion is that it is because I never run out of storage space on my device, which is probably the flag for the WebView dumping temporary data for space.

This is no issue for myself day to day, so I haven't bothered to prioritise this issue -- I want to come up with a solution of this probably by forking the reader to use local mobile storage but that is a problem that will take time for me to move towards.

[brishtibheja]

In case this information helps, i encountered this issue before and my settings for ttu reader had "cache data" turned on. after turning this off, i haven't encountered this issue until now. i am not sure if these are correlated somehow.