Tell me more ×
Ask Different is a question and answer site for power users of Apple hardware and software. It's 100% free, no registration required.
up vote 2 down vote favorite
1

I'm trying XCode4. I created a new project, told XCode to put in my ~/develop/ directory, but then I immediately get asked:

“Test project” is locked for editing and you may not be able to save your changes. Do you want to unlock it?

“Test project” is currently locked because you do not own the parent folder and have no write permissions for it.

[Don't Unlock] [Unlock]

...which isn't true: my ~/develop/ folder is owned by me (staff group) and has drwxr-xr-x permissions. I write to it every day. XCode is running as my account.

Is XCode right? What can I do to fix this? If I press “Don't Unlock” it seems to work fine.

share|improve this question
Have you tried pressing "Unlock"? What does it do? Also: is the file/folder locked in the Finder? Can you unlock it there? – CajunLuke Jul 16 '11 at 19:01
What does ls -led ~/develop/ - show - the extra information is the ACL for the directory – Mark Jul 5 '12 at 23:15

3 Answers

up vote 1 down vote

Launch Finder and right click on your folder and go to Get Info. After this process you can change the permission.

If you like Terminal for this job, this topic on StackOverflow will help you.

share|improve this answer
up vote 0 down vote

If you navigate to that folder from Finder, you can click Get Info and manage the permissions from the bottom of the window. You can navigate there by using the Go To Folder menu item in Finder or directly navigating their.

share|improve this answer
up vote -1 down vote

After changing my home directory name Xcode gave the same warning on a project I was working on. The work around I used was to create a duplicate of the project.

share|improve this answer
1  
Hello, and welcome to Ask Different! This site tries to be the definitive Q&A reference to all things Apple. For this to work, it is important to stick to the exact question when answering. In this case, while your workaround is a good hint, you fail to address any aspect of the question related to the cause of the behaviour, which makes the value of your solution questionable. If you can’t provide any insight into that, your suggestion would be more adequate as a comment to the original question than as an answer. Thanks for pitching in, and enjoy the site! – kopischke Nov 4 '12 at 21:45

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.