This was working on previous macOS Big Sur Beta 5, but as of Beta 6, with this minimal code, my macOS app crashes instantly when started.
Code: ModelView.swift
import SwiftUI
import SceneKit
struct ModelView: View {
var body: some View {
return SceneView(scene: SCNScene())
}
}
Crash details:
language
code-blockdyld`__abort_with_payload:
		0x11ae8f6f4 <+0>:	movl	 $0x2000209, %eax					; imm = 0x2000209
		0x11ae8f6f9 <+5>:	movq	 %rcx, %r10
		0x11ae8f6fc <+8>:	syscall >	0x11ae8f6fe <+10>: jae		0x11ae8f708							 ; <+20>
		0x11ae8f700 <+12>: movq	 %rax, %rdi
		0x11ae8f703 <+15>: jmp		0x11ae8d8e4							 ; cerror_nocancel
		0x11ae8f708 <+20>: retq	
		0x11ae8f709 <+21>: nop		
		0x11ae8f70a <+22>: nop		
		0x11ae8f70b <+23>: nop		
When I look at the report, it shows this:
dyld: Library not loaded: /System/Library/Frameworks/_SceneKit_SwiftUI.framework/Versions/A/_SceneKit_SwiftUI
Referenced from: /Users/myuser/Library/Developer/Xcode/DerivedData/test-sceneview-evrchiajpqhubmeajvyhnlrdpiju/Build/Products/Debug/test-sceneview.app/Contents/MacOS/test-sceneview
Reason: image not found
And indeed that lib is not there.
I'm curious if anyone else has seen this, or can confirm that I am not crazy? (well, not about this anyway).
I submitted feedback (FB8668898).
Eric
Post
Replies
Boosts
Views
Activity
On macOS 13.2, with Xcode 14.2, I've set up a NavigationSplitView with 3 panes.
I have an OutlineGroup in the sidebar, and selecting parent nodes works fine (and the navigation works great), however selecting a child node just shows the selection for a split second and then returns to the previous selection (a parent node). I've tried nearly everything I can find on the internet, etc, and nothing seems to make it work. It's rather hard for me to post the code right now (I'd have to sanitize a lot of it), but wondered if anyone is aware or has a workaround for this?
Note:
I have this all wrapped in a List, and other items in the list are working just fine. Only the items in the OutlineGroup are acting funny.
This stack overflow link directly talks about the same issue, and their workaround does not work (and is.. not exactly right):
StackOverflow