We ran into this issue as well. I filed feedback for this: FB22102831 Several users report they see our crash reporter window after they woke their Mac(Book) from sleep, the crash logs suggest the crash occurred while adding or removing a display, which might be the cause of nil being returned by the subsystem. Here are two main thread stack traces for crash reports: 0 libsystem_kernel.dylib 0x3024c8c34 mach_msg2_trap 1 libsystem_kernel.dylib 0x3024db024 mach_msg2_internal 2 libsystem_kernel.dylib 0x3024d1988 mach_msg_overwrite 3 libsystem_kernel.dylib 0x3024c8fb0 mach_msg 4 SkyLight 0x30f9896a8 _CGSGetRealtimeDisplayDataShmemPort 5 SkyLight 0x30f6b0820 WS::RealtimeDisplayDataMapping::shmem 6 SkyLight 0x30f6b06f0 WS::RealtimeDisplayDataMapping::data 7 SkyLight 0x30f6b0cc8 realtime_data_for_display 8 SkyLight 0x30f6b1fc4 SLSDisplayGetCurrentHeadroom 9 AppKit 0x30bde35f8 -[NSCGSDisplay initWithDisplayID:flipOffset:] 10 AppKit 0x30ae7dee4 ___NSCGSCreateDisplaysFromDisplayIDsUsingPredicate_block_invoke 11 AppKit 0x30b8e8694 _NSCGSCreateUniqueDisplaysWithFlipOffset 12 AppKit 0x30b8ea3cc _NSCGSDisplayConfigurationUpdate 13 AppKit 0x30b8e9734 _NSCGSDisplayConfigurationUpdateAndInvokeObservers 14 AppKit 0x30b8e9d70 _NSCGSDisplayConfigurationDidReconfigureNotificationHandler 15 SkyLight 0x30f5144e4 (anonymous namespace)::notify_datagram_handler 16 SkyLight 0x30f95d70c CGSDatagramReadStream::dispatchMainQueueDatagrams 17 SkyLight 0x30f95d5d0 CGSDatagramReadStream::mainQueueWakeup 18 CoreFoundation 0x30262d600 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ 19 CoreFoundation 0x30262d540 __CFRunLoopDoBlocks 20 CoreFoundation 0x30262c984 __CFRunLoopRun 21 CoreFoundation 0x3026e6e30 _CFRunLoopRunSpecificWithOptions 22 HIToolbox 0x31bba978c RunCurrentEventLoopInMode 23 HIToolbox 0x31bbacab4 ReceiveNextEventCommon 24 HIToolbox 0x31bd36b60 _BlockUntilNextEventMatchingListInMode 25 AppKit 0x30b397b58 _DPSBlockUntilNextEventMatchingListInMode 26 AppKit 0x30ae91e44 _DPSNextEvent 27 AppKit 0x30b95cd08 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] 28 AppKit 0x30b95ca14 -[NSApplication(NSEventRouting) nextEventMatchingMask:untilDate:inMode:dequeue:] 29 AppKit 0x30ae8a77c -[NSApplication run] 30 AppKit 0x30ae766d8 NSApplicationMain 31 dyld 0x301db6d50 start Thread 0 0 Foundation 0x31d995f20 _NSRequestConcreteObject 1 Foundation 0x31cc2cc2c -[NSNumber hash] 2 CoreFoundation 0x31a060574 -[__NSFrozenSetM containsObject:] 3 WindowManagement 0x4dc04b55c -[_WMWindow applyTags:mask:] 4 AppKit 0x321f1b530 -[NSWindow _setFrameCommon:display:fromServer:] 5 AppKit 0x322a0933c -[NSWindow(NSScreenLayout) _setFrame:fromAdjustmentToScreen:anchorIfNeeded:animate:] 6 AppKit 0x3221b4488 -[NSWindow _adjustWindowToScreen] 7 AppKit 0x3221d3ee4 -[NSWindow _displayChangedSoAdjustWindows:] 8 AppKit 0x322d5b874 ___NSApplicationPerformScreenInvalidationReactions_block_invoke 9 AppKit 0x321ed3804 -[NSApplication enumerateWindowsWithOptions:usingBlock:] 10 AppKit 0x322d5b174 ___NSApplicationReactToScreenInvalidation_block_invoke 11 AppKit 0x322d5a9b4 _NSApplicationReactToScreenInvalidation 12 AppKit 0x322d5ac00 -[NSApplication(ScreenHandling) _reactToDisplayChanges:] 13 AppKit 0x322808818 _NSCGSDisplayConfigurationUpdateAndInvokeObservers 14 AppKit 0x322808cfc _NSCGSDisplayConfigurationDidReconfigureNotificationHandler 15 SkyLight 0x325f7d02c (anonymous namespace)::notify_datagram_handler 16 SkyLight 0x32638ad98 CGSDatagramReadStream::dispatchMainQueueDatagrams 17 SkyLight 0x32638ac5c CGSDatagramReadStream::mainQueueWakeup 18 libdispatch.dylib 0x319b7fb28 _dispatch_call_block_and_release 19 libdispatch.dylib 0x319b99858 _dispatch_client_callout 20 libdispatch.dylib 0x319bb6b54 _dispatch_main_queue_drain.cold.5 21 libdispatch.dylib 0x319b8edac _dispatch_main_queue_drain 22 libdispatch.dylib 0x319b8ece8 _dispatch_main_queue_callback_4CF 23 CoreFoundation 0x31a088da0 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ 24 CoreFoundation 0x31a049a98 __CFRunLoopRun 25 CoreFoundation 0x31a048c54 CFRunLoopRunSpecific 26 HIToolbox 0x331529278 RunCurrentEventLoopInMode 27 HIToolbox 0x33152c4e4 ReceiveNextEventCommon 28 HIToolbox 0x3316b7480 _BlockUntilNextEventMatchingListInModeWithFilter 29 AppKit 0x321ed8ab0 _DPSNextEvent 30 AppKit 0x3228775ac -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] 31 AppKit 0x321ecbc60 -[NSApplication run] 32 AppKit 0x321ea2358 NSApplicationMain 33 dyld 0x3197aab94 start Unfortunately we have not been able to reproduce this on our side. But a fix would be appreciated!

