My application crashes only when it does not work using the Xcode debugger. It was hard to track because I can't debug, but I finally figured it out. This was due to a release call on some object that did not belong to me. Before I fixed it, I searched and found here two related questions (links below)
IOS application Failure to start independently on the device, not crash when working through Xcode using the debugger or in the simulator
IPhone crashes only when the device is not connected to xcode, how to understand the crash log?
None of the above questions answered why there is no failure when working through debugger.So my question is, why is this happening? I know the reasons for debugging / releasing specific crashes, but this is crazy. This is a coincidence, although it happened more than 10 times.
, , - , . debug-malloc . , . (, , , ) , . , , () , . , -, , .
, - , , .
SQLite - [[NSBundle mainBundle] resourcePath], iCloud.
, iPhone, .
http://itunes.apple.com/us/app/console/id317676250
, , .
, NSString, UTF8String char. , , NSString, , , UTF8String ( , ) autorelease . , NSString .
, , , , , , - . , , ; , NSZombie .
, , , , , . , "" , , , . , , .
, , , , - . , XCode, iPad.
The application in question is written in Obj-C, but relies on some third-party code written in Swift. Swift code is included in the application as an embedded infrastructure. I had to set “Embedded Content with Summary Code” to “Yes” in the build settings for the application (in the “Build Settings” section), then the problem disappeared.