ios - 当我启用使用自动布局时 Xcode 5 崩溃

Question

由于错误，我在 Storyboard中禁用了自动布局，当我想再次启用它时，Xcode 崩溃了。我需要帮助!这非常重要....

错误是:

Process:         Xcode [315]
Path:            /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier:      com.apple.dt.Xcode
Version:         5.0.2 (3335.32)
Build Info:      IDEApplication-3335032000000000~4
App Item ID:     497799835
App External ID: 106632651
Code Type:       X86-64 (Native)
Parent Process:  launchd [133]
User ID:         502

Date/Time:       2014-01-27 08:33:35.371 +0100
OS Version:      Mac OS X 10.8.5 (12F45)
Report Version:  10

Interval Since Last Report:          2942 sec
Crashes Since Last Report:           12
Per-App Interval Since Last Report:  2564 sec
Per-App Crashes Since Last Report:   12
Anonymous UUID:                      24878C32-E46C-C700-0F6F-8B0D08B0549F

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
Sending userDidChangeValue: to <IDEInspectorBooleanProperty: 0x7fec6f13dcd0> from <NSButton: 0x7fec6f09da40>
ProductBuildVersion: 5A3005
ASSERTION FAILURE in /SourceCache/IDEInterfaceBuilderCocoaTouch/IDEInterfaceBuilderCocoaTouch-3747/IBPlugin/Utilities/IBObjectMarshalling.m:670
Details:  Failed to run one shot request for IBUIDatePicker, IBUIImageView, IBUITabBar, IBUITabBarItem, IBUITableView, IBUIView, IBUIViewController, and IBUIViewControllerAutolayoutGuide.

Interface Builder encountered an error communicating with the iOS Simulator. If you choose to file a crash report or radar for this issue, please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" and include their content in your crash report.

Exception name: NSInternalInconsistencyException
Exception reason: UITableView dataSource is not set

错误较大，但我不能添加太多代码。

编辑:

我的 Xcode 的图像:

编辑:我再次重新安装 Xcode，但还是同样的问题。

Answer 1

解决方案:

最后我解决了这个问题，使用我的 Storyboard的旧版本并应对 (cmd+c) 新的 View Controller ，当我复制到旧的 Storyboard时，这个 View Controller 启用了“使用自动布局”。这是一个糟糕的解决方案(但速度更快)。在我看来，这个问题是一个重要的 Xcode 错误。