I got this error when after installing work with plus and running the menu. Is there anyway to fix this problem. Thank you
I just updated my XCode to 9.1 today, and surprisingly I can't find "Allow location simulation" in scheme setting, please refer to the screenshot below:
Has any one got the same problem? And any suggestion that I can fix it?
Apple's getting worse and worse lately.
I had this issue as well and the fix was to run the application in the Simulator and then go to Edit Scheme while the Simulator was running and the Core Location option magically reappears.
I just tried restarting XCode and running/stopping the app several times, then the checkbox magically appeared.
I've also fired a radar to Apple anyway.
I have recently started getting this warning in Xcode when working in Simulator mode. Apple were not able to help and suggested I submit a bug report, which I have done. But I wondered if anyone here has experienced the same?
It occurs when the keyboard is used during Simulator mode only. The screen freezes for a few seconds and then carries on. Very frustrating.
-[UIKeyboardInputManagerClient handleError:forRequest:] will retry sending handleKeyboardInput:keyboardState:completionHandler: to keyboard daemon after receiving Error Domain=NSCocoaErrorDomain Code=4097 "connection to service named com.apple.TextInput" UserInfo={NSDebugDescription=connection to service named com.apple.TextInput}
When I am running app on simulator it is working fine but when I am installing on device using developer profile it is giving error and showing build failed.But when try to see error detail it is not showing anything.I do not know whats the problem..
Please help me.
Thanks in advance!
Every time I open my app in Xcode 4.4 it crashes. It never used to do this in Lion and being very close to submission after about 6 months of work, I'm pretty annoyed to say the least!
This is part of the crash report if it helps; I can't make head nor tail of it. If anybody can help me, I'd be forever in your debt.
UNCAUGHT EXCEPTION (NSBadBitmapParametersException): Overflow allocating bitmap backing store. Cannot back bitmap with 1152921504606846976 bytes per row, -9223372036854775808 height, and 1 planes.
Um, have had that issue what I did Is delated xcode and redownloaded it.
Hope that works!
Experiencing such kind of problems, I got the following conclusion: 3 files can be corrupted
Your project file, in that case try using time machine to get the
one which will work
The XCode prefs: /Users/xample/Library/Preferences/com.apple.dt.Xcode.plist
Your project's Derived data ~/Library/Developer/Xcode/DerivedData
If one of those is corrupted, it will corrupt the 2 other one. To recover a project, start trashing the pref and derived data, then try to open your project. Reinstalling XCode did not solved my problem, using the DP4.5 neither in my case.
HOWEVER: Installing the latest "Command Line Tools for Xcode solved it (and this is probably the first thing to try)
Sounds weird but Xcode 4.4 has problem with printing out logs of big strings.
I had the same problem, and I deleted an NSLog which printed a big amount of text, and the crash stopped...
For me, I'm getting this crash when trying to open a particular .storyboard file from the project view. If I open the file directly through finder, it doesn't immediately crash so long as the window is small. If I try to resize it or scroll one of the views into view, it will crash again.
I faced same issue with XCode 4.5.1. It keep crashing whenever i open storyboard and it throws following error:
Application Specific Information:
ProductBuildVersion: 4G1004
UNCAUGHT EXCEPTION (NSBadBitmapParametersException): Overflow allocating bitmap backing store. Cannot back bitmap with 1152921504606846976 bytes per row, -9223372036854775808 height, and 1 planes.
Apple released new developer preview version of XCode 4.5.2 last week, which has fix for all intermediate crashes that we saw in previous versions. This build is available in https://developer.apple.com/devcenter/ios/index.action
You can try this.
This is going to Apple as a bug report I'm afraid; they said from the crash report that it looks like a bug. Thanks to everyone for their help.