Bug 186719

Summary:	WebKit build fails at code signing
Product:	WebKit	Reporter:	Simon Fraser (smfr) <simon.fraser>
Component:	WebKit Misc.	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED WORKSFORME
Severity:	Normal	CC:	bfulgham, mitz, simon.fraser
Priority:	P2
Version:	WebKit Nightly Build
Hardware:	Unspecified
OS:	Unspecified

Description Simon Fraser (smfr) 2018-06-15 22:49:31 PDT

My WebKit build at home (no Internal tree) fails at:

=== BUILD TARGET WebKit OF PROJECT WebKit WITH CONFIGURATION Debug ===
Check dependencies
PhaseScriptExecution Make Frameworks Symbolic Link
PhaseScriptExecution Migrate WebKitLegacy Headers
PhaseScriptExecution Postprocess WKBase
PhaseScriptExecution Postprocess WKFoundation
PhaseScriptExecution Postprocess Framework Headers
PhaseScriptExecution Copy Additional Resources
PhaseScriptExecution Copy WebDriver Atoms to Framework Private Headers
PhaseScriptExecution Copy iOS Sandbox Profiles for Manual Sandboxing
PhaseScriptExecution Check For Weak VTables and Externals
PhaseScriptExecution Check For Inappropriate Objective-C Class Names
PhaseScriptExecution Check For Framework Include Consistency
PhaseScriptExecution Check For Inappropriate Files In Framework
PhaseScriptExecution Check For Inappropriate Macros in External Headers
CodeSign A
Signing Identity:     "-"
/Volumes/Data/Development/apple/webkit/OpenSource/WebKitBuild/Debug/WebKit.framework/Versions/A: code object is not signed at all
In subcomponent: /Volumes/Data/Development/apple/webkit/OpenSource/WebKitBuild/Debug/WebKit.framework/Versions/A/XPCServices/com.apple.WebKit.Plugin.xpc
Command /usr/bin/codesign failed with exit code 1
** BUILD FAILED **

This seems related to r185298 or r232492.

Comment 1 mitz 2018-06-15 23:14:11 PDT

Seems like there’s a stale version of the plug-in service in your built products directory. Removing the service bundle from within the built framework (the path that appears in the error message) as well as from the top level of WebKitBuild/Debug if it’s present there ought to resolve the issue.

Comment 2 Simon Fraser (smfr) 2018-06-16 08:24:55 PDT

Indeed it did!