Issues with Safari dev tools + WKWebView + local URL + iOS 18 simulator

Question

Created Dec ’24

Replies 2

Boosts 0

Participants 1

When I'm inspecting a WKWebView in a simulator and the WKWebView loads a local URL with a port number, I've found that most features of Safari dev tools that worked in iOS 17 are broken in iOS 18. Here are the steps I'm taking:

Set up a WKWebView with isInspectable = true that loads a local URL, e.g. https://www.local.mydomain.com:3000
Install a self-signed SSL certificate on a simulator for www.local.mydomain.com
Run my app on the simulator
The WKWebView loads successfully
In Safari on my Mac, I can select the WKWebView and open dev tools to inspect it

If the simulator is on iOS 17, this works fine, no issues.

But if the simulator is on iOS 18, Safari dev tools are mostly broken. I can tell that there is a connection to the WKWebView because the Network tab logs the requests that I expect. But I cannot use any of the other dev tools features: Elements, Sources, Console, etc.

Has anyone else encountered this? Is there a workaround?

Boost

Answer 1

jkadis OP

Dec ’24

Also if the simulator is on iOS 18 and the WKWebView loads an external URL, it's fine. As far as I can tell, the issues are only with a local URL

0

Answer 2

jkadis OP

4d

Answering my own question. The issue:

Affects both WKWebView and Safari
Is not specific to iOS 18
Does not affect just local URLs; I can reproduce it during a port forwarding session to an external domain

How to reproduce with Nextjs which is the framework I'm using:

Install a self-signed certification for a domain like
Start a Nextjs dev server
Open any page in the Nextjs dev server in Safari on a Simulator
Open Safari Dev Tols

The Elements tab will be either empty or show only the very top level elements of the DOM. The Network and Sources tab will show a correct list of resources that have been loaded but won't show the responses as you'd normally see. Screenshot 2025-02-24 at 5.49.19 PM.png

0