First, the problem background:
Jump to H5 in the app page, the initial page for the user of various information and the like, in addition to the front end of the link parameters to the acquisition request interface, then the data cache and the like, may be written to acquire app data window, and then other operations. The adoption of the latter, so under normal circumstances, to enter directly from within the app H5 page and refresh the page can get to the window of data, but at the time of transfer of third-party payment H5, H5 third-party payment page from returning to their project when the H5 page, but did not get a window of data, and upon inspection found H5 page jump back from a third party, fail to get their own page in the window of data initialization, then they can take to refresh, window there is value, Thus suspected H5 page after leaving their projects, the pin is a data window, from a third party after the back, app overwrite value of the window, but the front-end code before it is executed to get any value. Finally, to the front-end code plus the value of the timer to delay the execution to solve the problem. Very often we find background data such as normal but the front is not normal, the more consideration asynchronous problems.