BUG: Possible BookOrbit progress sync issue

[RobinD42]

I still need to verify this but I've seen at least one case where I read for a while in Codexa (the android app) and then read the same book for a while in BookOrbit's reader (v2.9.0). Later when I opened the book in the Codexa app again it opened at the same position where Codexa was last located at, not where I left off in BookOrbit.

[thehijacker]

Well you are onto something. But I found this out few days ago myself. On my instance I had KOSync enabled with BookOrbit and also BookOrbit integration mainly because of the much faster and detailed library view, but also due to pushing proper progress to BookOrbit. I am also reading on Xteink X4 Pro this days where I use special Crossink-BookOrbit firmware that lacks KOSync to pull/push progress but fully enables BookOrbit integration like Codexa has. I noticed a drift between progress that I push on Xteink X4 and Codexa.

I removed KOSync from my account and what do you know, I do no handle pull from BookOrbit at all. I was only focused on progress push. I do have a fix for this ready, but I haven't pushed the changes just yet as I am still testing this but lacking the time.

I have pushed the changes now so if you are using Docker reployment of Codexa I kindly ask you to change tag from :latest to :dev and give the new version a try. It is just now building. Should be up in few minutes.

Is there a reson why you use BookOrbits reader instead of Codexa in your browser? I always had issues with Foliate library.

[RobinD42]

Thanks! I'll give it a try this evening.

Is there a reson why you use BookOrbits reader instead of Codexa in your browser? I always had issues with Foliate library.

No real reason. I was playing with the color and layout options there and then just kept on reading for a couple more chapters.

[thehijacker]

Thanks for testing. I could use some feedback and extra pair of hands testing this and that. Currently only my wife and kids are the biggest testers as we are all heavy readers.

[RobinD42]

The issue no longer happens after updating my container. This can be closed.

Thanks for testing. I could use some feedback and extra pair of hands testing this and that.

I'm happy to help, and I'm an avid reader too. I've just recently gotten started with BookOrbit so I'm very interested in getting a capable reader on the new stack.

[thehijacker]

Thanks for the test. I will leave it open until I release a new version. I still wish to do more tests myself especialy with Xteink X4 also pushing and pulling progress.

[thehijacker]

Included in v2.6.2