On my "Amazon Kindle running FIRE OS 5.7.0.0" the new version of your software "VERSION 4.5.2 (2023-02-05)" fails to open my ePUB books.
It opens up and when I click on a book, it give me a error message: "Your version of webview is obsolete and is no longer supported. Uodate webview to the latest version".
Could you please fix this issue ?
I don't have a Kindle Fire to test on, but I see that Fire OS 5.x is based on Android 5.1. I don't see this error on an emulator running Android 5.1.
This error happens when the WebView component fails to load (i.e it throws an error when the reader tries to start up). Can you let me know what version of WebView is loaded? On a vanilla Android device you would be able to see that through Settings/Apps/Android System WebView. I assume the same should be available on your Kindle Fire.
If I know what WebView version your device is using, I can try and see if I can load the same on my device and see if the same issue happens.
Here is what I see:
Amazon System WebView
version 100.amazon-webview-v100-4896-tablet.4896.127.37
Hello,
I would like to say I am having the same problem. However I cannot tell you which version of WebView I have as I can't get the Kindle Fire tablet to even admit it's using it. I am using the same Fire OS Version as OGM and recieving the exact same error message.
Did the problem just start happening with the latest update? I.e. was the previous version working properly? The latest version had updates to some Android libraries so it's possible that introduced an incompatibility with the WebView being used on that version of FireOS. Specifically, the webkit library was updated so that sounds like a likely suspect to have introduced incompatibilities.
Since this seems to be an Amazon specific version of WebView, I'm not sure I'll be able to get that installed on any of my devices. I'm adding some logging for this situation, so I'll put out an update soon which will capture a log file with more information when the failure happens. It might take me a few days to put that update out, but if you're willing to side load, I can give you the update a little sooner.
I'll also do some more investigation to see if the latest webkit library I'm using might have issues with the Amazon WebView component.
Yes, Everything worked fine yesterday, this morning nothing worked.
same here. It was working 2 days ago and started failing now.
I am not too technical to do this "side load" upload, so sorry.
Thanks for the replies. My best guess is that the webkit update caused this regression. I'm preparing another update (4.5.3) for both Basic and Full versions that revert back to the previous version of webkit. I'm also including logic to capture exception details in a log file if the issue continues. Once you get the update, if the problem persists (I'm hoping it won't), please send me a copy of the log file. When I post the update I'll add another comment here with more details about where to find the log file, should it be necessary.
I'm hoping to release tonight (it's 7:30AM local time for me now) after I'm done work (my day job). Updates show up quickest on Google Play, so if I get the update out tonight, you should be able to see it on Google Play soon after. I don't think 4.5.2 has gone live yet on the Amazon App Store as that version is still sitting in an "Approved" status rather than "Live". So hopefully this upcoming update will get out there in the Amazon ecosystem before 4.5.2 even goes live.
I'm assuming both of you received the update through Google Play, but if not, let me know so I know I don't miss anything.
Once I get things back up and running (hopefully soon), I'll see if I can find a FireOS 5.7 device to try and debug this better.
There was an update overnight, unfortunately the problem still persists, and the same error message happens whenever you try to open a book.
I use the Amazon AppStore on my Kindle, I don't have Google Play installed and I am using the eLibrary Manager Basic" to read.
Some of the app details on the Kindle AppStore shows:
eLibrary Manager Basic
Version 4.5.2
ASIN: BOOBS2SY1Q
Latest Developer Update: February 14, 2023
Original Releasae Date: March 13, 2013
File Size: 6.0 MB
Let me know if you need anything else. Thanks.
I have my update prepared to release to the Amazon App Store which should fix the issue (I believe - but I won't know for sure until I get it out there). Unfortunately, both the Full and Basic apps seem to be stuck in an "Approved" status in the App Store (they should be "Live") and therefore I am unable to release the fix until the status changes. I've opened a problem ticket with Amazon so hopefully they will respond soon with a resolution.
I'll release the new version (hopefully with the issue fixed) as soon as I can get my previous submission status cleared up.
Sorry for the delay. It seems everything likes to go wrong at the same time.
I'll keep you posted.
And we thank you for your hard work and diligence.
Sorry it's taking so long to post the update.
Amazon still hasn't cleared up whatever issue they are having on their end in the App Store with my previous submission (it's still in an "Approved" status and blocking updates). The messaging on the developer console has changed over the last couple of days though, so I hope that's a sign that someone is doing something. I'm keeping my fingers crossed.
Anyway, as soon as I can I will post that update.
Unfortunately, Amazon is being ominously quiet on the tickets I've opened to clear up my
eLibrary Manager and
eLibrary Manager Basic Amazon App Store status so I can release my update. Again, I'll do that as soon as I can.
In the mean time, I've released version 4.5.4 on all other app stores (including Google Play). So if anyone is having issues with the last update on your Fire tablet and you have access to Google Play, you can get the update through that channel.
If you are using
eLibrary Manager Basic and you are comfortable with sideloading, you can also get the .APK file at
- https://kpwsite.com/home/content/eLibrary/download.html
You can find a link for 4.5.4 towards the bottom of the page.
Hopefully Amazon will enable release of the update soon and I'll get it out on the Amazon App store as well. I will post here when that happens.
Just installed the version 4.5.4 on my Kindle and it works just fine now.
Thank you for the quick turnaround.
Thanks for letting me know!
I've got a Fire (with FireOS 5.7.0.0) on order from eBay that should be coming soon. With that I hope to be able to figure out what happened with the previous version and hopefully find a workaround for it.
I'm happy the update fixed the problem in any case.
An update on this issue:
I've gotten my hands on a Fire (5th gen) with FireOS 5.7.0.0 and have been able to figure out what the issue is with version 4.5.2 of my app. Version 4.5.4 does in fact fix the issue (as confirmed above).
The issue should only happen if you have a Fire device on FireOS 5.x with a recent version of WebView (i.e. 100). If your Fire has FireOS 5.x with older WebView (i.e. version 59), or if your FireOS version is anything other than 5.x (either older or newer), then you should not have a problem with version 4.5.2. If you are experiencing the issue though, you will need version 4.5.4 of my app (or any version other than 4.5.2 - the issue is specific to that one).
Unfortunately, Amazon is still dragging its feet clearing up my Amazon App Store submission status for both Full and Basic versions of my app, so as of this morning, I am still unable to post the fix to that app store. I will let you know when I finally release 4.5.4 with the fix.
If you have access to other app stores like Google Play, or if you are OK with side-loading, I've posted details about those options above.
Sorry for how long this is dragging out, but I'm not sure what else I can do other than communicate with Amazon through public forums to try and get some focus on the issue - which I have been doing but with as of yet limited success.
Version 4.5.4 is now live on the Amazon App Store.
For anyone who has been out of commission over the last couple of weeks, I apologize. You should be able to update to get the fix now.
Karl