I just upgraded my Xcode to Version 8.0 (8A218a), when I insert some breakpoints and run a project, it just stops for like two minutes then goes to one breakpoint and then takes another two to go to the next one.
Update: Step over also behaves the same (very SLOW).
Does anyone else using 8.0 meet this issue?
I had the same problem.But it only happen in iOS8.It won't happen in simulator or iOS9+.So,upgrading your iOS version may solve this problem.
In my case Xcode 8 automatically added a lot of variables to Debug area including those not available in the current context. Hiding debug area significantly improved performance.
I had the same problem.happen in iOS10.Delete Breakpoints and disable source control.Has been resolved.
Related
I have Updated Xcode yesterday from version 7 to version 8.1 overnight and deleted the xcode 8.0 beta that i had!
Today I tried to Open all my projects, and when I go to the storyboard, I get the following Error..
An internal Error Occured. Editing Functionality may be limited. Report a Bug (which I did).
The project that I opened, does not use size classes or autolayout.
I have searched many questions on the net, which pointed that the problem is caused by projects without autolayout. or suggested that i clean xcode, simulator, deleted derived data folder.. all without success..
I also tried saving the storyboard as an Xcode7x file with no success..
Finally I tried creating a new SingleView Application and added a UIButton to it.. (while using size classes, autolayout..) still the same.. so it's definitely an Xcode Bug issue.. Not an autolayout incompatibility problem.
any hints?
p.s. compiling the project will actually run great, and all ui elements will show as intended. I don't have Xcode7 installed anymore.. any suggestions?
I can not reproduce the crashe, but I could fix messed up UI by setting up the following under Editor menu -> Canvas:
It was fixed when i updated xcode!
Yes, this happens to people. Yes, I've looked at all the solutions.
This is different.
XCode starts and there is no error message, it just freezes. This is the screen I get:
That's it. No errors. I can't interact with it, I can't close it. The only thing I can do is use Show All Windows. There are five and yes I don't need them all (never did! don't know why I have them) but I can't close any of them. To get rid of it I need to do a hard reset.
I've tried deleting the library file in Finder as this was one of the solutions.
Nope.
Anyone any ideas?
I think it's XCode 6 (the latest) but I can't tell because I can't access the menu.
I ended up scouring Stackoverflow for ways to clear the startup process.
You hold cmd+shift when you start XCode - ONLY from the task bar, this does NOT work if you go into the Applications folder - and it will load blank.
Then you can load your project.
I searched StackOverflow and it doesn't look like many people are having this problem, but for me, this happens very, very frequently. Maybe not every time, but perhaps every other time.
Once I try to build and run the app, Xcode crashes, and in a strange way: it just disappears with no error messages, no suggestion to report the problem, nothing at all. This happened with Xcode 6.0 as well. It doesn't matter whether I am running the app on a device or on an emulator.
To prevent the crash, I need to Product > Clean. If I do this clean each time before running the app, crashes do not happen, but once I forget to do that, Xcode can crash any moment.
I don't think I ever had this crash with an old project, but it keeps happening with the project that I started in Xcode 6.0.
Because of that, iOS development is becoming for me quite a painful exercise, similar to pre-Android-Studio Android development.
Is it just my problem, or maybe someone else is having it? Maybe someone has a solution?
I just started running into the same issue and found a workaround for it. Found it to be an issue with building when Xcode is full screen. Seems silly, but so far exiting full screen mode has worked for me. I've been able to re-introduce the issue after building full screen a few times, and then instantly fix it again by exiting full screen.
Yeah, it's not that the app is crashing, it's just that the click is triggering the red close window button behind the red button (yeah, seriously). You'll notice, Xcode is still open, it's just that the window has closed. You might also notice that sometimes when you click "stop" in full screen mode, it switches to non full screen. Again, the tap is passing through the run/stop buttons to the underlying window controls.
So dumb.
I solved it using 'cmd + R' instead of clicking the run button
I have a calendar program that I am trying to convert to iPad (using XCode4, no storyboards, but running on the Simulator).
It currently is not behaving correctly when I move to a previous month (I get a blank screen before the view is re-drawn). So I commented out the code that does the actual creating and drawing of the screen, and the screen is still re-drawn! I comment out other code, and the same thing happens... it's as if it is ignoring the commented statements!
I am dumbfounded as to why this is happening... I have done multiple cleans, straight builds then run... same thing happens.
Any ideas?
Have you tried clearing the cache of the simulator?
From the simulator menu:
IOS Simulator > Reset contents & settings
Try cutting out the code from Xcode. If it still runs then something is seriously wrong. Also try duplicating the project folder in finder and run the new project, it has solved some weird xCode behavior for me.
An unmatched brace, parenthesis or other syntax error can cause both the problems you describe.
I have put NSLog points throughout the launch stuff of my app, including delegate methods. The last one I can find that gets hit, gets hit about 2 seconds before viewDidAppear. How can I find out where my app is slowing down?
You can use the Time Profiler tool on Instruments for determining how long each call takes.
In xcode you can use Instruments tools. It's really useful when looking for memoryleaks, performance issues etc.
Trigger the problem while using the tools.
See the Apple link for getting started with Apple Developer tools.
Apple Developer Tools
Best,
In your question, you note that you're using NSLog statements, which can be useful, but at the same time setting breakpoints can be even easier and provide more insight to your problems. Try adding a breakpoint in the tray on the left side of your code. You can also set conditional breakpoints to analyze the code that is being stopped on.
Combining the use of breakpoints with Instruments can greatly help you understand your apps performance and possible problems. You can find the Instruments application in Xcode 4 under the Xcode menu. Click Xcode -> Developer Tools -> Instruments. You can also Profile your app with instruments by clicking and holding on the Run button and then selecting Profile:
You should then see a screen like this:
Select Time Profiler to determine how long each call takes. Then click Profile