在Xcode中成功编译和构建后,应用崩溃 [英] App is crashing after successfully compile and build in Xcode
问题描述
我的应用存在严重问题.它是在2012年末开发的,但现在我必须添加一些新的SDK.我已经通过CocoaPods添加了所有内容.
There's a serious issue with my app. It was developed in late 2012 – but now I have to add some new SDKs. I've added everything through CocoaPods.
尽管它可以成功编译并构建,但是它紧接着崩溃却没有向我显示任何错误/警告消息.
Although it compiles and builds successfully, it's crashing just after it without showing me any error/warning messages.
我已经尝试了很长时间,但仍然找不到办法.
I've tried to figure it out for a long time but still couldn't find a way.
以下是我的Xcode告诉我的信息(崩溃后):
Here's something that my Xcode is telling to me (after crash):
dyld_sim`dyld_fatal_error:
0x1030c4000 <+0>: int3
-> 0x1030c4001 <+1>: nop
这是我所看到的:
我还设置了错误断点:
但是没有运气.
我已经在main.m和AppDelegate.m中放置了断点,但是它并没有在这里停下来.
I've put breakpoint in main.m and AppDelegate.m but it didn't stop over here.
这是构建设置-体系结构:
出什么问题了?
更新:
在具有7.1的iPhone5上运行时,收到以下消息.
I got the following message when I run it on iPhone5 having 7.1.
信号5异常退出:跟踪/BPT陷阱:5
exited abnormally with signal 5: Trace/BPT trap: 5
更新2:添加了崩溃日志
Incident Identifier: 86E3767B-D6FD-4E31-A10A-3D1A87E66DFB
CrashReporter Key: bbd8c85f9242cf76be887456c573dc6db1b5d9ef
Hardware Model: iPhone5,1
Process: MY_APP [587]
Path: /var/mobile/Applications/D0526AD1-A61F-4951-B1D5-E508D10A2591/MY_APP.app/MY_APP
Identifier: com.myapp.MY_APP
Version: 1.0.9.2 (1.0.1)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2015-06-25 11:17:53.805 +0530
OS Version: iOS 7.1.1 (11D201)
Report Version: 104
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x00000000e7ffdefe
Triggered by Thread: 0
Dyld Error Message:
Library not loaded: @rpath/XCTest.framework/XCTest
Referenced from: /var/mobile/Applications/D0526AD1-A61F-4951-B1D5-E508D10A2591/MY_APP.app/MY_APP
Reason: image not found
Dyld Version: 324.1
Binary Images:
0x2be97000 - 0x2bebafff dyld armv7s <4d05d388718832c99cdd4e74aeb07d51> /usr/lib/dyld
0x2f356000 - 0x2f458fff AVFoundation armv7s <c88b12b244d13bbd9a8ab681956234e4> /System/Library/Frameworks/AVFoundation.framework/AVFoundation
0x2fa79000 - 0x2fa99fff Accounts armv7s <73b0639b81fe30d5b2b13628d3df2273> /System/Library/Frameworks/Accounts.framework/Accounts
0x2fc1a000 - 0x2fc2bfff AssetsLibrary armv7s <372ff89a2ede36aa85ce562f3e513f07> /System/Library/Frameworks/AssetsLibrary.framework/AssetsLibrary
0x30541000 - 0x30665fff CoreGraphics armv7s <182ccc3a111d360eb5c1e58b4289afb3> /System/Library/Frameworks/CoreGraphics.framework/CoreGraphics
0x30988000 - 0x309d7fff CoreLocation armv7s <5d78705a46ab313fa21f1d5ed2f0ce3f> /System/Library/Frameworks/CoreLocation.framework/CoreLocation
0x30a0f000 - 0x30a8afff CoreMedia armv7s <d68d0cf856f13ff7ab9418ccd671cd65> /System/Library/Frameworks/CoreMedia.framework/CoreMedia
0x30b34000 - 0x30b8cfff CoreTelephony armv7s <711db5ac808937b09143f43f11f06422> /System/Library/Frameworks/CoreTelephony.framework/CoreTelephony
0x30b8d000 - 0x30c1dfff CoreText armv7s <43e84c5a90fc36a984363965f2d8029b> /System/Library/Frameworks/CoreText.framework/CoreText
0x30ded000 - 0x30fd7fff Foundation armv7s <b75ca4f9d9b739ef9b16e482db277849> /System/Library/Frameworks/Foundation.framework/Foundation
0x31c27000 - 0x31cd2fff MessageUI armv7s <42cf298919f134d888a001f1336c2550> /System/Library/Frameworks/MessageUI.framework/MessageUI
0x31cd3000 - 0x31d36fff MobileCoreServices armv7s <1a736ebbc93431c8943cdd93a0a0fdcb> /System/Library/Frameworks/MobileCoreServices.framework/MobileCoreServices
0x3277e000 - 0x32786fff OpenGLES armv7s <1c3e551d0a923b86940ad36a6e682463> /System/Library/Frameworks/OpenGLES.framework/OpenGLES
0x32971000 - 0x32ab8fff QuartzCore armv7s <741ee0338b1235aab1550f91a3956041> /System/Library/Frameworks/QuartzCore.framework/QuartzCore
0x32b12000 - 0x32b54fff Security armv7s <cd7187d315eb301e845cfae580ca905f> /System/Library/Frameworks/Security.framework/Security
0x32ca4000 - 0x32cf3fff SystemConfiguration armv7s <82758c34b29a333bbdfe73e78361e0e1> /System/Library/Frameworks/SystemConfiguration.framework/SystemConfiguration
0x32cf4000 - 0x32cf5fff Twitter armv7s <b6adeefeb05639abb4140fa07a92e705> /System/Library/Frameworks/Twitter.framework/Twitter
0x32cf6000 - 0x33469fff UIKit armv7s <f725ad0982673286911bff834295ec99> /System/Library/Frameworks/UIKit.framework/UIKit
0x3a5d0000 - 0x3a61bfff libc++.1.dylib armv7s <72615c78ae5f39dcbafa740d87035caf> /usr/lib/libc++.1.dylib
0x3af0a000 - 0x3afa1fff libsqlite3.dylib armv7s <584eaf4090783a64b8a33125a6a976bd> /usr/lib/libsqlite3.dylib
0x3b0f0000 - 0x3b0fcfff libz.1.dylib armv7s <578def3dfb6e3180b5f9d0cdacfea7ab> /usr/lib/libz.1.dylib
推荐答案
我能够构建&从项目中删除 OCMock
, Specta
和 Expecta
框架后,运行应用程序,然后在 Command + R 使其起作用.谢谢大家的2美分:)
I was able to build & run the app once I removed OCMock
, Specta
and Expecta
frameworks from my project, and then, a full cleanup and cleaning of derived data before Command+R make it works. Thanks everyone for your 2 cents :)
更新:
执行完此操作后–我无法调试我的应用程序.我应该只允许在 release
模式下运行它.否则会给我这个错误.
After doing this – I'm not able to debug my app. I should only allowed to run it in release
mode. Otherwise its giving me this error.
架构i386的未定义符号
undefined symbols for architecture i386
这篇关于在Xcode中成功编译和构建后,应用崩溃的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!