iPad（iOS 17）FBSScene崩溃求助：-[FBSScene _updateClientSettings:withTransitionContext:]

以下是iPad运行iOS 17系统时，主线程在FBSScene相关方法处崩溃的堆栈信息，具体崩溃点为-[FBSScene _updateClientSettings:withTransitionContext:]（FBSScene的私有方法「更新客户端设置:伴随过渡上下文:」）：

Crashed: com.apple.main-thread
0  FrontBoardServices             0x38b8 -[FBSScene _updateClientSettings:withTransitionContext:] + 1092
1  FrontBoardServices             0x340c -[FBSScene updateClientSettingsWithTransitionBlock:] + 116
2  FrontBoardServices             0x336c -[FBSScene updateClientSettingsWithBlock:] + 124
3  UIKitCore                      0xac510 -[FBSScene(UIApp) updateUIClientSettingsWithBlock:] + 168
4  UIKitCore                      0xac340 __39-[UIWindow _noteOverlayInsetsDidChange]_block_invoke + 248
5  UIKitCore                      0xab004 -[_UIAfterCACommitBlock run] + 72
6  UIKitCore                      0xaade8 -[_UIAfterCACommitQueue flush] + 164
7  libdispatch.dylib              0x26a8 _dispatch_call_block_and_release + 32
8  libdispatch.dylib              0x4300 _dispatch_client_callout + 20
9  libdispatch.dylib              0x12998 _dispatch_main_queue_drain + 984
10 libdispatch.dylib              0x125b0 _dispatch_main_queue_callback_4CF + 44
11 CoreFoundation                 0x3720c __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16
12 CoreFoundation                 0x33f18 __CFRunLoopRun + 1996
13 CoreFoundation                 0x33668 CFRunLoopRunSpecific + 608
14 GraphicsServices               0x35ec GSEventRunModal + 164
15 UIKitCore                      0x22c2b4 -[UIApplication _run] + 888
16 UIKitCore                      0x22b8f0 UIApplicationMain + 340
17 XXX                           0x1890428 main + 25 (main.m:25)

崩溃逻辑链与排查方向 #

• 崩溃触发逻辑：系统检测到窗口覆盖内边距变化后，在CA事务提交后的回调队列中，尝试更新FBSScene的客户端设置时出错，属于UIKit与FrontBoardServices底层交互的问题。
• 常见触发场景：
  • 自定义窗口管理（如多窗口、悬浮窗、自定义Overlay）导致内边距频繁或异常变更
  • iOS 17新特性（如Stage Manager、新窗口布局API）适配不到位，导致Scene状态不一致
  • 第三方库或自定义代码在_UIAfterCACommitBlock队列中执行了干扰Scene状态的操作
• 具体排查步骤：
  • 检查项目中修改UIWindow的safeAreaInsets、overlayInsets的代码，重点看异步回调或CA事务提交后的执行逻辑
  • 验证iOS 17下多窗口/分屏场景的适配情况，确认是否存在Scene状态冲突
  • 排查第三方UI框架（尤其是窗口管理、悬浮窗类）是否适配iOS 17
  • 在模拟器中复现问题，通过断点跟踪-[UIWindow _noteOverlayInsetsDidChange]的调用时机，定位触发前的操作

内容的提问来源于stack exchange，提问作者XianqiangWang