I tried to install some Pods into my Project.
I kept getting the error message:
The document "S&J.xcworkspace" could not be opened.
The issue was that my Project name contained the &. I created a new project with a different name (without the &) and everything worked fine.
Hope this helps someone.
Thanks.. This actually helped, spend several hours figuring out why my .xcworkspace wasn't opening, only to read your post and found that was making the same mistake of having & in my file name... Changed the name and boom, like magic, app running like a champ.. :)
Related
while I'm doing my spring project, I got this error message
**log4j:ERROR Could not parse url [file:/Users/gim/내폴더/Workspaces/Workspace_final/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/fogams/WEB-INF/classes/log4j.xml].**
so I immediately changed the directory which was named to Korean.
(and it made me to lose all the Workspace that I was working on..so foolish.
but I've re-built it through gitHub)
and now my Workspace directory is
/Users/gim/myfolder/Workspaces/Workspace_final/
but I still get the same exact error.
so I've tried cleaning server, updating maven project...and never worked.
please help me to find the problem.. thanks
Wich IDE are you using?! For intellij, you'll need to download sources and reload your project
It was kind of mac system error. when I searched,
people said I need to switch the system country, and then
switch it back to my country.
so I did that and re-opened the Eclipse and it worked!
Since updated my mac to OSX10.12, I have got this error:
And I must clean, otherwise the build will fail.
I have googled a lot, but did not found useful solution.
I am wondering about the .pcm files.
hope some person could help. Thanks.
I got this issue once. Here are the steps of what worked for me:-
Getting the path for the derived data folder in Finder from Xcode.
closing Xcode
deleting the derived data folder from finder
emptying Trash
Reopening Xcode
Cleaning and building again.
Hope this helps you as well...
Hi my Xcode project at some point yesterday started failing to build with the error:
Compilation failed for data model at path
'/Users/cooldocman/Library/Developer/Xcode/DerivedData/cooldocs-ejjarvdamwdcbbcpahhnbweztrmh/Build/Products/Debug-iphonesimulator/cooldocs.app/cooldocs.momd/cooldocs.mom'
I did research on StackOverflow and other sites - and none of the suggested fixes to similar sounding issues have worked for me. The issue appears to be at the intersection of SVN, Xcode, Core Data and XCUserState, and I have tried a number of steps from info I found on StackOverflow and other sites, but still have not solved this.
Here's what I have tried so far:
One stackoverflow article recommended to clean out the SImulator applications folder:
So I removed apps from under /Users/cooldocman/Library/Application Support/iPhone Simulator/5.1/Applications
... the error persisted ...
Another stackoverflow thread advised to remove the temp DerivedData folder.
So I removed all folders under
/Users/cooldocman/Library/Developer/Xcode/DerivedData
(the folders in the error message i.e. /Users/cooldocman/Library/Developer/Xcode/DerivedData/cooldocs-ejjarvdamwdcbbcpahhnbweztrmhwere
therefore were deleted)
Another article said to remove the contents of the Archives folder ...
/Users/cooldocman/Library/Developer/Xcode/Archives
Still no luck even after steps 2 and 3
Even after all the cleanup, I still see when I grep contents of my project that a reference still exists to the old "cooldocs-ejjarvdamwdcbbcpahhnbweztrmh" folder...
$ grep ejjarvdamwdcbbcpahhn //*///*
Binary file trunk/cooldocs.xcodeproj/project.xcworkspace/xcuserdata/cooldocman.xcuserdatad/UserInterfaceState.xcuserstate matches
Now how do I clean this up?
PERHAPS THE SECRET I NEED IS HOW TO CLEAN UP THIS LEFTOVER xcuserdata and hopefully that will resolve the issue - or otherwise, to use a treasure hunt analogy, it may at least open the door to another mysterious tunnel that needs to be crawled down! (and when I come out of that final cave is when I can start the actual work on what I really need to do!)
Thanks for reading and appreciate any help and insights from this group!
:-)
Regarding to xcuserdatad folder, Why not just close your Xcode and delete it in Finder or Terminal? It's safe to do that. Next time you open the project with Xcode, It will recreate it for you .
I had this same issue and none of the suggestions worked. I finally deleted the entire directory which had my project and cloned it again from Github and it fixed the issue. It's possible that some file that was git ignored wasn't getting reverted, but I didn't have time to find out which file it was.
Indexing, code completion, & coloring disappear from my projects on a fairly regular basis, usually right after I add a file. And then it returns hours or days later, usually for unknown reasons (I've tried keeping a record but it's pretty random). CMD-clicking on even known terms (like viewDidLoad: or NSLocalizedString) result in a "Symbol Not Found" error.
It happens with Xcode 4.2 (I believe it happened in Xcode 4.0.2, but not as frequent).
I have no build errors, warnings, or static analysis messages.
I've restarted Xcode.
I've tried turning precompile off.
I don't have a case where I've got a circular header file include/import.
It happens if I use gcc, LLVM, CLang (in whatever combo).
It happens if I use iOS 4.3 or 5.0.
I've tried deleting the "derived data.", and even only the Index/ path.
After deletion & re-build I see the .hmap file & .xcindex folder (filled with db.xcodeindexdb* files).
...but I can't get code-completion, symbol detection, or coloring back.
What else can I do? I sincerely appreciate the help.
Have you tried a clean install (sudo /Developer/Library/uninstall-devtools)?
I have exactly the same problem for one particular project. Following workaround works for me: apart from deleting Derived Data , I make an SVN update or revert any file of the project. If the project file itself is changed my Xcode displays wrong target ,so I close the project and re-open it and then indexing starts properly.
The most reliable way I've found to force re-indexing of the project is to change the build settings, specifically 'Run Static Analyzer' - I wish I had a real answer though.
This might seem like a silly response, but have you tried to repair file permissions under disk maintenance?
Your thread is old, but anyway...
Deleting the derived data folder helps me everytime. I have to do it quite regularly, which is very annoying. Your find the path in the xCode-Settings(cmd+,) in the locations-tab.
I just had this issue. What worked for me is clearing the derived data, then closing the project and re-opening it. It didn't reindex until I closed and re-opened the project. The project never compiled fully, so it didn't even have to finish building to work.
I am on Mac OS X 10.6.8 using Xcode 4 with Cocos2D.
The other day, I got an error message out of the blue when trying to run my project:
The document "MainMenuScene.m" could not be saved.
I tried the following, none of which has worked:
replacing the file
creating a new one and renaming it (which I could not rename it. I was told I didn't have permission)
creating a whole new project and reading the files/copy pasting the code in
opening Disk Utilities and running Repair Risk Permissions (which works again once, but then reverts back).
I sometimes get the off chance and the file does save, but reverts back to not saving again.
Anyone have any ideas on what I can do to fix this?
I had this issue with a project on an external ssd. Disconnecting the ssd and reconnecting fixed it for me.
In short:
Have you tried turning it off and on again?
See the full conversation in the comments, but this ended up being solved. Moving what was suggested/asked here for clarity and closure.
Is that the full error? Also, are you saving it on a USB or your HD?
Are you an admin on your computer, etc? Have you tried to move the project completely, or copy and try to work on it from somewhere else? With the currently given information I cant think of anything that would cause that kind of problem. What has changed since you were last able to edit and save without issues?
Glad we got it figured out!
-Karoly
Have you tried just moving the file? That'll probably do it.