I am using Xcode 6.1 with a Swift project.
I get the "SourceKit" (iirc) editor crashing issue several times a day but it usually resolves itself and doesn't result in having to close Xcode.
Now the last time it happened it resolved itself but has now taken away all autocompletion calls. Nothing autocompletes, my class functions, UI*, nothing (aside from basic types UInt etc).
I have cleared derived data, removed Xcode and it's related files, re-installed and nothing completes automatically, nor by using the escape key to show suggestions. Autocomplete is definitely checked in preferences as I have been using it for almost a month prior to todays issue.
Has anyone else experienced this? and does anyone have a solution to this problem? Really, really need autocomplete back.
Thanks
Yes this is a bug that I have been experiencing for the last few days in 6.1 The solution for us was to stop building on the simulator. Once we did that (and started testing on actual devices) the sourceViewKit started working again. I'm not exactly sure why this is the case, but it seemed to work for us when nothing else did.
It is definitely a bug.
In fact changing to a different simulator (i.e. iPhone 5 to iPhone 5s) and running once does also solve the issue. You do not have to run on actual device (for those who do not have a paid developer license)
Xcode 6.3 public release version (released publicly at time of writing) seems to have fixed these issues (at long last).
Related
I am using the two finger swipe gesture to go back on Xcode a lot.
At least I used to because it seems to be broken since a few weeks now. Instead of going one step back, it now appears to jump two steps, making the feature completely unusable for me.
What I have tried:
restart Xcode
restart Mac
go through ~/Library/Developer/Xcode and delete or change various settings (getting desperate)
...but to no avail.
So I am starting to think that this my be an actual software bug in the particular Xcode version (I am using 12.5) but it seems unlikely because an issue like this should be easily caught by the engineer even before submitting the build to QA – just by the developer building the Xcode version, presumably with Xcode itself.
Does anyone else experience this? Is there some broken setting or cache that needs to be reset? Or can the hypothesis be backed up that this is indeed a software bug and all we can do is sit on our hands and try to reprogram years of muscle-memory to use control-command-left instead?
Xcode13 release fix it.
"methods
Additional bug fixes and stability improvements"
I have been using Xcode 10.2.1 since it came out and been having a pretty consistent performance issue. If I have Xcode open for a while it get's increasingly slow to the point that it's nearly unusable. Even clicking on controls in interface builder has a 2-5 second lag. The issue seems to resolve itself after restarting Xcode, but it's getting pretty annoying working with a laggy Xcode. I've also noticed that previously opened files are sequentially closed out of the main window (~5 per second) as Xcode quits like they had been open the whole time. It's very odd. Anyone have any idea what's going on or how to fix this issue?
Thanks in advance!
I just upgraded from XCode 9.2 to XCode 9.3.
Since then my playground is very unresponsive/slow, animations play at unexpected times and UIKit elements are not properly layouted anymore.
Are there any known issues and/or fixes that I can apply?
Had same issue and there was no way around it. People filed bugs as far back as April 8th.
Best solution is to download Xcode 9.4 Beta from Apple Developer Page.
This worked for me and CPU usage is low and Xcode doesn't crash on playgrounds anymore.
Playgrounds have been buggy all along but 9.3 takes it to another level. Have you noticed a “diagnosticd” process taking up much of the cpu while running playgrounds? I suspect that this may be in part responsible for the lack of performance. Not much to do until Apple gets their act together (if ever)
Xcode 9.3.1 has just been released (10 May 2018) and is supposed to fix 'an issue that caused Xcode to slow down when editing a playground'.
Kill "homed"
My experience is that homed is going nuts, hogging the CPU.
Without quitting the Playground app, you can go into Activity Monitor (Applications > Utitlities > Activity Monitor) and sort by %CPU, you might see Process Name homed taking a large CPU load. Double clicking on homed and selecting Quit does not seem to harm the workings of the playground.
If you still encounter problems, you could close the Playground app, and use the same process to force quit com.apple.CoreSimulator.CoreSimulatorService, although doing that requires a lengthy process when you restart your Playground.
Have anyone tried out the new Color Asset Catalogue feature in Xcode 9. For me every time I edit something on this like adding or editing a colour asset, I have to wait for 10-15 seconds while Xcode shows the coloured progress and does not allow any interaction.
At the same time being highly annoying, it is also highly counter-productive. I also found IB to be generally too slow after updating to Xcode 9.
Are these known issues ? Is there a solution to this?
i asked apple about the hangs and crashes that keep on occurring on Xcode 9, and they replied:
First, quit Xcode. And then temporarily move aside
UserInterfaceState.xcuserstate so that new user state is created.
It can be found here
path_to/$WORKSPACE.xcworkspace/xcuserdata/$USER.xcuserdatad/UserInterfaceState.xcuserstate
(if it is an .xcodeproject, it will be deep in the project.xcworkspace
directory).
this worked for me with autocomplete problems and switching between files. hope it helps you out as well.
Xcode 9 is borderline unusable for me too at times. The worst is how long it takes to open/edit a storyboard file and also run the simulator. Even autocomplete and switching between code files is lagging a lot for me, much more so than past versions. I imagine Apple knows about it considering the Apple development forums are full of threads about how the newest update is unacceptable but as for how long it will take for them to do anything about it, who knows. It's an absolute nightmare for iOS developer's productivity to say the least.
My solution is to just quit Xcode when it starts getting too slow. It's a pain, obviously, but usually helps short term.
Ever since I started using Xcode, I've experienced extremely annoying problems with Code Sense. The problem is that when Code Sense kicks in for code completion, sometimes the source code text below the line I'm working on goes "crazy". If I continue typing, the problem gets worse, and after a while the source code is completely screwed up (funny colors, missing lines and characters, ...). Strange enough, the source code itself is unaffected, because when I select another source file and then go back to the one I was working on, everything looks fine again.
The problem can be seen in this screencast: http://www.screencast.com/t/OGY3NWE5
Interesting facts:
This problem has occurred on 3 different machines, so it's not related to a corrupt installation.
Sometimes it's fine for a while (up to one hour) after launching Xcode, but once it starts happening, it's getting worse and worse, until Xcode is restarted. Then it's fine again (for a while)
I've searched the web for similar experiences, and I can't find anything. I would think that it is a known problem, since it occurs on 3 different Macs here (both running 10.5 and 10.6).
Anyone having the same problems? Or a suggestion for fixing this?
Yeah, it can be a real pain. I didn't find a 'fix for it as such, but I do a quick switch from implementation to header (or vice versa) and then back again using Command-option-up. The screen redraws and everything is fine again
Well, I finally (kind of) fixed this problem by simply turning off Quick Help. Previously, I left this on all the time, and it resulted in a very unstable code sense (to the point where Xcode simply became unusable).
This is not a real solution, but it should at least help people experiencing the same issue.
I wrote about it here
My issue was with localization. if your XIB file is localized using xcode 4's, then it was failing for me. removing the localization worked, though not a proper solution.