React-native: webview error 'Encountered an error loading page @RN 0.34.1

Created on 16 Oct 2016  Â·  17Comments  Â·  Source: facebook/react-native

E/ReactNativeJS(27798):   'Encountered an error loading page', { canGoForward: false,
E/ReactNativeJS(27798):   code: -2,
E/ReactNativeJS(27798):   canGoBack: false,
E/ReactNativeJS(27798):   description: 'net::ERR_NAME_NOT_RESOLVED',
E/ReactNativeJS(27798):   loading: false,
E/ReactNativeJS(27798):   title: '',
E/ReactNativeJS(27798):   url: 'https://www.baidu.com/',
E/ReactNativeJS(27798):   target: 122 }

following my code:// component is custom.

                <WebView
                    scalesPageToFit={true}
                    renderLoading={()=><Loading value="XXX"/>}
                    renderError={()=><Loading value="XXX"/>}
                    onError={()=><Loading/>}
                    source={{uri: "https://www.XXX.com"}}
                    style={{padding: 10}}
                />

Who can help me?

Locked

Most helpful comment

Yes, this is still an issue. I'm seeing this on the latest react-native as of July 22, 2017.
Perhaps, wait for a solution to be posted before closing the issue.

All 17 comments

I meet this error when I close network.

Are you set up a proxy?

l have the same problem
Encountered an error loading page Object {domain: "WebKitErrorDomain", canGoBack: true, target: 10, code: 101, loading: true…}canGoBack: truecanGoForward: falsecode: 101description: "The URL can’t be shown"domain: "WebKitErrorDomain"loading: truetarget: 10title: "百度一下"url: "https://www.baidu.com/#0.26427529194080224;0.877470845104408%3Bthis.setHeight(1387)"__proto__: Object

+1

l have the same problem too +1

oh , i know , i have not add some link which have show in the webview to the App Transport Security Settings

+1 Same here, does any one have a proper solution for this issue.

I solve this issue by implementing onShouldStartLoadWithRequest . the error occur when the webView try to open a wrong url. we can intercept the request before it happen.

@LeonHwa do you have a sample on how you resolved this?

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

  • Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
  • If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
  • Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

Yes, this is still an issue. I'm seeing this on the latest react-native as of July 22, 2017.
Perhaps, wait for a solution to be posted before closing the issue.

+1

+1

+1

+1

+1

Please open a new issue and make sure to follow the template.

Was this page helpful?
0 / 5 - 0 ratings