I'm having some trouble working with xCode. It just keeps hanging and using 100% CPU right after a couple lines of code. I'm working on a new project and it barely has two files and it has become completely imposible to work with.
I tried reinstalling xCode and starting my project from scratch but it won't work.
I noticed three things that may help someone find out what it's going on.
It's slow even when typing, the characters appear delayed on the screen.
It keeps saying indexing on the task bar on top. If I clean the project it will disappear but come back whenever I start working again.
It overheats as soon as I open xCode
And here's some other facts that might help
I'm running xCode 6.1.1 (build 6A2008a)
My Mac is a mid 2012 MacBook pro 8GB Ram
I did a fresh install of Yosemite a month after it was released, so it's pretty clean.
I'm using the latest build of Xampp for my SQL server
I'm using nodejs as a backend so I'm running an http with nodemon
Hope any of you has a solution to this.
Thanks and merry christmas to all of you.
EDIT
I found out that it will build just fine if I remove my conditional cast to NSInteger, NSString, Float, etc. I have like 8 of them one after the other, and just replacing as? for as did the trick. I'm curious as for why this is happening anyway though.
Similar problems on 6.1.1 (but also source kit crashes) were improved (but not completely resolved) for me by deleting derived data.
Related
I've been working on a lightweight game with some friends. Today I updated Unity to 2018.1.0f2, and after about 30 minutes of loading time, I was able to edit my project again.
But all of a sudden, Unity is being very slow. I try playing the game, and it is running at about 2-3 FPS. The current editor mode is DX11, but I tried forcing it to OpenGL and that only made it much worse. My computer should be able to handle it; I have a GTX 1080, 32 GB of RAM, and an i7-8700K.
Can someone please explain what is causing this, and how to fix it?
Also, there is a known bug involving Unity collab being slow. I am not using that.
I'd try two things:
1) Uninstall all Unity installs you have (2018 and earlier, if you still have them), then re-install 2018.1.0f2 from scratch.
2) Go to your project folder, and delete everything except the dirs Assets and ProjectSettings (you may delete even this one, but then you need to re-set all project settings from scratch) - remember that if you imported packages via NuGet, you should leave the Packages directory too.
Then try to relaunch Unity and load the project by opening it from the Unity launch window and see if it lags again or not.
Let me know how this goes.
I'm working with an old (Delphi 2010) app with a number of very specific components that have to be installed, some from compiled from sources. It's a pain to set up, is what I'm getting at.
Currently, I have it on a Windows 10 machine, but I haven't upgraded Windows 10 in quite some time. If I upgrade Windows, it breaks the debugger (and I haven't been able to fix that so I've downgraded Windows).
I'm trying to find any way to move the Delphi environment without having to go through the various steps to get it to work, like making a VM out of it. Or, if I have to go through the steps again, only do it one more time in such a way that I can push-button recreate it. (There are a lot of things I need to try to upgrade the app itself, but many of those strategies will break the environment for me.)
Any strategies?
I'm working on an iPad app and I need to try a few things, for which I usually have a small sample app that I use. While my primary app project opens just fine, the sample app doesn't. Xcode (Version 5.0) just sits there, the wait cursor spinning. The other odd thing is that when trying to make a new project, I get the same behavior.
What's going on here? Various other threads on Stack and other forums suggest removing various files, in ~/Local/... and in the .xcodeproject directory. However this doesn't seem to help. Any ideas as to what's going on?
I restarted my macbook and XCode behaves now. There goes my 200 day uptime...
My company is still running Snow Leopard and we're thinking about upgrading to Mountain Lion (Edit: Mavericks) soon. We are developing iOS and Mac OS X applications and have a small break between the old projects and the new projects. What this means is, that we can start over with the new applications on the new version. But what happens to the old versions? They don't have ARC, Storyboards etc... I know you can switch off ARC but we want to make sure that we will still be able to commit updates to our old projects and we can't afford to put lots of time and effort in the conversion process.
I spent some time reading the user comments below the xCode update on the AppStore and read that the new Version deleted old projects. Of course we have a backup but this makes me uncertain if it's the right step.
Does anybody have experience how this works in a non personal environment? At home I'm running Mountain Lion and xCode converted small projects by itself. I'm just not sure about large scale projects...
Thanks for your time!
Edit: I will upgrade one system tomorrow and then try to post the results and maybe some tipps, important steps and things to be aware of.
Tipps what to consider when doing an upgrade:
Before you start
Take your time for a good backup! - You can regard data which is only
located on one harddrive as non existend.
Start with one system first and try out everything before doing the
major upgrade.
Installation
Consider it takes way more time than it does at home! The
MountainLion Download took >5 hours because of a symmetrical internet
connection. Installation time was ~1 hour (MacMini 2009 - 4Gigs Ram
1067). + xCode Downloadtime ~1hour
Before you install the new xCode make sure all your projects and your old xCode Dev Folder are
backupped.
When the installation routine asks you to delete your old xCode do so
(I didn't do it and now I have to manually assign each project to the
new xCode. I've to delete the old version manually too and it's a bit
more complicated if you have to do the research which files you are
allowed to delete and which not)
Then you have to download the different xCode
libraries. There goes at least 1 additional hour.
Time of the downloading- and installation process so far: ~8 hours. (Keep in mind we've a slow internet connection)
Projects
Copy your projects and don't run your conversion and tests on the
original.
When you open the project you'll probably receive lots of warnings.
Don't Panic!
When clicking on the "Validate Project Settings" warning xCode will suggest to convert your
project for you. I've done this for 3 iOs applications (Build Target:
4.3) now and it worked every single time. Let it create a snapshot for you. Just in case.
If your app has already been code signed you'll probably receive the
"Target Integrity" warning. In every single case it worked for me to
edit the path for the "entitlement.plist". (Just click the warning
and edit the path at "Code Signing Entitlements")
It may happen that you've to change the deployment-target. To do so
go to the Project Navigator (cmd + 1), click on your
project's name and then Summary. There you can edit your
Deployment Target.
If you get warnings on deprecated methods you should search
stackoverflow.com for your particular case. If it has to do with
NSURLConnection look here.
To be continued...
I have an Xcode project that has been upgraded to Xcode 3.2, and whilst it builds fine (and produces an executable that runs fine), when I try to debug it the debugger doesn't start.
When I look in the debugging window, it says that the build was fine. When I look in the console, I get a 'Session started ', but the application never begins.
I've had a wander through the build settings, and can't see anything that appears to be turned off when it should be turned on. I thought it may be a new setting that I need to turn on, but I can't see anything of interest that may help.
Any advice would be grateful accepted!
Cheers and thanks.
Have you tried a full Clean of the project?
I was having the same problem and just discovered that my app launches on the iPhone correctly when I've started Xcode from the finder, but not when I've launched Xcode from my shell. For example, I start Xcode by typing "open project.xcodeproj" into my bash terminal, and device debugging is broken, but if I start Xcode via spotlight or by double-clicking on my project, or from the Applications folder, device debugging works fine. I'm not certain, but it appears to be a problem with my shell environment variables.
Thanks to Rob for the advice. I tried rebuilding everything a couple of times and still to no avail.
However, after turning on my machine this morning, trying the project out it now debugs quite happily. I'm guessing that after installing Xcode I should have rebooted the machine (it didn't require one according to the installer).
Thanks all.