To find the WebKit you built, Xcode needs to know the build products location that build-webkit used. Set the project’s build products location.To interchange between building WebKit from the command line and Xcode you must ensure both use the same build directory. Note: The Xcode project file depends on the build location specified in the project itself. Note that if you have specified a custom build location in Xcode preferences, then you don’t need to do this. Ensure that the Products, Intermediates, and Index Datastore locations for the workspace match those used by build-webkit by choosing File > Workspace Settings and clicking the Advanced button, selecting Custom, Relative to Workspace, and entering WebKitBuild for Products, Intermediates and Index Datastore. To debug from within Xcode, you can use the WebKit workspace. At the debugger prompt, enter run to start the process. It will start the debugger with Safari or MiniBrowser as the target, respectively. Run script debug-safari or debug-minibrowser.

To enable it, run the following in Terminal: defaults write IncludeInternalDebugMenu 1 There is a Debug menu that can be enabled in Safari, and it exposes many useful options to help with debugging. Substitute .Development for the value of -attach-name to debug the WebProcess. xcrun -sdk iphonesimulator lldb -attach-name MobileSafari -wait-for Use the -wait-for option to wait for MobileSafari to be launched and attach to it as early as possible. In Terminal, run the following command to attach to the currently running MobileSafari: xcrun -sdk iphonesimulator lldb -attach-name MobileSafari Turn all logging and activity tracing on process launch (may be overridden by tools) You can change the verbosity of this logging by setting the environment variable OS_ACTIVITY_MODE to one of the following values: Valueĭisables all logging and activity tracing (cannot be overridden) WebKit emits a lot of logging by default. You will need to attach to the appropriate process(es) to debug an issue.

The code base is organized around these process boundaries.

Safari) and the following auxiliary processes: Colloquial name Unlike the legacy API that executes within a single-process the modern WebKit API functionality is segregated between the UIProcess (e.g. The WebKit system framework exports two public APIs on both Mac and iOS: a modern, multi-process API (WKWebView) and a legacy single-process API (WebView on Mac and UIWebView on iOS).

Apple safari simulator