I'm trying to submit an archive to the App Store. Yesterday, the same process was working fine. I'm getting an Xcode quit unexpectedly error. I'm using Xcode 6.3.2. Please provide assistance.
Search results for
LLDB crash
29,557 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
When I try to submit my app to app store, the xcode crash and give me this log:Backtrace: 0 0x000000010c0a1b6a -[IDEAssertionHandler handleFailureInMethod:object:fileName:lineNumber:assertionSignature:messageFormat:arguments:] (in IDEKit) 1 0x000000010adfb5df _DVTAssertionHandler (in DVTFoundation) 2 0x000000010adfb8ce _DVTAssertionFailureHandler (in DVTFoundation) 3 0x000000010b76e48e +[IDEIssueManager _issueProviderInfo] (in IDEFoundation) 4 0x000000010b76db0d -[IDEIssueManager _updateIssueProviders] (in IDEFoundation) 5 0x000000010ae0e3de __73-[DVTObservingBlockToken observeValueForKeyPath:ofObject:change:context:]_block_invoke (in DVTFoundation) 6 0x000000010ad83d5c DVTInvokeWithStrongOwnership (in DVTFoundation) 7 0x000000010ac353e4 -[DVTObservingBlockToken observeValueForKeyPath:ofObject:change:context:] (in DVTFoundation) 8 0x00007fff8e7ca0f3 NSKeyValueNotifyObserver (in Foundation) 9 0x00007fff8e7d6d68 NSKeyValueDidChange (in Foundation)Yesterday erevything work fine.
I'm out of ideas and I have no idea how to solve this. Any help will be appreciated.I've got the following situation:MainViewController which points to a CollectionView embedded in a NavControllerCollectionView points to a DetailViewControllerDetailViewController shows the full picture chosen in the CollectionView and has a button which passes this image to the MainViewController. Protocol and delegate are used for thisThis image should now be shown in an UIImageView in the MainViewControllerThe delegation works. I have an UIImage in my MainViewController. BUT: the UIImageView is nil. So when I set the chosen Image as the imageView.image it crashes. The MainViewController is initialized and I also see my default Picture. See below for the code, and the console-output.MainViewControllerclass MainViewController: UIViewController, UserChosePhoto { @IBOutlet var googleImageView: UIImageView! var usedImage: UIImage? = nil override func viewDidLoad() { super.viewDidLoad() / println(viewDidLoad: (googleImag
Have you looked in Xcode? The Organizer now has a Crashes tab.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Having the same issue with the same backtrace. Xcode 6.3.2/Yosemite 10.10.3I was able to upload the app using Application Loader. The upload was successfull, but I recieved the warning The resulting API analysis file is too large. We were unable to validate your API usage prior to delivery. This is just an informational message.It looks like the Xcode crash occurs when trying to present a warning on a thread other than the main thread. Perhaps it is this warning?-Steve
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I'm having the same issue. It crashes immediately when the status shows Upload Archive. I've tried about 20 times, rebooted 5 times and nothing works. Same process worked yesterday and the past few years. Yosemite 10.10.3, Xcode 6.3.2
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
This is the crash report :Process: Xcode [570]Path: /Applications/Xcode.app/Contents/MacOS/XcodeIdentifier: com.apple.dt.XcodeVersion: 6.3.2 (7718)Build Info: IDEFrameworks-7718000000000000~2App Item ID: 497799835App External ID: 812404257Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: Xcode [570]User ID: 501Date/Time: 2015-06-17 13:55:50.417 -0500OS Version: Mac OS X 10.10.3 (14D136)Report Version: 11Anonymous UUID: 62FC1C66-70DA-161C-D548-575494D67226Time Awake Since Boot: 710 secondsCrashed Thread: 17 Dispatch queue: NSOperationQueue 0x7f808b240380 :: NSOperation 0x7f808b13c930 (QOS: USER_INITIATED)Exception Type: EXC_CRASH (SIGABRT)Exception Codes: 0x0000000000000000, 0x0000000000000000Application Specific Information:ProductBuildVersion: 6D2105ASSERTION FAILURE in /SourceCache/IDEFrameworks/IDEFrameworks-7718/IDEFoundation/Issues/IDEIssueManager.m:457Details: This method must only be called on the main threadObject: <IDEIssueManager>Method: +_issueProviderInfoThread: <NSTh
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I am seeing this too. Was able to work around it by closing the Xcode window but leaving Organizer open. Submission goes through and Xcode doesn't crash if you take those steps. Such voodoo.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I can't make a simple SKAudioNode test to work. Can somebody help. Here's what I trying to do:Initialization: let soundURL = NSURL(fileURLWithPath: NSBundle.mainBundle().pathForResource(TestSound, ofType: caf)!) soundNode = SKAudioNode(URL: soundURL) soundNode.autoplayLooped = false self.addChild(soundNode)Then when running play action: soundNode.runAction(SKAction.play())It crashes at that point with EXC_BAD_ACCESS at thread point libAVFAudio.dylib`AVAudioFileImpl::CheckClientFormatSet:The same TestSound.caf plays correctly with: soundNode.runAction(SKAction.playSoundFileNamed(TestSound.caf, waitForCompletion: false))What am I doing wrong?
I've found the session Optimizing Your App for Multitasking on iPad in iOS 9 really interesting.Thanks to a Carmack quote in 2011 I started to know about memory mapping in iOS, but I've never found a concrete example about how to achieve or where to apply that.The session comes whitout a sample code or playground file and is a pitty because I'd like to recreate a sort of a scenario to profile.Back into 2013 out of curiosity I wrote this answer on stack overflow about how to memory map big images, I never had a clear reply.Since the session talks about memory map sets of images whithout impact the RAM I'm not getting if I didn't understand some base concept or what I was doing wrong.I've test memory map with these simple lines of codes, but profililing with allocation I always saw the image allocated in RAM as dirty and crashes on real device due to the huge size of the image.NSError * __autoreleasing error = nil; NSData * mappedData = [NSData dataWithContentsOfFile:[[NSBundle mainBundle] pathForResou
Same error here. Project was fine yesterday.edit:Btw I get the error with Application Loader. If I upload with xcode, it just crashes with:Version: 6.3.1 (7703)Crashed Thread: 13 Dispatch queue: NSOperationQueue 0x7ffd5fee4140 :: NSOperation 0x7ffd6213f880 (QOS: USER_INITIATED)Exception Type: EXC_CRASH (SIGABRT)Exception Codes: 0x0000000000000000, 0x0000000000000000Application Specific Information:ProductBuildVersion: 6D1002ASSERTION FAILURE in /SourceCache/IDEFrameworks/IDEFrameworks-7703/IDEFoundation/Issues/IDEIssueManager.m:457Details: This method must only be called on the main threadObject: <IDEIssueManager>Method: +_issueProviderInfoThread: <NSThread: 0x7ffd63824880>{number = 35, name = (null)}Hints: NoneBacktrace: 0 0x000000011056dbfa -[IDEAssertionHandler handleFailureInMethod:object:fileName:lineNumber:assertionSignature:messageFormat:arguments:] (in IDEKit) 1 0x000000010f2c2b9f _DVTAssertionHandler (in DVTFoundation) 2 0x000000010f2c2e8e _DVTAssertionFailureHandler (in
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
Also the same issue via Application Loader. Xcode just crashes
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
I unpaired and re-paired my Watch to my phone per the recommendation here. This took quite a while (over an hour?) for the Watch to recover from as it had to undergo a restore (unfortunately losing my activity information in the process).After it came back to life and I got the Trust/Don't Trust dialog after firing up Xcode, it took another several hours before Xcode finally recognized my phone + Watch as a viable target. Xcode crashed constantly, as well. I was just about to head home for the day when I tried debugging my app one more time and ... it worked!If I have to do this again, I believe the solution to saving the activity data is to perform an encrypted backup to iTunes first, and then unpair/pair.Regardless, thank you for this solution, @MrBit!
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Application Loader ends up Invalid Binary, and Xcode just crashes. Weird. I've emailed to the App Store team at appreview@apple.com. Hope get through ASAP.
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
Hi All,I've read the other comments but haven't figured this out. Is it possible to play audio to the watch speaker as of beta 1? I can get the mp3 file to tell me I need an external bluetooth speeker on the simulator but my watch just crashes. I just can't figure it out and it looks like others can't fix it either. Then I see a hack for nanoFlappy that plays all audio to the watch speaker...***? I have tried the code on other post but it just doesn't work. So if anyone has code (Swift) that actually works, I would appreciate seeing it...Thanks.