[maxkatz6]

Fixes #90

Problem

Our managed delegate classes (WKScriptMessageHandler, WKNavigationDelegate, ASWebAuthenticationPresentationContextProviding) only got their protocol if objc_getProtocol found it. objc_getProtocol only returns protocols that some loaded image references. When it returned null, the class silently didn't conform, and per #90 WebKit crashes on iOS 26.

The workaround in the issue fits this: declaring a Xamarin class that implements IWKScriptMessageHandler/IWKNavigationDelegate makes the app binary register those protocols.

Fix

New NSObject.AddProtocol(classHandle, name, methods) helper:

• If the runtime knows the protocol, add it as before.
• Otherwise, register a protocol with the same name. It conforms to NSObject and has descriptions for the methods we implement, e.g. the required userContentController:didReceiveScriptMessage:. The runtime checks conformance by name, so WebKit accepts it.

Testing

• iOS 26.5 simulator, Debug and Release, without the fix: no crash, invokeCSharpAction message received. The protocol is found there, so the simulator doesn't reproduce WKWebView Binding for DidReceiveScriptMessage in iOS 26 needs updating #90.
• Fallback path, tested on the simulator by registering an unknown protocol name: the class conforms, protocol_getMethodDescription returns v@:@@, and messages still arrive.
• Not tested on a physical device, which is where WKWebView Binding for DidReceiveScriptMessage in iOS 26 needs updating #90 was reported. It still needs a check on iOS 26 hardware without the workaround class.

🤖 Generated with Claude Code