Update: we managed to fix the issue on our end by moving the 'Embed Frameworks' build phase above the 'Run script' build phase(s).
We're seeing the same error, but we don't change DSTROOT. We have 2 frameworks in our workspace, where framework a links to and depends on framework b (Always Used / Do Not Embed) and the host app depends and embeds and signs both framework a and b (Always Used / Embed & Sign). This works fine in Xcode 14.3.1 but causes the Cycle inside ...; building could produce unreliable results error in Xcode 15.0 beta 1.
Post not yet marked as solved
Yeah, I only experience the issue when running in iOS 16.1 Simulator. On device it seems to work as expected.
Here as well, I see this filling up my Xcode console while running on device (iPhone X / iOS 13.2 / Xcode 11.2.1) for any WKWebView. It does not happen in the simulator, so it must be specific to iOS on device.When I check the device logs in the console app, I see the following line always preceding the 'kill' line:default0x1201ef200 (PageID=22) -[WKWebView _updateVisibleContentRects:] - usesStandardContentView is NO, bailingerrorkill() returned unexpected error 1defaultInvalidating assertion 27-912-10256 (target:xpcservice<com.apple.PDFKit.PDFExtensionView>) from originator 912errorkill() returned unexpected error 1This particular WKWebView was rendering a PDF. For other WKWebView's I always see the 'usesStandardContentView is NO, bailing' preceding the 'kill()' log entry.Not sure if that is a coincidence, or the cause of the issue. In any case, these errors got added to WKWebView.mm over the last year.
