xcode 应用程序卡在 iOS 9 上的启动画面中，没有错误
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/32837237/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
App stuck in splash screen on iOS 9 with no error
提问by danialmoghaddam
My app gets stuck on splash screen in iOS 9 both on iPhone and simulator. I can run it on iOS 8 or lower on device and simulator with no problem. My colleague working on the same app has exactly the same problem.
我的应用程序在 iPhone 和模拟器上的 iOS 9 启动画面上都卡住了。我可以在 iOS 8 或更低版本的设备和模拟器上运行它，没有问题。我在同一个应用程序上工作的同事遇到了完全相同的问题。
There is no error or anything, just hangs on splash screen. If I stop it on xcode and try to run it from the phone or simulator directly, it would run without any problem.
没有错误或任何东西，只是挂在启动画面上。如果我在 xcode 上停止它并尝试直接从手机或模拟器运行它，它会毫无问题地运行。
By the way, I don't see didFinishLaunchingWithOptionsor willFinishLaunchingWithOptionsgetting called!
顺便说一句，我没有看到 didFinishLaunchingWithOptions或willFinishLaunchingWithOptions被叫到！
回答by quellish
In your "answer" you include the code:
在您的“答案”中，您包含以下代码：
+(void)initialize
{
titles = @[NSLocalizedString(@"CODE", nil), NSLocalizedString(@"ERROR", nil), NSLocalizedString(@"TROUBLESHOOTING", nil)];
}
This is indeed the source of your issue. It's wise to be very careful when implementing +loador +initialize. @bbum has a great articleon exactly that topic.
这确实是您问题的根源。在实现+loador时非常小心是明智的+initialize。@bbum 有一篇关于该主题的精彩文章。
+initializeis invoked the first time the class (or category) is touched - when the class is initialized +initializeis called by the class loading mechanism. There is no guarantee of when in the class loading process this may happen, which is part of your problem.
+initialize在第一次接触类（或类别）时+initialize调用- 当类初始化时由类加载机制调用。无法保证在类加载过程中何时会发生这种情况，这是您的问题的一部分。
In your case you are using NSLocalizedString- which under the hood can be fairly heavy. It has dependancies on several other classes (NSString, etc) and can potentially access the file system. As @bbum points out in his article, that can lead to serious trouble. In your case, this may be a nasty deadlock.
在您的情况下，您正在使用NSLocalizedString- 引擎盖下可能相当重。它依赖于其他几个类（NSString等）并且可以潜在地访问文件系统。正如@bbum 在他的文章中指出的那样，这可能会导致严重的麻烦。在您的情况下，这可能是一个令人讨厌的僵局。
Move your titles = @[NSLocalizedString...line to a more appropriate place in your object, like an initializer, awakeAfterUsingCoder:, etc. and your immediate problem should be solved. After doing so you should check your entire codebase for instances where +initializeand +loadare implemented and audit them to make sure those uses are in line with @bbum 's recommendations.
将您的titles = @[NSLocalizedString...行移动到对象中更合适的位置，例如初始化程序、awakeAfterUsingCoder: 等，您的当前问题应该得到解决。这样做之后，您应该检查整个代码库中的实例，+initialize并+load对其进行审核以确保这些使用符合@bbum 的建议。
回答by danialmoghaddam
OK I found the problem. It sounds ridiculous though!!
好的，我发现了问题。虽然听起来很可笑！！
I am using UITabBarControllerand inside the first controller I have a UITableViewControllerwith a customised datasource class which would initiate a hard code table header and these headers are localised!!
我正在使用UITabBarController并且在第一个控制器内部我有一个UITableViewController自定义的数据源类，它将启动一个硬代码表头，并且这些头是本地化的！！
+ (void)initialize {
titles = @[NSLocalizedString(@"CODE", nil), NSLocalizedString(@"ERROR", nil), NSLocalizedString(@"TROUBLESHOOTING", nil)];
}
After I traced the stacks, I realised the process gets stuck right there with no trace and error! I still don't know why!
在我跟踪堆栈之后，我意识到这个过程卡在那里，没有任何跟踪和错误！我还是不知道为什么！
So I came up with a workaround:
所以我想出了一个解决方法：
+ (void)initialize {
titles = @[@"Code",@"Error",@"Troubleshooting"];
}
And only retrieve the localised value when returning the text:
并且仅在返回文本时检索本地化值：
- (NSString *)titleAt:(NSInteger)index {
return NSLocalizedString(titles[index],nil);
}
回答by Soleiro
Ok, I think I found the answer.
好的，我想我找到了答案。
You have to specify arm64 in all "Valid Architectures". If you don't specify arm64 or forget one the app won't start and stays on the splashscreen.
您必须在所有“有效架构”中指定 arm64。如果您不指定 arm64 或忘记一个，应用程序将不会启动并停留在启动画面上。
Just verified this.
刚刚验证了这一点。
Is this an Xcode 7 bug?
这是 Xcode 7 的错误吗？
回答by Soleiro
I have both debug and release set to NO You sure "any SDK" also has arm64?
我将调试和发布都设置为 NO 您确定“任何 SDK”也有 arm64？
