It's so stupid. Suddenly, my console in Xcode 4 remains empty. I swear, I didn't do anything. ;) Even if I restart Xcode or reboot the system. What the heck is that?
EDIT: it's not in other project. I must have set something wrong. But what?
chris
By console do you mean Output section? Could you try with a little app with only an NSLog to see if there's any change?
Related
I've searched around and can't find anything on this.
Using Swift 2 and Xcode Version 7.0.1 (7A1001). Every time I execute something in the debugger console, Xcode crashes.
The project is not very big, and has less than 10 third party frameworks.
I can't think of much more information that's relevant, but I'm sure there's more, so please do ask me if there's anything I should add to my question that would help.
I've of course cleaned build and derived data.
It's driving me insane. Thanks!
UPDATE 16/11/12
Submitted rdar://23559366.
How are you maintaining your third party frameworks? Via Carthage?
If so then this is probably your issue: https://github.com/Carthage/Carthage/issues/924
This is an issue if the location of the /Carthage/Build/iOS folder is in a different location to where it was produced (i.e if it was compiled on a different machine and the absolute file path has changed).
A temporary fix would be to run carthage build --no-use-binaries on your machine to rebuild the symbols using the current absolute file path working around the bug.
But if you wasn't using carthage then its probably not your issue so sorry
I had similar problem with Xcode whenever I hit breakpoint.
In case you see this screen right before your Xcode crashes - you are lucky and my fix might save you. All you need to do is open this window and in the Project Navigator, select any file that you want, so that instead of that white blank view you would get your code. After this you are most likely will be able to successfully stop your app at your breakpoint and perform the debug.
I am not sure why this happens, but I suspect that the reason is Debug View Hierarchy mode, which you might have triggered prior to setting you breakpoint and trying to stop at it. At least this is when it happens to me.
I have similar problem earlier.
If you try to print non-optional variable and unfortunately it holds nil value then it breaks/crash. so that make sure declare all possible variables as "Optional type".
Suddenly, only code completion which starts with # has stopped working in all Xcode projects in Xcode 6.
About a week ago, after upgrading to Xcode 6.0.1, I tried to use Debug View Hierarchy, then not only Xcode but also my entire Mac system crashed and it restarted. Since then, if I remember correctly, The problem has started to happen.
Most code completions are working correctly, like NSLog().
But, only code completion which starts with #, like #"string", #[array, ...], hasn't been working in all of my Xcode projects. When I type #, I can't see an automatic code completion popup window for NSString, id, NSArray, and so on. The code completion popup window automatically doesn't show up, but when I type the esc key, it shows up.
I tried deleting Derived Data from Organizer in Xcode, but It didn't solve the issue.
I updated Xcode to 6.1 just today, but it didn't work.
I tried re-installing Xcode 6.1 with deleting all files at ~/Library/Developer/Xcode, and it didn't work either.
Even in a new Xcode project, there's the same issue. One of the weirdest points is that this code completion issue happens in my all Xcode projects regardless of when they are created. Also, the code completion for only # doesn't work.
The code completion for # is used very often. It's a sooo pain in the neck... It would be great if you could give me any advice to solve this issue. Thanks!
I believe Apple has changed the behavior of this. So I guess get used to it.
I know it sucks, but at least you can change it to something else.
If someone knows how to get it back to like in Xcode 5 that would be awesome!
I'm experiencing a very confusing issue with Xcode. It started when the debugger started skipping over some lines and stopping at the wrong lines on breakpoints. I tried adding NSLogs, but they weren't having any effect.
I restarted Xcode and did a clean build, and now no breakpoints fire anywhere, and NSLogs don't work either, even in -applicationDidFinishLaunchingWithOptions:. I've made sure that the current scheme is in Debug mode, so I don't know why this would be happening.
Has anyone else experienced something similar?
EDIT: Logs that were present before I started having this issue still work, but no new ones.
#Jumhyn, You should write the solution then by yourself and accept that answer and close it or accept this answer saying ... TRY TO RESTART YOUR COMPUTER :)
I have an older iOS6 app that I was playing with last year; it was only for my wife, so I never released it, but I wanted to dust it off and see if it was potentially useful to others. So I load it up in XCode5 (5.0.2 running on 10.8.4; I've also tried this on my home laptop running the same XCode and Mavericks). However, though the app builds and runs fine, none of my NSLog statements show up in the console, on either computer. I've cleaned, rebuilt, run it on every simulator and iPad I have, hunted through settings, torn my hair out, etc., but I can't figure out how to get them to show up. I started a new iOS app to make sure it's not something in my setup, but NSLogs from there work just fine. Unfortunately, I'm not even sure where to start looking to fix this. Does anyone have any ideas for directions that I should be exploring here? Thanks!
Edit: I just tried copying over the files into a new project, and now the NSLogs are showing up! Still leaves me with no ideas as to why they're not showing up in the old project.
Edit2: It's not just user error; I can see the log messages from the new project with the copied files (see image). They just don't show in the old project when I run it.
Maybe you're not opened a Console in XCode 5, it seems, you're trying see a logs in member console.
Try click at here and you will see console with "All Output" option:
As noted in the comment by #combinatorial, I had a debug statement hidden (so cleverly that I fooled myself) in the pch file. Thanks so much for helping me nail that down!
so I followed the tutorial at
http://icodeblog.com/2008/08/08/iphone-programming-tutorial-populating-uitableview-with-an-nsarray/
It compiles and run successfully but it only shows Fruits at the top and no items.
Same thing happened when I followed another tutorial. Does anyone know how to fix this or what the problem is?
brute force:
run the code in the debugger with breakpoints on the entry and exit of every function learn what it's doing and see where it's failing. (At least on all the functions that display data or build data to be displayed)
optionally (since the code you linked to is 2 years (and 2 OS versions) old):
pick the sample code from apple that does the same thing (sorry, I don't know which one off the top of my head)
Did you perhaps miss some code in the applicationDidFinishLaunching block in the example at the link provided?
Or perhaps didn't link the FruitViewController to the view?
So I dont think it has to do with the guide. It has to do with some settings maybe? Somehow the xcode is not connecting to the iPhone simulator?