Error while build project Xcode says : "you don't have permission"

Question

I have downloaded one project from the internet and, when I am trying to run it/build it the XCode, XCode says :

The file “PROJECT NAME” couldn’t be opened because you don’t have permission to view it.

I have also put read/write permission to the project folder as well but still not working.

Why does this is happen? Please help me to resolve this issue

Possible duplicate of ["The file "MyApp.app" couldn't be opened because you don't have permission to view it" when running app in Xcode 6 Beta 4](https://stackoverflow.com/questions/24924809/the-file-myapp-app-couldnt-be-opened-because-you-dont-have-permission-to-vi) — Senseful, Apr 24 '18 at 04:29
Refer to this [answer](https://stackoverflow.com/a/50167291/6521116) with a good summary of this issue. — LF00, May 04 '18 at 05:20

score 61 · Accepted Answer · edited Sep 25 '18 at 15:10

61

Go up to the folder containing the project in your Finder.

Right Click > Get Info

Go to the bottom of the Info pane, and click the little lock, type in your password when prompted.

Then, change permissions for yourself to read+write.

Click the little gear below, and apply to all enclosed items.

Close the lock once you are finished!

If this doesn't work, Change the value of "Compiler for C/C++/Objective-C" to "Default Compiler (Apple Clang)" under the Build Settings of your target.

edited Sep 25 '18 at 15:10

Oleh Veheria

412
5
13

answered Dec 08 '14 at 10:08

Michael Voznesensky

1,612
12
15

8

I have followed your steps but it is not working may be some different problem. – jogshardik Dec 08 '14 at 10:12
1

I don't know the actual what problem is there but there is so many solutions below all solutions are right because i have tested that but i think your answer include most of the solutions. – jogshardik Apr 13 '15 at 06:24
Changing the permissions for me didn't solve it, I already had the correct permissions. But changing the compiler did it! Thx – Alex Cio May 13 '15 at 13:00
3

I have tried both the option but it does not worked for me..please help – Ankit Kr.Vishwakarma Dec 16 '16 at 06:36
This work for me ... But you need to clean and build your project – Alwin Oct 19 '17 at 05:48
I had to restart, as simple as that since both scenarios mentioned above were already there – manman Nov 17 '17 at 17:22

score 27 · Answer 2 · answered Jan 02 '15 at 17:45

27

The project i have download from the internet don't have the Executable file in info.plist which should be there and its value should be this ${EXECUTABLE_NAME}. Instead of this value it consist some different value. So i have changed it ${EXECUTABLE_NAME} this value then clean->build->run successfully.

answered Jan 02 '15 at 17:45

jogshardik

1,446
1
12
23

1

Thanks for this one, it helped me after I duplicated a project. My executable file name was still the old app name. – JohnnyC Oct 14 '15 at 22:41
I had changed the info.plist file the earlier file didn't have the ${EXECUTABLE_NAME} set! Thanks a lot this worked for me – Mudit Jaju Aug 31 '16 at 17:52
2

This worked. Hey, Apple, would it be so hard to use an "if" statement to make the error say "I can't run your program because the name of your target doesn't match the name in your info.plist?" – M Katz Nov 05 '16 at 03:09
Perfect! Working for me. – Govaadiyo Jul 28 '17 at 12:01
Thanks a lot, this worked. I would add that the build system creates executable file named .app, and if you change in Info.plist, the system just won't find the executable. Can't believe Apple still didn't fixed it. – Borzh Nov 17 '18 at 01:26

score 20 · Answer 3 · answered May 01 '17 at 06:18

20

None of the answers helped me. Although the build was successful i got the error while trying to run the project. Accidentally while cloning the project, there were no files under the Build Phases -> Compile Sources.This might have happened while working on a team in git.

Files under compile sources may be the entry point to be able to build/run the project.

Once i added the AppDelegate & ViewController file in compile sources i was able to run the project without any error.

answered May 01 '17 at 06:18

LC 웃

18,888
9
57
72

Thank you, this helped me. How can we ensure these compile sources and copy bundle resources references are saved to the remote repository so when we clone the project it works normally? – Roman Samoilenko Feb 05 '18 at 11:41

score 15 · Answer 4 · answered Dec 08 '14 at 10:19

15

Take your Projects build Setting

In Architecture section make sure that Architectures and Valid Architectures are the same. If any extra Architecture is present in Valid Architecture section please remove it and then try building the code, It will work. Here in the image edit the section marked as red.

answered Dec 08 '14 at 10:19

Sudhin Davis

2,010
13
18

Thanks for answering i have follow your steps the application build successfully but still issue are there. – jogshardik Dec 08 '14 at 10:35
3

Have you cleaned your project after doing this? do ctrl+shift+k – Sudhin Davis Dec 08 '14 at 10:38
Yes i have clean my project and then build it again. – jogshardik Dec 08 '14 at 10:40
I have resolved the issue thanks everyone for helping – jogshardik Dec 09 '14 at 04:59
Please share your solution. – Sudhin Davis Dec 09 '14 at 05:09
3

The project i have download from the internet don't have the executable file in info.plist which should be there and its value should be this ${EXECUTABLE_NAME}. Instead of this value it consist some different value. So i have changed it ${EXECUTABLE_NAME} this value then clean->build->run successfully. – jogshardik Dec 09 '14 at 05:20

score 11 · Answer 5 · answered Feb 10 '15 at 13:23

11

I had similar issue ad problem was there was an info.plist file in one of the folder in framework that i downloaded from GitHub , deleting it fixed the issue

answered Feb 10 '15 at 13:23

vishal dharankar

7,536
7
57
93

score 9 · Answer 6 · answered Mar 20 '15 at 16:42

9

I had the same problem. In my case, it caused from I try change display name's app from default to another by edit "Executable file" in Info.plit then compile, it will show this error. So I edit value property "Executable file" as default then edit value property "Bundle name" instead.

enter image description here

answered Mar 20 '15 at 16:42

Kakashi

534
11
16

Thanks for this one, it helped me after I duplicated a project. My executable file name was still the old app name. – JohnnyC Oct 14 '15 at 22:41

score 7 · Answer 7 · answered Feb 25 '15 at 07:02

I had the same error message wit ha project with Xcode 6.1.1.

What I did to resolve it was the following:

in Build settings, "Architectures" section: set "Architectures" (ARCHS) to "Standard architectures (armv7, arm64)" for your target and/or project as needed.
in Build settings, "Build Options" section: set GCC_VERSION to "Default Compiler (Apple LLVM 6.0)" for project

I was able to launch and test the project with theses settings.

score 7 · Answer 8 · answered Jul 06 '17 at 16:19

7

Clean the project inside Xcode.

Go to Product -> Clean

That worked for me.

answered Jul 06 '17 at 16:19

Manuel BM

868
1
13
17

score 5 · Answer 9 · answered Jun 13 '15 at 22:21

5

Select TARGETS -> General -> Identity -> Version (should be 1.0 or whatever version you want).

answered Jun 13 '15 at 22:21

Dorald

724
7
12

score 5 · Answer 10 · answered Apr 01 '16 at 12:38

5

Doing a Product -> Clean and deleting derived data then rebuilt project worked for me.

The story is that I had 2 projects opened at same time. I've deployed first project on my device and after a while I was trying to deploy second one (initially stopped running first application), then got this ugly error message.

answered Apr 01 '16 at 12:38

nsinvocation

7,559
3
41
46

Actually, this solved my problem right now. It happened in the middle of my work when I edited info.plist file. Strange... – Dimmy3 Jul 22 '16 at 20:10
It solves my problem - but need to do it every few builds. – UKDataGeek Jan 08 '17 at 23:20

score 4 · Answer 11 · answered Apr 01 '15 at 12:51

Just figured out it can be another problem. It can happen that your Main.m file isn't included anymore in the Build Phases -> compile sources. You'll get the same error. You can just re-add it by clicking the plus and selecting the file from the dialog.

NewStackUser · Answer 12 · 2014-12-08T10:26:36.683

2

Check if Xcode version that you are using is up to date to open the source code. Also check if you have third party libraries, included in it. Check if deployment target, build target etc are up to date in the project settings.

edited Dec 08 '14 at 10:26

answered Dec 08 '14 at 10:03

NewStackUser

657
5
17

Try to change code signing Identity to "Don't code sign" in project settings. – NewStackUser Dec 08 '14 at 12:07

score 2 · Answer 13 · answered Mar 22 '17 at 12:36

2

Some how my project's Info.plist was missing See Below:

Before:

After:

I have drag and drop the info.plist file path and it worked for me.. :)

answered Mar 22 '17 at 12:36

Dheeraj D

4,386
4
20
34

score 2 · Answer 14 · answered Oct 03 '17 at 13:42

2

I have same issue. The problem is with project target membership was removed when I dragged and drop files externally.

I added Target membership for it and its working fine for me.

answered Oct 03 '17 at 13:42

mrunal thanki

753
6
16

score 1 · Answer 15 · answered Apr 21 '17 at 04:54

I've had same this error in Xcode 8.2. The reason I found out for me, I've included Info.plist from outside project folder (manually copy).

So that Xcode is getting confused for select correct Info.plist.

I just removed that Info.plist from the added library.

Then it is working fine without any permission alert.

score 1 · Answer 16 · answered Jan 03 '19 at 22:50

1

I deleted a folder that had some header files and plist files from a project I dragged and dropped from. This solved the problem for me. I hope it helps you.

answered Jan 03 '19 at 22:50

uplearned.com

3,393
5
44
59

score 1 · Answer 17 · answered Mar 16 '21 at 07:22

I got same problem, when running objective c project in Xcode 12.4 & macOS Big Sur. My screen shot as below.

solution as below:

Add "VALID_ARCHS" value "arm64 arm64e armv7 armv7s x86_64" screen shot as below

Change "Build System" to "New Build System" using below steps:

Open xcode project
Open File -> Project Settings -> Per-User Project Settings: -> Build System: -> "New Build System" -> Done

Add "Excluded Architectures" as "arm64"

score 0 · Answer 18 · answered May 09 '16 at 09:39

I had similar issues with Xcode 7.3:

The file “FirstSteps.temp_caseinsensitive_rename” couldn’t be opened because you don’t have permission to view it.

In my case the solution was to change the Product Name in the Packaging section of the Build Settings:

from "FirstSteps.temp_caseinsensitive_rename" to "FirstSteps"

screenshot

score 0 · Answer 19 · answered Nov 19 '16 at 23:37

I had the same issue but a different cause; answering here for anyone who gets stuck like me in the future.

In my case the issue was that my Xcode project contained no source code directly. All the code, including main(), was being pulled in from an externally-built static library. The solution was to add an empty dummy.cpp file to the project.

Casper · Answer 20 · 2019-03-20T11:06:05.303

In my case, the cause for this error was different. I had, for some reason removed my AppDelegate's Target Membership from the Application Target. I din't realise that it caused the issue for a long time coz it did work briefly even after I had removed the Target Membership, but later stopped working.

So, make sure you have your AppDelegate set for your Application Target.

@UIApplicationMain // <- THIS
class AppDelegate: UIResponder, UIApplicationDelegate {

}

score 0 · Answer 21 · answered Jan 26 '18 at 16:05

0

In my case : xcode menu - product- clean and then build fix the problem.

I imported framework project into another project for some reason I got this error also.

answered Jan 26 '18 at 16:05

user1105951

2,259
2
34
55

score 0 · Answer 22 · answered Apr 19 '18 at 02:47

0

I just Cleaned the project and it worked perfectly.

go to "product" and press "clean"

answered Apr 19 '18 at 02:47

M.E

11
1

score 0 · Answer 23 · answered Oct 04 '18 at 17:58

0

Ok, so if any other person facing the same issue on XCode 10, I have fixed it by goin to File->Workspace settings->Build System I made it Legacy build system and it worked!

answered Oct 04 '18 at 17:58

Mostafa

1,522
2
18
34

in XCode 10 there is no `Workspace Settings` but `Project Settings`. I tried with it as well but issue is still there. – Vaibhav Saran Feb 23 '19 at 08:30

score 0 · Answer 24 · answered Mar 08 '19 at 06:26

0

LC 웃 is right on my case. Have deleted the Build Phases -> Copy Bundle Resources build phase which leads this issue. And, adding it back fixed this issue. Also make sure files are present in the build phase.

answered Mar 08 '19 at 06:26

Praveenkumar

24,084
23
95
173

score 0 · Answer 25 · answered Nov 28 '19 at 17:11

In my case I have Xcode 10.1 & 11 installed to my machine. Not sure whether this will create a problem like this.

I tried all this tips. But didn't solve my issue. Then I tried, manually deleted all files which throws this error and then added it again manually.

Which worked perfectly for me.

score -1 · Answer 26 · answered Nov 17 '19 at 05:03

-1

I had the similar issue upon updating my macOS and Xcode (Xcode Version 11.2.1 & Swift 5 ), tried most of the solutions above, but did not seem to work.

However i deleted Xcode and reinstalled it - seems to have resolve the issue.

answered Nov 17 '19 at 05:03

Kunal Parikh

19
1

Error while build project Xcode says : "you don't have permission"

26 Answers26

Linked