iOS应用程式在苹果审核小组失败，但在我的设备上失败 [英] iOS app crashes for apple review team but not on my device

问题描述

我的应用程序不会崩溃我的iDevices，但苹果审查团队说，它是崩溃在ipad 6.0.1。这是resymbolicated日志的相关部分：

 最后异常回溯：
 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行）？

这意味着最可能的问题与故事板加载有关 - 无论是使用故事板还是捆绑包 - 这是异常被抛出的地方。不知道 UIStoryboard 的源代码，以及436行上的什么使它抛出异常，这可能是你从非苹果员工那里得到的。 / p>

为了超越这一点，实际上在本地重现崩溃（所以你可以努力修复它）：

• 验证包装/执行清洁/全新安装（如注释中所示）


• 尝试其他设备（可能有


• 尝试使用较旧的iOS版本（也许他们不小心给您iOS版本的信息不正确？）


• 在您的应用处于后台时，尝试模拟低内存环境（也许崩溃与您的应用在此情况下在后台关闭并重新启动相关）。

如果您无法重现问题，您可能希望从审核小组获取更多信息，而不仅仅是堆栈跟踪：

• 您可以更准确地了解如何导致崩溃吗？


• 这是对现有应用程序的更新吗？可能是因为您的应用程式尚未正确清除旧版本吗？

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

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

解决方案

To answer your question:

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

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):

• 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:

• Can you get more exact reproduction steps on how they are causing the crash?
• Is this an update to an existing app? Might they have an old version of your app that hasn't been cleaned properly?

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