I ran into this issue as well, filed a feedback as well and linked yours. When dignosing the issue to find a fix for this, I doug a bit in the UIKit code. Turns out, UITextView has a (private) method -(BOOL)startAutoscroll:(CGPoint)point which basically takes the input and calculates whether the view should scroll while selecting text. This method uses both contentInset and textContainerInset to inset the visible rect of the text view. To me this looks like a bug, as textContainerInset should not affect the viewport in a way that contentInset does.

With SwiftUI's List I found that using Label instead of an HStack and .tint instead of .foregroundColor works, at least on macOS 15. For other lists, like embedding a SwiftUI cell inside an NSTableView, this does not work. However, since macOS 14 there is the backgroundProminence environment value which does exactly what you ask for.

I was not able to activate Siri on my iPad on this screen. However, upon every restart, the iPad asked which WiFi to join. You can just hit continue without joining any WiFi. This will skip the activation step. If the device auto-joins a WiFi, you can tap the Lock-button, which makes a menu appear. From there you can choose WiFi settings. You can hit the info button on the WiFi the device joined and hit Forget this Network.

I see the same issue, no firebase in use. Filed as FB12236547. Adding -ld64 (using the old linker?) works fine for now.

I saw the exact same issue. The app has shortcuts configured and uses in-app intent handling. Using these intents with widgets works without issues on the home screen, but not on the Lock Screen. The configuration UI does not show up. The issue seems to be the in-app intent handling for me. Documentation states that an intent extension is required for widgets. As soon as I added one for handling the intent used by the widget, the configuration showed up. This also applies to Widgets for macOS. I don't know why in-app intent handling is allowed for Homescreen widgets but not for the lock screen & macOS.

Here are images from the sample project: Opening the modal sheet closes the find bar.

We were able to resolve this issue. Our problem was that for some provisioning profiles an older, still valid signing certificate was selected. This appeared to be no issue with Xcode 12, but is one with Xcode 13. Selecting the newest signing certificate for each provisioning profile fixed the issue.