When using the Chrome debugger iOS 8.1, the tricky part is. It works as expected. When it is not running with the Chrome debugger, the app crashes as long as you navigate to a new view. I have a custom swipe View, so I can swipe to another view, and I can see that everything loads correctly before “Stable” and crashes. If I just try to click on a new page, it will crash almost immediately.
I My guess (educated from this stackoverflow question) is that it is a matter of time, as long as my assumption is that iOS 8.1 runs faster than iOS 9.2 is correct. I guess the debugger will slow down the app to the extent that The timing issue itself does not exist. Having said that, I tried the “slow animation” mode in the emulator and it still crashes when not using the debugger.
Considering this, I realize It is most likely a configuration issue. I am running XCode 7.2, and I am using react-native 0.21.0-rc.
The error that appears when I try to click anywhere/change the view is:
null is not an object (evaluate’inst.componentWillReceiveProps’)
In our case, it turns out that we made an error in the code snippet , The error will only occur when the browser obtains support for the js function
Date().toLocaleTimeString
Mozilla said that you can execute the following Operate to check the browser’s support for this feature:
function toLocaleTimeStringSupportsLocales() {
try {
ne w Date().toLocaleTimeString('i');
} catch (e) {
return e.name ==='RangeError';
}
return false;
}
I haven’t updated to the latest Xcode, but it crashed on an iPhone running iOS 10. Once I upgraded Xcode to the latest version, the error also started to appear in the simulator, Because Safari may have gained support for toLocaleTimeString. SIM is too. The report run debugging error is more specific and pointed out my fix.
I suspect this is the same problem, but this is what I have in my application The way to fix this error in the program, and how it only appears in the version instead of sim-strictly because different versions of Safari lead to different execution paths. Hope this can help others to solve this problem.
I have a react-native app that runs on iOS. On iOS 9.2, the app runs perfectly, whether it is using the Chrome debugger or not when it is used. However, on iOS 8.1 , The application will load, and you can refresh the list, load data from the server, etc. This has been tested in both operating systems and can run on the simulator and physical devices.
When When using the Chrome debugger iOS 8.1, the tricky part is that it works as expected. When it is not running with the Chrome debugger, the app crashes as soon as you navigate to a new view. I have a custom sliding view, so I You can swipe to another view, and I can see that everything is loaded correctly before “Stable” and crash. If I just try to click on a new page, it will crash almost immediately.
My guess (from This stackoverflow question started education) Yes, this is a timing issue, as long as my assumption is that iOS 8.1 runs faster than iOS 9.2 is correct. I guess the debugger will slow down the application so that the timing issue itself is not Doesn’t exist. That being said, I tried the “slow animation” mode in the simulator and it still crashes when not using the debugger.
With this in mind, I realize that it is most likely A configuration issue. I’m running XCode 7.2, and I’m using react-native 0.21.0-rc.
The error that appears when I try to click anywhere/change the view is:
null is not an object (evaluate’inst.componentWillR eceiveProps’)
I encountered the same problem when publishing our app – it will not appear in the emulator, only when it is published.
In our example, it turns out that we made an error in the code segment, and the error will only occur when the browser gets support for js functions
< /p>
Date().toLocaleTimeString
Mozilla stated that you can check browser support for this feature by doing the following:
function toLocaleTimeStringSupportsLocales() {
try {
new Date().toLocaleTimeString('i');
} catch (e) {
return e.name === 'RangeError';
}
return false;
}
I haven’t updated to the latest Xcode, but it crashes on an iPhone running iOS 10. Once I After upgrading Xcode to the latest version, the error also began to appear in the simulator, because Safari may have gained support for toLocaleTimeString. SIM is also. Reporting the debugging error is more specific and pointing out my fix.
I suspect this is the same issue, but this is how I fixed this error in my app and how it only appears in the version and not sim-strictly because different versions of Safari lead to different execution paths. Hope this Can help others solve this problem.