When building the development service, we disable all restricted entitlements so that the debugger can attach to it (see https://bugs.webkit.org/show_bug.cgi?id=187355). But this means it does not have the com.apple.runningboard.assertions.webkit entitlement, which we need to actually take RunningBoard assertions. We think this may be leading to the development service getting unexpectedly suspended or deprioritized.
<rdar://problem/116866896>
If it's also a restricted entitlement, then presumably we need to teach WebContent to work without it?
(In reply to Alexey Proskuryakov from comment #2) > If it's also a restricted entitlement, then presumably we need to teach > WebContent to work without it? It is controlled by the plist whether or not our processes are managed by running board or not. see Source/WebKit/Scripts/update-info-plist-for-runningboard.sh
Speculative fix incoming.
Pull request: https://github.com/WebKit/WebKit/pull/19005
Committed 269328@main (f8192d525e8b): <https://commits.webkit.org/269328@main> Reviewed commits have been landed. Closing PR #19005 and removing active labels.