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.
Related
I use AnyLogic PLE v8.76 on mac. It worked fine for a week, but today I got problem launching the software. I keep getting this message:
And this is the error shown:
I tried to download Anylogic again, but I still got the same problem...
I did not download any other softwares or change things on my mac.
Can somebody help me?
Thank you!
Best option, as often advised by the AnyLogic support team, is to clear the workspace.
Try the following:
Make hidden files and folders visible on your Mac - cmd+shit+.
Navigate to your user folder (Either from he side bar, or Macintosh HD -> Users->(yourname)
Find the .AnyLogic... folder, on mine it is called .AnyLogicProffesional
Delete the following two folders workspace8.x and configuiration8.x where the 8.x indicates your version number of the currently installed AnyLogic version.
These files keep settings and the currently loaded models on the disk and will remain even if you download a new version of AnyLogic, which is why downloading a new version does not always solve these kinds of problems.
If the issue still persists contact support, they might ask you to send the error report you got from your Mac (so copy and paste it to a document the next time you get it) as well as some error logs that get stored in these hidden files and folders. (Now you at least know where to find them ;-) )
If my solution did not provide the answer, please add an answer if you manage to find it.
Suddenly I'm getting an odd error popping up every few minutes.
'Periodic workspace save.' has encountered a problem.
Could not write workspace metadata '{workspace}.metadata.plugins\org.eclipse.core.resources.snap'.
I've checked and the file is there. It's not marked "read-only".
Nothing's changed recently. I am on a Citrix VM running Windows 7 and my workspace is on a mapped drive. However, this setup has been running fine for over a year.
Any ideas?
I ended up creating a new workspace and moving my projects over there. Fortunately there weren't many (nor did I have too many snippets) and I could recustomize the way I wanted.
This is not a very good solution, however, and I'd love to see a better way to fix this issue.
Im finding myself using TextMate 2 more and more for development these days
One thing that is bugging me is that it does not seem to reload a file when it is changed externally.
This is a big problem since I use terminal to switch git branches a lot, and it often results in accidentally saving an older version over the new branch
Sadly the TM team seem to have disabled the Issue tracker on github, and documentation just seems scattered far and wide over the web in tiny scraps.
Any ideas?
Right now it reloads the file silently whenever the file on Disk is changed. There is currently no option for a prompt.
Regarding the closed issue tracker: As an alternative, you can always send a mail to the Textmate users list if you find a problem.
I just updated to TM 2. In the past, I have enjoyed using TM to view development.log as I am introducing new or modified code. TM 1 would ask me if I want to revert to what's on disk and of course I would respond with Yes. Then I could see any additions to the log file. Occasionally I would empty the log file with Cmd+A, Delete, Cmd+S. Macromates, please make TM 2 work like TM 1 reloading content.
I also could not find a solution to this problem which is still there, however it is possible to file an issue using this contact page: http://macromates.com/support
Additionally there are hidden setting which cannot be set from the GUI. Unfortunately they don't include and setting for automatic load from disk: https://github.com/textmate/textmate/wiki/Hidden-Settings
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 suddenly can't save any files in any of my Xcode projects in my home directory. Not sure what caused this. Here's the error I'm receiving:
I don't think Xcode is correct, since I am the owner of -- and have read+write permissions on -- the affected files.
A few other fun facts:
I can edit these files in other applications as the same user, so the problem seems to be specific to Xcode.
Other users can create and edit projects in their home directory without issue.
Running Xcode as root (via sudo /Developer/Applications/Xcode.app/Contents/MacOS/Xcode) does allow me to edit these files.
chown, chmod -R 755, etc. on the directory containing my projects doesn't help.
Disk Utility > Repair Permissions doesn't help.
Reinstalling Xcode, clearing Xcode .plists, etc. doesn't help. Failing both on Xcode 4.1 and 4.2.
Thoughts? Hopefully I'm just missing something simple.
I've just run into this issue myself. No amount of rebooting fixed it for me. In fact, it only began after a reboot. After much frustration, I used fs_usage to observer the file system calls that Xcode and any other processes were making when I attempted to save.
The results were interesting. In particular, one of the last things I saw before Xcode loaded NSAlertPanel.nib (which I assume is the UI for the error sheet), thing showed up:
revisiond.3029 getattrlist /private/var/folders/9f/_7xjwv310nb6c7yr6py_9jtc0000gn/T/TemporaryItems
Xcode.2437 mkdir /private/var/folders/9f/_7xjwv310nb6c7yr6py_9jtc0000gn/T/TemporaryItems/(A Document Being Saved By Xcode)
This looked highly suspect to me, so I investigated this directory. It turns out that
"/private/var/folders/9f/_7xjwv310nb6c7yr6py_9jtc0000gn/T/TemporaryItems" was owned by root:staff, and NOT writable by the group. Making this directory writable by the group fixed the issue for me immediately.
So, it appears this was a bad iteration between Xcode and revisiond, which is responsible for the File Coordination features in Lion. I do not know why this problem persisted for me when a reboot fixed it for others.
Check how you have this setup in source control. I've noticed with the new Xcode that if you have this under source control (svn) that that might be blocking your ability to write over the file regardless of permissions.
You may want to do an svn cleanup
from terminal issue a
ls -laE#"
There may be extended attributes or ACL (Access Control List) permissions problems. I have had that happen. It can be really bad if it has inherited attributes
If that is the case fix with
chmod -R -N
Be careful!
Looks like I had netbiosd blocked in my firewall configuration. After unblocking it and restarting my computer, the issue seems to be resolved.
I spent about two hours with this same problem. I tried all of the above. Finally, I rebooted my machine. Everything works fine after the reboot.
Everything was working fine and i ran into this issue. I tried most of the above suggestion. Finally,the MacOSX software update resolved the issue.