iOS应用审核被拒求助：EXC_CRASH(SIGABRT)崩溃日志分析

我的应用在App Store审核环节被拒，但使用实体设备测试时无异常，无法定位问题。现将Crash Log附上：

Crash Log:
Last Exception Backtrace:
0 CoreFoundation 0x1c6349e48 __exceptionPreprocess + 164
1 libobjc.A.dylib 0x1bf6938d8 objc_exception_throw + 60
2 UIKitCore 0x1c8924838 -[UIStoryboard initWithBundle:storyboardFileName:identifierToN
3 UIKitCore 0x1c8924394 -[UISceneConfiguration initWithName:sessionRole:] + 1572
4 UIKitCore 0x1c898167c +[UISceneConfiguration configurationWithName:sessionRole:] + 64
5 UIKitCore 0x1c898f5c8 -[UISceneSession _initWithPersistentIdentifier:sessionRole:configurationName:] + 168
6 UIKitCore 0x1c8723230 -[UIApplication _connectUISceneFromFBSScene:transitionContext:] + 408
7 UIKitCore 0x1c8722ee8 -[UIApplication workspace:didCreateScene:withTransitionContext:completion:] + 372
8 UIKitCore 0x1c8722d08 -[UIApplicationSceneClientAgent scene:didInitializeWithEvent:completion:] + 288
9 FrontBoardServices 0x1dc064e90 -[FBSScene _callOutQueue_agent_didCreateWithTransitionContext:completion:] + 344
10 FrontBoardServices 0x1dc0a48f8 __92-[FBSWorkspaceScenesClient createSceneWithIdentity:parameters:transitionContext:completion:]_block_invoke.78 + 120
11 FrontBoardServices 0x1dc068c24 -[FBSWorkspace _calloutQueue_executeCalloutFromSource:withBlock:] + 168
12 FrontBoardServices 0x1dc0a4530 __92-[FBSWorkspaceScenesClient createSceneWithIdentity:parameters:transitionContext:completion:]_block_invoke + 360
13 libdispatch.dylib 0x1cd958fdc _dispatch_client_callout + 20
14 libdispatch.dylib 0x1cd95ca5c _dispatch_block_invoke_direct + 264
15 FrontBoardServices 0x1dc072d40 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 52
16 FrontBoardServices 0x1dc0728dc -[FBSSerialQueue targetQueue_performNextIfPossible] + 220
17 FrontBoardServices 0x1dc075184 -[FBSSerialQueue performNextFromRunLoopSource] + 28
18 CoreFoundation 0x1c6415f34 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
19 CoreFoundation 0x1c642230c __CFRunLoopDoSource0 + 176
20 CoreFoundation 0x1c63a6230 __CFRunLoopDoSources0 + 340
21 CoreFoundation 0x1c63bbb8c __CFRunLoopRun + 836
22 oreFoundation 0x1c63c0ec0 CFRunLoopRunSpecific + 612
23  GraphicsServices 0x1ffb6b368 GSEventRunModal + 164  
24  UIKitCore 0x1c88b686c -[UIApplication run] + 888
25  UIKitCore 0x1c88b64d0 UIApplicationMain + 340
26  libswiftUIKit.dylib 0x1ceeda308 UIApplicationMain(_::::) + 104
27  MyApp 0x102b7ee8c static UIApplicationDelegate.main() + 104
28  MyApp 0x102b82880 main + 28
30  dyld 0x1e4bd2960 start + 2528

我已排查初始化流程中可能出现Nil的场景，但未发现问题，恳请协助定位崩溃原因。

崩溃原因分析与排查方向 #

从崩溃栈可以看出，崩溃触发在UIStoryboard初始化阶段，后续关联到UISceneConfiguration的创建流程，核心问题是场景配置与Storyboard的关联出现异常，本地测试无异常但审核环境崩溃，大概率是打包或配置的环境差异导致：

• 检查Info.plist中的UISceneConfigurations配置：确认每个场景的UISceneStoryboardFile对应的文件名完全正确，注意大小写——审核环境的文件系统严格区分大小写，而本地设备可能不区分，容易因文件名大小写不匹配触发崩溃。
• 验证Storyboard的打包包含情况：检查Xcode的Build Phases -> Copy Bundle Resources列表，确保对应的Storyboard文件已被添加，避免本地存在但打包时遗漏。
• 核对场景配置名称一致性：确认代码中调用的场景配置名称与Info.plist中UISceneConfigurationName完全一致，包括空格、特殊字符和大小写。
• 模拟审核打包流程测试：使用Xcode的Product -> Archive导出Ad Hoc包，在实体设备安装测试，复现审核环境的打包逻辑，看是否能触发相同崩溃。
• 检查Storyboard依赖资源：确认Storyboard中引用的图片、XIB或其他资源均已正确包含在包中，审核环境可能因资源缺失导致Storyboard初始化失败。

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