[Webkit-unassigned] [Bug 271664] New: [iOS 17.4] Local WebKit builds don't use locally-built app extensions
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Mar 25 10:57:05 PDT 2024
https://bugs.webkit.org/show_bug.cgi?id=271664
Bug ID: 271664
Summary: [iOS 17.4] Local WebKit builds don't use locally-built
app extensions
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: WebKit Process Model
Assignee: webkit-unassigned at lists.webkit.org
Reporter: ajuma at chromium.org
CC: achristensen at apple.com, mjs at apple.com,
pvollan at apple.com, rohitrao at google.com,
sihui_liu at apple.com
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?
--
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/20240325/97f10e7c/attachment-0001.htm>
More information about the webkit-unassigned
mailing list