Use breakpoints (or console.logs) to check and make sure a certain piece of code is being run, or that a variable has a certain value.This should narrow down the possible sources of the error, and provide you with more information to search the internet for others who have had the same problem.For example, if you use a state management library like Redux, you can try removing that from the equation completely to see if the issue lies in your state management (which is really common in React apps)

With Safaris web inspector you can debug the webview and js code in your Cordova.

If the code you're adding in each 'piece' is complex, you may want to simplify what you're doing. For example, your app may work in the iOS simulator without a problem.

Apply your recent changes piece by piece, until it breaks.

Revert back to a working version of your code (this may even be a completely blank expo init project).

This step is vital in fixing obscure errors.

Isolate the code that's throwing the error.

Search for the error message in Google and Stack Overflow, it's likely you're not the first person to ever run into this.For errors that aren't as intuitive to solve, here's a good list of steps to take: there is no direct way to run the app on iOS emulator unless you use Mac pc or laptop. Apple provides an excellent developer experience for debugging on Mac OS X. Click on the Flutter Inspector from the right pane and click on. Sometimes you'll be able to tell exactly what's wrong just by the stacktrace, but other times the error message is a little more cryptic. Debug on either an iOS device directly or debug on an iOS simulator.

Ipad emulator for mac inspector