I have a problem to open my project in Xcode 8 it's loading and not open. Yesterday It's opened but today not. I already deleted xcurdata folder, cleared DerivedData folder and deleted file com.apple.dt.Xcode in ~>/Library/Caches
Someone give me a light?
It's a problem with my icloud. My project was in Documents and every time that I install some framework with cocoapods, the Xcode stop to work, and load after icloud finish sync. I solved the problem putting the folder of project out of icloud.
This is in regards to an issue where you try to load a project in Xcode 8 after doing a migration to Swift 3 and all it does is stall and show the "Loading..." indicator in the Xcode status window?
Other methods of trying to correct this were:
1) Deleting ~/Library/Saved Application State/come.apple.dt.Xcode.savedState
2) Deleting /xcuserdata/ from Project.xcworkspace and Project.xcodeproj
3) Backing up the current story board, removing it from the project, recreating it, then cutting and pasting the contents from the old story board to the new story board.
I've tried all of the above to no avail. I've also upgraded to 8.1. I had a git folder inside my documents folder, so I am in the process of migrating that out my documents folder. Will try to load the project again after it's finished.
Just curious but did you have the "Optimize Mac Storage" option checked for iCloud sync? I did have it checked, I could see how this could cause a lot of issues with Xcode should your projects be stored in the documents folder. If some assets aren't getting touched for a long time, they are removed from the local drive and only stored in iCloud...
In my case with Xcode 8.2, I experienced slow and lots of hangs .. I am working with many projects .. the solution that so far seems to solves all such issues was to "disable" git repository creation during project creation .. I did recreate all of my projects without "git" repository because first: I am not experienced in using such "git" version control, and second: cause I manage versioning myself.
Related
On OS 10.8.2 and using the latest Flash Builder 4.7 it seems I can't go for more than a few days before running into compile errors.
90% of the time these have something to do with my workspace becoming corrupt.
Simple to fix, BUT, a pain having to reapply ALL my settings, plugins etc every time I create a NEW workspace.
Can anyone suggest any way(s) of avoiding workspaces from becoming corrupt?
Great question, I really hope someone can answer it. In the meantime, I found a way to recover from crashes without needing to rebuild all the project configuration etc which is so tedious. This is on OSX 10.8.4, Flash Builder 4.5, hopefully it works for FB 4.7 too...
Ensure FB is closed
Move all the project files out of the {workspace_fb}.metadata/.plugins/org.eclipse.core.resources/.projects folder.
Start FB then close it again.
Move projects folders back in to the .projects folder.
Start FB.
Alright. This is utterly puzzling.
I am developing a game project with Xcode 4.1.
The project files are always with me in an USB stick, because I am constantly developing the project on many different Macs.
So I come to a workstation, paste a copy of the project in the USB stick to the desktop, and start working on that copy. When I am done developing, I delete the project in the USB stick, and then copy the one in the workstation's desktop back to the USB stick.
For some reason, my file GameData.h and GameData.m are not properly updated. But everything else in the project is. Basically, I made some edits to GameData, and when I got back home, I noticed that GameData is not the same as the one I was editing a while back. In fact, it only has code I wrote yesterday.
What could be wrong? Why is that file the only thing that never gets copied properly?
Check to make sure your GameData.m/.h files are where you think they are. Select one of them in the navigator tree, right click, select Show in Finder. Examine the file it points to - is it in the same directory as it's project peers, does it have correct (writable) permissions, is it an alias to another file, etc.?
Sometimes you can get into trouble (usually with libs) by adding them to the project, but not checking the box that says "copy into destination group's folder if necessary". In this case, XCode tries to find the file in that other directory (which may not be on all of your Mac machines) rather than the directory where all the other project files are.
I have noticed that occasionally xCode either fails to save a file or fails to rebuild after a file has been changed. It seems to happen on some projects and not others (I've noticed it mostly on a desktop app, but never on phone apps). I have no idea why this happens.
I have a project that has one target dependency. The target dependency is dependent on a framework called Three20.
The dependency tree looks like this.
myProject
-> myCustomFramework
-> Three20
When I tried to build and run I get the following error message.
Workspace Integrity Couldn't load Three20.xcodeproj because it is
already opened from another projet or workspace.
I have only one project open. Any suggestions on why I am getting this message?
Quitting the xcode completely and opening it up again worked.
Quitting Xcode alone didn't work for me. What I did was:
File->Close Workspace/Project on every open workspace.
Xcode->Quit
Open Xcode again and open troublesome workspace
I have close the Xcode completely but IT didn't work. I have killed the procces and It did finally!!!
:-)
Had the same problem in a case where I got a workspace working, closed it, copied the containing folder to a USB drive, then reopened. I got that message for one of the projects in the workspace. Closed, tried again, removed/re-added project - no luck. Closed, tried to open the project alone and got the message about it being open in another workspace - not true. Quit XCode, restarted by double-clicking my workspace in Finder, and all went well after.
I had same problem. Fixed after updating of cocoa pods with pod update command.
Restart the computer and try again opening the project :)
I updated to master and I'm not able to load new classes like
RKObjectMapping. I went through the install instructions again and reviewed
the example projects but still can't figure it out. Why wouldn't XCode know
about RKObjectMapping when I include ?
I had this problem as well.
From this thread on the RestKit group:
Close the project
Open Window->Organizer
Under Projects tab, delete DerivedData for your project
Quit Xcode and Relaunch
Open the project
Clean and rebuild
Everything should work.
I've found various proposed solutions to this problem on this internet, but none of them work for me. Does anyone know why this might be happening?
http://answers.unity3d.com/questions/15294/xcode-build-and-archive-error-no-such-file-or-directory
http://blog.joshschumacher.com/2011/04/06/xcode4-the-operation-couldn%E2%80%99t-be-completed-no-such-file-or-directory/
I've tried archiving with every combination of coding signing vs not using code signing, and I've tried using every combination of provisioning profiles, but I still get the same error every time.
I'm very confused as to why I'd even be getting an error like this when trying to save a file. I'm using XCode 4, my application builds for archive fine. In fact, I can even upload my application to itunesconnect (and it was accepted!). I just can't create an IPA for sharing and beta testing before submission.
Any ideas?
The error message
Right before I get the error
After much frustration, I filed a developer support request with Apple. The technician I spoke with was able to save my archive as an .ipa on her computer -- the exact same archive that I was not able to save on mine, which pointed to a possible bug in my system (and from the sounds of it, many other people's).
She recommended that I uninstall and reinstall XCode and the developer tools, and that worked!
Here were her uninstall instructions:
Make sure that your machine is running the latest Mac OS X (10.6.7) and iTunes.
Run the following command in the Terminal application to uninstall your SKD:
sudo <Xcode>/Library/uninstall-devtools --mode=all (where <Xcode> is the path to the directory that contains your SDK.)
Drag your <Xcode> to the trash and restart your machine
Re-download and install Xcode (4.0.2) from the iOS Dev Center. Make sure that the System Tools, UNIX Development, Essentials packages in the Custom Install pane are selected before installing it.
I have the same issue after my distribution certificate was expired. I add new ones (private key and certificate) and xCode "Share" command starts to produce such error.
The problem resolves as soon as I remove old private key & certificate from Keychain Access.
Hope it helps
Selecting "Don't Re-sign" at Identity solved the same issue for me.
I actually had the same problem, but a different solution (and reason). I had Xcode 3 and Xcode 4 both running at one point. I recently deleted Xcode 3 and moved my Xcode 4 from /Xcode4 to /Developer directory. This caused me to have the same issue you describe.
I moved the directory back to /Xcode4 and now my archives save out correctly.
I also had the same problem but I could resolve the problem in the below way.
My project was on the portable disk (formatted as FAT-32) and the project referred some folders on the same disk as "add folder reference for any added folder". I could build it any configurations however I couldn't just make .ipa file with above alert.
So, I copied the referenced folders on the portable disk to the desktop of the disk installed XCode (MacOS). And adding again the folders into the project. I could make .ipa file.
I installed Xcode 4.0.2 in one directory and then manually moved it to another.
When I moved Xcode back to the first directory everything worked.