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
Offline webview(cache) support #1387
Comments
Any updates here? |
No, sounds like no one has done this yet? |
Hello 👋, this issue has been opened for more than 2 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically |
@RasAlGhul1, how did you solve the problem? |
It may be very useful |
I need offline support for WebView, still no answers?? |
Hello all, So, this problem is something that’s been plaguing us for more than a year now. The case for this to be reopened, and fixed, is this: When a person is using your app on Wifi, and they then switch to their phone’s internet (everyone’s phone does this several times a day), the applications built on this tech momentarily “error.” Our customers see this, and complain about it. Yes, when the connection is re-established, the app will reload. And, yes, we’ve implemented custom logic that will show a nicer error than the one that shows by default. BUT, why show the error at all if the page can simply continue to be shown, or be reloaded from the cache? |
Hey if you want to show your own custom error srceen try this:
if you did this remove your return and use this instead for reandering your content
notice you can use HTML In webview https://reactnative.dev/docs/0.63/webview you just check if you have a connection if yes then show your site and if you no connectio then your your custom html site . hope i could help somebody |
Is there anyway to show the cached version when there is no internet? At the moment it shows only an error that there is no internet.
The text was updated successfully, but these errors were encountered: