Closed danielesegato closed 1 year ago
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Was coming to ask if you had a chance to check this out, and I see you removed the stale label already! Thank you :-)
Yes sorry! I will implement this, I just haven't had a chance yet
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
I guess there's no plan to do this?
Description When loading a web page the
state.errorsForCurrentRequest
does not report HTTP errors with the page being loaded (ex. a 404 or a 403).Steps to reproduce
nothing will be print, no error despite the page having a 404
Expected behavior http errors of the main page should be reported somehow by the state
Additional context It is relatively easy to "fix" by extending
AccompanistWebViewClient
with your own state for the error which is provided by theonReceivedHttpError()
method.but I think it should be part of the errors exposed by default by the library.