The file ".app" couldn’t be opened because you don’t have permission to view it

Question

I get the following warning when I try to run my app:

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

I have looked through all the previous questions I could find and can't find an answer.

I have tried:

Replacing my info.plist
Deleting Derived Data
Duplicating my app
Editing the permission on the folder of the project
Changing "Compiler for C/C++/Objective-C" to Default in Build Settings
Checking my architectures
Cleaning My Project

Thanks for your help!

Update: I can not run it in simulator or on my phone.

Yes, I have not tired it on a phone because I have to get a cord. — jbokwx, Dec 25 '14 at 21:47
@user3424395 - usually the first step is to completely clean a project. Start with cleaning the project. Then close the project and clean the derived data caches. Also see [After duplicating a target in xcode 6 and building with iOS8 sdk unable to install / open it](http://stackoverflow.com/q/26219300/608639). It seems to be the exact problem. — jww, Dec 26 '14 at 03:18
Try :Build settings->Product Name-> Change the product name,default is `$(TARGET_NAME)`, and rebuild. — Zigii Wong, Dec 26 '14 at 03:19
This one did the trick for me: http://stackoverflow.com/questions/24924809/the-file-myapp-app-couldnt-be-opened-because-you-dont-have-permission-to-vi — Sjakelien, Apr 12 '15 at 09:59
I did not figure it out, and have not found a solution that works. I plan on scraping the app and moving to a new idea for a similar app under a new wame. — jbokwx, Apr 25 '15 at 21:50
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:30
Refer to this [answer](https://stackoverflow.com/a/50167291/6521116) with a good summary of this issue. — LF00, May 04 '18 at 05:22

score 21 · Answer 1 · edited Feb 23 '19 at 09:29

21

select info

Enter Bundle name As : ${PRODUCT_NAME}

Executable file : ${EXECUTABLE_NAME}

edited Feb 23 '19 at 09:29

Vaibhav Saran

12,848
3
65
75

answered Apr 07 '15 at 09:49

Gulzaman

429
3
11

score 10 · Answer 2 · answered Sep 12 '15 at 01:09

10

I also saw this occur when some of the items of source code were not included in the Target Membership for this particular target. It compiles just fine either way, but it won't run unless you check the boxes for Target Membership in the File Inspector. The error given is the same lack of permissions message above.

answered Sep 12 '15 at 01:09

Aku

844
9
16

1

My gosh, @Aku, this lonely little no-votes answer was the key to all my problems. The solutions that worked for other people never worked for me. But this did! Thanks for throwing it out there. You've got my vote. – Le Mot Juiced Nov 17 '15 at 04:22
I just ran in to this issue too with this being the cause, thank you! – Rajveer Jan 13 '16 at 10:28
@Aku you are my savior. Now if only there was a Jack that would tell me which files to include in the target in question... – tadelv Nov 04 '19 at 09:04

score 4 · Answer 3 · edited May 23 '17 at 12:17

4

Go into your build settings change Compiler for C/C++/Objective-C to Default compiler (Apple LLVM 6.0) instead of Unsupported Compiler(com.apple.compilers.llvmgcc42) for project.

You can refer this question "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

edited May 23 '17 at 12:17

Community

1
1

answered Apr 01 '15 at 06:20

Tarun Seera

4,212
4
27
41

score 1 · Answer 4 · answered Jul 08 '18 at 08:30

1

reinstalling pods worked for me my mistake was : i used update to recommended settings warning and by default xcode update my pods but it doesnt updatet my podfile so just using 'pod install' worked for me

answered Jul 08 '18 at 08:30

Mr.Zee

125
1
9

score 0 · Answer 5 · answered Apr 05 '16 at 14:23

On XCode 7.3 I got the same issue

Mistake I did

I just Added physical folders and moved my files into them, problem started.

I also tried everything

Default compiler
Clean and build
Reset simulator and reboot simulator, Xcode, iPhone even mac
Updated Info.plist
Deleting Derived Data
Editing the permission on the folder of the project
Checking my architectures

nothing worked :(

How I resolved

I just deleted those physical folders, clean build and YESS!! It works!!

score 0 · Answer 6 · answered Jan 30 '17 at 14:52

I encountered the same problem after I inadvertently removed a folder from the XCode project that contained several required files. Oddly, that folder contained both the LaunchScreen and Main storyboards, as well as the project's custom (and only) AppDelegate... yet I was able to build the project without error, and the only error presented when I clicked "Run" was the "you don't have permission" dialog box, not a runtime error complaining of missing files/references/dependencies.

Moral of the story: In addition to all of the other troubleshooting suggestions above, make sure your project contains all of the folders and files that it depends on.

LF00 · Answer 7 · 2018-05-04T05:14:32.023

I usually do it by one of the below ways.

project.pbxproj: checkout the workable project.pbxproj file.
Build Options: set Compiler for C/C++/Objective-C to default compiler.
Executable file: set to $(EXECUTABLE_NAME) or directly set to your app name.
Build > Clean:just do a clean.
Replace the Info.plist with a new file from a new project
Duplicate Info.plist in the project: just remove the extra one.
Derived Data.: Find the Derived data path by Xcode->preference->locations->Derived data, then delete it with rm -r /Users/roofe/Library/Developer/Xcode/DerivedData
And there may other reasons, you can refer to “The file ”MyApp.app“ couldn't be opened because you don't have permission to view it”

score 0 · Answer 8 · answered Apr 09 '18 at 06:36

0

Deleting Derived data from, Xcode > Preferences > Location and rebuilding the project did the trick for me.

answered Apr 09 '18 at 06:36

akaMahesh

383
2
9

score 0 · Answer 9 · answered May 19 '19 at 20:51

0

I tried various way listed here in the answers, not worked.

Finally I did following and it worked on Xcode 10.1:

Build settings->Product Name-> Changed the product name

The default is $(TARGET_NAME), and rebuild.

answered May 19 '19 at 20:51

Rizwan

3,324
3
17
38

score 0 · Answer 10 · answered Oct 26 '20 at 19:55

0

Choose Legacy Build System Solved my problem

File -> Workspace Settings -> Build System: Legacy Build System

answered Oct 26 '20 at 19:55

Muhammad Numan

23,222
6
63
80

This solution is never a proper solution do not switch this option unless you have tried everything else before... – Olympiloutre Jan 13 '21 at 13:30

score 0 · Answer 11 · answered Nov 29 '20 at 11:05

in my case, this issue happened after I added files (a folder) to my project via "Add Files to PROJECTNAME...". To fix this I had to make sure that the files are added to the right target, which is selectable at the bottom of the window, in which window you choose the files/folder to be added.

score 0 · Answer 12 · answered Dec 12 '20 at 08:24

For Ionic / Ionic (Capacitor)

Change -> CDVCamera.m

(CDVPluginResult*)resultForVideo:(NSDictionary*)info
{
   NSString* moviePath = [[info objectForKey:UIImagePickerControllerMediaURL] absoluteString];
   return [CDVPluginResult resultWithStatus:CDVCommandStatus_OK messageAsString:filePath];
}

to This

(CDVPluginResult*)resultForVideo:(NSDictionary*)info
{
    NSString* moviePath = [[info objectForKey:UIImagePickerControllerMediaURL] path];

    NSArray* spliteArray = [moviePath componentsSeparatedByString: @"/"];
    NSString* lastString = [spliteArray lastObject];
    NSError *error;
    NSFileManager *fileManager = [NSFileManager defaultManager];
    NSString *documentsDirectory = [NSHomeDirectory() stringByAppendingPathComponent:@"tmp"];
    NSString *filePath = [documentsDirectory stringByAppendingPathComponent:lastString];
   [fileManager copyItemAtPath:moviePath toPath:filePath error:&error];

   return [CDVPluginResult resultWithStatus:CDVCommandStatus_OK messageAsString:filePath];
 }

The file ".app" couldn’t be opened because you don’t have permission to view it

12 Answers12

Linked