Problem scenario is like that, I developed a new activity page, had to work overtime, testing, alignment, online, on-line process and so on, finally come to an end, but in a good weekend all of a sudden we test little sister sent WeChat messages told me that in iphone6 and android hang on the page of this important online accident, Must be the first time to conduct troubleshooting and repair problems. Then I hooked up with an agent at home and started sorting out problems (another productive day!). .
Troubleshooting process:
First I looked at it on my phone and it was great, the page was perfect…
Then I went to my colleague’s Android, and it was great, the page was perfect…
The version was matched again, and the initial investigation should be caused by compatibility problems.
Here, I use the method of troubleshooting. For local debugging, Charles is mainly used to connect with the local agent for debugging and troubleshooting. Charles only shows loading HTML and JS, and then…
Some syntax in the code is not supported in the earlier version, js error causes the page to hang directly. Charles had very little to offer at such times, so he had to find another way.
At this point I wish I could see the error message displayed on the console of my phone, look around the Internet, and see that VConsole does what I want, but (there it is again!) Vconsole requires the page to render normally before you can see the error message. I understand that this is not very different from Charles, but relatively intuitive, and you can see the DOM node.
Later, under the reminder of my tutor, I learned that some debugging tools of Chrome can be used for debugging. //inspect/# Devices ://inspect/# Devices, just open the developer mode of the phone, connect it to the computer via USB, then open webView and you can see the page opened on your phone as shown in the picture.
Unexpected token…
This tells us that the error was caused by the use of the extension operator in my project, and the extension operator was not compiled so that it could not be recognized on some systems.
At this point, the troubleshooting process is over, and the next step is the process of problem analysis.
See several other blogs for the problem analysis process.
Juejin. Cn/post / 684490…