苹果审核团队的 iOS 应用程序崩溃，但在我的设备上没有崩溃 [英] iOS app crashes for apple review team but not on my device

问题描述

我的应用程序在我的 iDevices 上没有崩溃，但 Apple 审核团队表示它在 ipad 6.0.1 上崩溃了.这是重新符号化日志的相关部分:

My App does not crash on my iDevices, but the apple review team says it is crashing on ipad 6.0.1. This is the relevant part of the resymbolicated log:

Last Exception Backtrace:
0   CoreFoundation                  0x327fb29e __exceptionPreprocess + 158
1   libobjc.A.dylib                 0x394dd97a objc_exception_throw + 26
2   UIKit                           0x38897d54 +[UIStoryboard storyboardWithName:bundle:] + 436
3   UIKit                           0x386da406 -[UIApplication _loadMainStoryboardFileNamed:bundle:] + 38
4   UIKit                           0x38563794 -[UIApplication _runWithURL:payload:launchOrientation:statusBarStyle:statusBarHidden:] + 524
5   UIKit                           0x3850bc34 -[UIApplication handleEvent:withNewEvent:] + 1000
6   UIKit                           0x3850b6c8 -[UIApplication sendEvent:] + 68
7   UIKit                           0x3850b116 _UIApplicationHandleEvent + 6150
8   GraphicsServices                0x35c8759e _PurpleEventCallback + 586
9   CoreFoundation                  0x327d067e __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 10
10  CoreFoundation                  0x327cfee4 __CFRunLoopDoSources0 + 208
11  CoreFoundation                  0x327cecb2 __CFRunLoopRun + 642
12  CoreFoundation                  0x32741eb8 0x32739000 + 36536
13  CoreFoundation                  0x32741d44 CFRunLoopRunInMode + 100
14  UIKit                           0x38562478 -[UIApplication _run] + 664
15  UIKit                           0x3855f2f4 UIApplicationMain + 1116
16  MyApp                           0x0007362e main (main.m:16)
17  MyApp                           0x000735e4 start + 36

这是否意味着故事板是问题所在(第 2 行)?

Does this mean that the Storyboard is the problem (line 2)?

推荐答案

回答您的问题:

这是否意味着故事板是问题所在(第 2 行)?

Does this mean that the Storyboard is the problem (line 2)?

这意味着最可能的问题与故事板加载有关 - 无论是故事板还是包 - 因为这是抛出异常的地方.在不知道 UIStoryboard 的源代码以及第 436 行是什么让它抛出异常的情况下，这可能与您从非 Apple 员工那里得到的一样具体.

It means that the most likely problem is related to the storyboard loading - either with the storyboard or the bundle - as that's where the exception is being thrown from. Without knowing the source code of UIStoryboard and what's on line 436 that makes it throw an exception, that's probably about as specific as you'll get from a non-Apple employee.

为了超越这一点并在本地实际重现崩溃(以便您可以努力修复它):

To get beyond that and actually reproduce the crash locally (so you can work toward fixing it):

• 验证包装/进行全新/全新安装(如评论中所建议)
• 尝试不同的设备(也许有一些残留物，清洁剂没有正确去除)
• 尝试使用较旧的 iOS 版本(也许他们不小心向您提供了不正确的 iOS 版本信息?)
• 尝试在您的应用处于后台时模拟低内存环境(在这种情况下，崩溃可能与您的应用在后台关闭和重新启动有关?)

• Validate packaging / do a clean/fresh install (as suggested in the comments)
• Try on a different device (perhaps there's something leftover that a clean isn't removing properly)
• Try an older iOS version (maybe they're accidentally giving you incorrect information to the iOS version?)
• Try simulating low memory environment while your app is in the background (maybe the crash is related to your app closing and restarting in the background in this situation?)

如果您无法重现问题，您更有可能希望从审核团队获得更多信息，而不仅仅是堆栈跟踪:

More likely you'll want to get more info from the review team than just a stack trace if you can't reproduce the issue:

• 关于它们是如何导致崩溃的，您能否获得更准确的重现步骤?
• 这是对现有应用的更新吗?他们可能有未正确清理的旧版应用吗?

这篇关于苹果审核团队的 iOS 应用程序崩溃，但在我的设备上没有崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！