finderiosmacbook propermissionxcode
When i try to open a specific project in xcode (i can open my other projects just not the most important one) i get this error
I have gone in "Get Info" and made sure my account had complete access, but i still get this stupid error and i have no idea why. I am also the administrator for my computer and logged into my only account for this computer (i have not made multiple accounts) Can someone please help.
– Thanks
Using sudo on the open command doesn't do anything particularly useful -- the actual program still gets run under the user's regular identity. To solve this, make sure TextEdit isn't running, then do:
sudo /Applications/TextEdit.app/Contents/MacOS/TextEdit &
open -a "TextEdit" /etc/sshd_config
The first command runs TextEdit as root; the second tells it to open the file. After this, you should be able to edit & save changes. When you're done, be sure to quit TextEdit (or it'll keep editing files as root).
Alternately, use TextWrangler (or its even-more-capable-but-not-free sibling, BBEdit). It handles saving files as root automatically, as well as having easy ways to edit invisible files. I much prefer it for editing config files and the like.
EDIT: Be sure to get the version of TextWrangler from the Bare Bones Software web site, not the version from the Mac App Store -- the App Store version has the save-as-root feature removed to comply with Apple's rules.
The problem is that Xcode 4.3 ignores the schema you had selected in older versions, and automatically sets it to run on device for iOS projects. Since you don't have an eligible device attached to your computer, you get this error. The fix is simple. In the toolbar, click on the menu which says iOS Device and choose one of the simulator options instead.
Best Answer
Open terminal and type
NOTE: the capital R in the command above. Obviously change the path to your project folder to what it actually is.
If that command works without error, but you still cannot open the project, then it isn't in fact a permissions problem but another bug in XCode.
You're not the first person to report this error however. Hopefully the above sorts it out for you. Let me know.