Home > Web Front-end > JS Tutorial > React Native related cross-domain resource error issues

React Native related cross-domain resource error issues

亚连
Release: 2018-06-11 15:39:08
Original
2019 people have browsed it

Below I will share with you a solution to the problem of cross-domain resource loading errors in React Native real machine breakpoint debugging. It has a good reference value and I hope it will be helpful to everyone.

Written in front

I had nothing to do and played around with React Native. Compared to before, the development experience is much better. However, I encountered a problem with cross-domain resource loading errors during real-machine breakpoint debugging. After some exploration, I finally solved it. Visual inspection revealed that it was a bug in the debugging service of the new version of RN.

There should be many students who have encountered similar problems. I will record them here and refer to them if necessary.

How to debug breakpoints

First, load and run the RN application on the real machine (the process is omitted).

Then, shake the phone, the development menu will pop up, and select "Debug JS Remotely".

Chrome will automatically open the debugging interface, the address is http://localhost:8081/debugger-ui/. Open the console, find the file you want to debug, add a breakpoint, and done.

Problem: Cross-origin resource loading error

Ideally, after the above steps, you can Happy breakpoint debugging. But the actual situation was not so smooth. After modifying the host according to the official guidelines, the problem still existed.

The error message seen on the console is as shown in the figure, and there is an error in loading cross-domain resources. 192.168.3.126 is the IP of the local intranet, and the domain name of the error resource is 192.168.3.126.xip.io.

Without having an in-depth understanding of RN, I came up with two ideas, the details of which will be described later.

Let the resources with loading errors have the same origin as the debugging page

Let the debugging service support cross-domain loading of resources

Solution one: Replace the host name

Replace localhost with 192.168.3.126.xip.io, that is, we pass http://192.168.3.126.xip.io:8081/debugger-ui / to access the debugging interface.

The debugging interface is accessed normally, resources are loaded normally, and done.

192.168.3.126.xip.io This host name looks a bit strange. The principle behind it will be further introduced later.

Solution 2: CORS

In the github issue "CORS issue with JS Remote Debugging when using xip.io", there are developers Reported the same error.

He solved it like this:

Find the node_modules/metro module, modify the Server/index.js and index.js.flow files, and add the following code to the _processDeltaRequest method.

mres.setHeader("Access-Control-Allow-Origin", "*");
Copy after login

This method is not recommended, but if you are in a hurry to debug it, you might as well try it.

What is 192.168.3.126.xip.io

Many students may be confused when they see this host name. How can a hostname that does not seem to exist be accessed successfully?

After pinging in the console, the IP returned is 192.168.3.126.

It’s actually very simple. xip.io is a special domain name. When you query the IP address corresponding to the domain name xxx.xip.io, it will directly return xxx.

Example: The intranet IP address of my laptop is 192.168.3.126. When I access 192.168.3.126.xip.io, the IP address returned by the DNS query is 192.168.3.126.

The principle is also very simple. The holder of xip.io has built a DNS resolution service on the public network. When the user initiates a DNS query for xxx.xip.io, it will directly return xxx.

Written at the back

The cross-domain solutions mentioned above are actually not satisfactory. If there is a better solution, Please tell me, thank you.

Reference link

http://xip.io/

CORS issue with JS Remote Debugging when using xip. io

Debugging on a device with Chrome Developer Tools

The above is what I compiled for everyone. I hope it will be helpful to everyone in the future.

Related articles:

ES6 iterator and for.of loop (detailed tutorial)

Use better-scroll scrolling in vue Plug-in

How to implement the single image cross-domain upload function in VUE UEditor

The watch in Vue cannot detect changes in object attributes Questions

veloticy-ui implements text animation effects

What are the differences between let and var defined variables in js?

VUE Personal summary (problems encountered)

Nuxt.js Vue server-side rendering

The above is the detailed content of React Native related cross-domain resource error issues. For more information, please follow other related articles on the PHP Chinese website!

source:php.cn
Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template