[Webkit-unassigned] [Bug 271664] [iOS 17.4] Local WebKit builds don't use locally-built app extensions

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Mar 26 09:08:54 PDT 2024


--- Comment #1 from Per Arne Vollan <pvollan at apple.com> ---
(In reply to Ali Juma from comment #0)
> When building WebKit for the iOS simulator after 276550 at main (so that
> USE_EXTENSIONKIT is true), local builds try to use app extensions from the
> simulator runtime rather than their locally-built counterparts.
> For example, rather than using
> WebKitBuild/Debug-iphonesimulator/WebContentExtension.appex, local builds
> instead try to use
> /Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/
> CoreSimulator/Profiles/Runtimes/iOS
> 17.4.simruntime/Contents/Resources/RuntimeRoot/System/Library/ExtensionKit/
> Extensions/WebContentExtension.appex
> In practice this means that local builds are very broken, since they are
> combining locally-built WebKit.framework with pre-built app extensions,
> resulting in mismatching IPC messages.
> Is there some additional configuration needed to get ExtensionKit builds
> working with the public SDK?

Thanks for reporting this issue!

The extension executables themselves are very small executables that just calls into the WebKit framework. What specific issues are you seeing? Since the IPC code is contained in the WebKit framework, I would not immediately expect there to be mismatches with regards to IPC messaging.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20240326/2b2685b4/attachment.htm>

More information about the webkit-unassigned mailing list