objective c - iPhone SDK 3.0 beta 4 broken, Internal Error -
Last edited: After downgrading to SDK for iPhone 2.2, this problem has been solved, then all Files have been removed from the crash window in the Organizer window (then upgrade back to 3.0 beta 4) Apparently, there were many crash logs (like 300+) associated with my iPhone, thanks for the insights! Original Problem: When I updated my iPhone SDK to the latest Beta 4 (released on 28 April), even when I open it, it crashes completely, Excluding me: / P> Does anyone know what this internal error is, is the NSCF coming out of the trade boundary? Now I can not open Xcode to do some general, non-iPhone related programming. So disappointing My guess is to do something with my device (in the organizer window). So anyway my iPhone's profile is there to remove (Ian Zhao's iPhone), so I can start a new one. I try to uninstall / reinstall the SDK, but my old iPhone's profile remains. EDIT: I paste the error message from the console (application / utility / console). Now the external editor looks like some mess with compatibility (I'm using TextMate as my external text editor).) The problem is that I set Xcode- to the text editor back to Xcode- > Can not open any preference? 03/05/09 9:22:49 PM Xcode [2457] Error loading / library / input manager / edit in ODBEditor / edit in ODBEditor.bundle / contents / macode / edit In ODB editor: Edit in Dlopen (/ Library / Input Manager / ODB Editor, edit in ODB Editor, Edit in Bundle / Content / Maccode / ODB Editor, 265): No suitable image was found. What was found: Edit in Library / Input Manager / ODBEditor / Edit in ODBEditor.bundle / Content / Maccode / ODBEditor: GC Capacity Mismatch 03/05/09 9:22:50 PM Xcode [2457] ODCompletionDictionary (version 4.1.v255) loaded 03/05/09 9:22:51 PM Xcode [2457] An unwanted exception was raised Thank you, please help me; My developing life is now in a halt: (
Try removing the closing dictionary, which is a There is a third-party extension that hooks into Xcode. One part of it is not loading, because this purpose is incompatible with the waste collection, and I think that when the second part is loaded, then using that code Tries that fails to load, and crashes the encode.
Comments
Post a Comment