DioException Error When Searching Books in OpenLib (F-Droid Version)

[DaveTmire85]

When attempting to search for books in the OpenLib app (installed via F-Droid), I encountered an error message stating:
"DioException [connection error]: The connection ground to a halt while trying to fetch data..."

The issue persists regardless of whether I am connected to a VPN or not. I have tried uninstalling and reinstalling the app, but the problem remains.

Steps to Reproduce:
Open the OpenLib app on Android.

Navigate to the search bar and enter any book title.

Press "Search."

Observe the error message.

Expected Behavior:
The app should display search results for the entered book title.

Actual Behavior:
The app displays an error message with a stack trace and does not load any results.

Screenshot attached.

Device Information:
Device: Samsung Galaxy A51 U1

Android Version: Latest firmware as of March 9, 2025

App Version: Latest version from F-Droid

Additional Context:
I was initially running Speedtest VPN when I encountered this issue. However, disabling the VPN and retrying did not resolve the problem.

I uninstalled and reinstalled the app via F-Droid, but the issue persists.

The stack trace in the error message indicates that the problem might be related to DioMixin.fetch or AnnasArchive.searchBooks.

[Zetsu4i]

errno 7 is connection error the app cant reach annas archeive url
thats possibly bcuz the website is blocked in your country

[DaveTmire85]

I can directly access annas-archive from my browser without VPN, and have successfully downloaded books that way.

Interestingly, I uninstalled the version I got off F-Droid's standard repo and got the Izzy version, which has been updated more recently, and it worked just fine. Perhaps the other repo needs an updated version?

[Zetsu4i]

I can directly access annas-archive from my browser without VPN, and have successfully downloaded books that way.

Interestingly, I uninstalled the version I got off F-Droid's standard repo and got the Izzy version, which has been updated more recently, and it worked just fine. Perhaps the other repo needs an updated version?

Okay then since its working nothing to worry about anymore
They probably just didn't update the f-droid release