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 :)
Related
I was changing some stuff around in my app and tried to re-run it and all of a sudden I get a ton of errors in the console that don't really make any sense. Does anyone know what's going on here? How do I fix this?
Solution: Restart XCode... it had to install some stuff so that it could run. sigh
I have Xcode 6.1.1, and my app crashes on start up. It never reaches the start view (not even its awakeFromNib), but crashes on UIApplication on main. When it breaks there, I get NOTHING in the debug. Literally nothing. If I continue the program anyways it will work, flawlessly. But it ALWAYS breaks at UIApplication at startup. So I press "continue" and the app works as intended. I've tried the project on another computer, works fine there. I've tried reclone my project, doesn't work on my computer/xcode, but on another computer. It's just as if I have a breakpoint on UIApplication main...
If I reverse to previous commits, like 18 commits back, it works fine. If I then remerge with latest commit, it crashes on UIApplication again.
Starting to get upset here, anyone who has the faintest idea of what could be wrong here?
Try this:
remove all breakpoints.
make sure you are not sharing breakpoints
in repository ;), check your git ignore file if needed, check data in
git.
add exception break point to all Objective-C Exceptions
run the project
Found it. The problem was that there was a breakpoint set on "All exceptions" in the breakpoint data. It felt so weird that I could force to continue and it would work flawlessly, so it was indeed a breakpoint sneaking about.
Thanks for the help, I would not have found this without your help.
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!
I am currently attempting to port a game I've developed in the Wintermute Lite engine to iOS platforms. My game will compile just fine in XCode (albeit using the armv6 architecture) and will run perfectly on the iOS simulator; however, when I try to deploy it to an iPad, the first thread will halt in XCode with the error "EXC_BAD_ACCESS (code=1, adress=0xfffffff6)", pointing to a non-specific line of assembly code.
First of all, if you guys have any ideas right off the bat as to what might be causing this, I would greatly appreciate some help. The thing is, I'm more than willing to debug this myself, but being a complete noob with Objective-C as well as XCode, I'm not sure how to trace this specific error back to the line of code that's causing it (I apologize if this is a really basic question but I've already attempted to find a command to get the line of code associated with the error, but with no success).
I realize that this is scant on details, but as I said, I'm not sure how to pinpoint the piece of code that's causing this error using XCode, otherwise I'd just debug this myself. If there's any extra information I can provide, let me know.
Thanks in advance for any help!
I got it working. After a lot of messing around with XCode, I realized that I incorrectly configured the project file provided by Wintermute. As far as I can tell, it had something to do with the fact that the project was originally set to build for "iOS Universal" and I changed it to "iPad 5.0," which somehow caused the project to break upon deployment.
Anyway, I started over with a new XCode project file and got it to compile perfectly! Sorry for the bother.
The problem is the fact that it isnt ment to run on iOS. The reason it runs on he simulator is that it is building for a Intel chip set, not ARM. Even though you set it to armv6 it doesn't mean that the code will run on a non-intel device.
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?