Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to render pages when on bad internet connection #33

Closed
YorickPieters opened this issue Jul 2, 2018 · 8 comments
Closed

Unable to render pages when on bad internet connection #33

YorickPieters opened this issue Jul 2, 2018 · 8 comments
Labels
bug Something isn't working

Comments

@YorickPieters
Copy link

When browsing an eBook and my mobile data connection is not good anymore, the app does not render the html. We get an ERR_CONNECTION_TIMED_OUT error message.

screenshot_20180628-131943

@YorickPieters
Copy link
Author

Occurs on: Play Store version (seen on both beta 1 and beta 2)
App version: 1.0.1
Github tag: v1.0.0-beta.2

Steps to reproduce:

  • Place device in flight mode
  • Open R2 Reader
  • Click on a publication
  • You get an error "Webpage not available" with error code ERR_PROXY_CONNECTION_FAILED

or

  • Go to a place with bad mobile data connection
  • Open R2 Reader
  • Click on a publication
  • You get an error "Webpage not available" with error code ERR_CONNECTION_TIMED_OUT

@HadrienGardeur
Copy link

I can't reproduce this issue on my Pixel 2XL running Android 9.

@YorickPieters
Copy link
Author

I'll try and gather more info on when it occurs. It does not always seem to trigger, just now I was able to work in flightmode again. It seems to occur mostly on one of my 2 mobile data connections, I even got a DNS lookup failed error at some point.

@llemeurfr
Copy link

llemeurfr commented Jul 2, 2018

Yes, as this is not visible on my android tablet when I put it in flight mode. And the local server should not be impacted by bad mobile connectivity.

@YorickPieters
Copy link
Author

Additional information. The cause of this issue seems to be that one of my Mobile Data (base gprs) providers had a proxy active. If I disable the proxy server for that provider the app works fine.
It is weird that Android would allow a localhost call to be passed on to that proxy.
One of my colleagues found a similar report on this project: syncthing/syncthing-android#440

@llemeurfr
Copy link

Reading the syncthing thread, seems there is no solution that doesn't involve a modification of the device config by the user. If true, that would be a mess.

@HadrienGardeur
Copy link

We need to investigate ASAP if this is still an issue.

@mickael-menu
Copy link
Member

I'm closing because I can't reproduce and I don't think we got any more similar report since then. R2 has been used in production for a while now.

This other issue that we'll tackle soonish should render this moot anyway: https://github.com/readium/r2-testapp-kotlin/issues/297

@mickael-menu mickael-menu transferred this issue from readium/r2-testapp-kotlin Oct 22, 2021
@mickael-menu mickael-menu added the bug Something isn't working label Oct 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants