[Interesting bug] initialization in scenarios with no connection header on the client connected to the network is too slow, but the client is not connected to the network, causing an exception and crash

It is too slow to initialize a client connected to the Internet.

When you open some apps without connecting to the Internet, they will initialize them to the home page quickly.

However, when I have already connected to the Internet, some apps will be initialized for a long time !!!!

Example 1:

When you have already connected to the Internet, open the Netease youdao dictionary.

At this time, the client jumps from the "Netease youdao dictionary cover page" to the "search word page". At this time, it is invalid to try to search the input box through the touch screen, because the page is waiting for the server to respond, the wait time is too long. The wait time is 5-10 seconds, and the wait time is 20 seconds.

I wonder if the designer has considered the application scenarios of software such as "English Dictionary? When I need to look up a word, you asked me to wait for you to put all the styles, especially the advertisements !! After the advertisement is loaded, can the dictionary be searched? The teacher has already mentioned the nth word.

 

An exception occurred when the client was not connected to the network.

Another problem is that when some apps are not connected to the internet, they will be blocked by the process and cannot perform subsequent operations.

Example 2:

Internet not connectedOpen an app

At this time, the client jumps from the app cover page to the home page. A window is displayed."An error occurred while initializing the application (network connection unavailable )"There are two buttons in the window: "cancel" and "retry ".

When you click the "retry" button, it is meaningless because the client is always not connected to the Internet and has no intention of connecting to the Internet.

However, when you click "cancel", the app is automatically disabled.

That is to say, this app is a fart when it is not connected to the Internet.

 

[Interesting bug] initialization in scenarios with no connection header on the client connected to the network is too slow, but the client is not connected to the network, causing an exception and crash