"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

Question

Whenever I try to run my app in Xcode 6 Beta 4 I am getting the error:

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

This error appears no matter what simulator or device I target.

I have tried:

• Deleting all Derived Data from Organizer in Xcode
• Repairing permissions on my drive
• Manually elevating the permissions of the built MyApp.app
• Restarting my computer

Has anyone else run into this problem and found a solution?

Solution 1

There was a problem with the Info.plist of the project. I created a new project with the same name in Xcode 6 beta 4 and then replaced the real project's Info.plist with the new one. The project then built and ran fine.

Look at the diff, it appears like the plist might have somehow gotten mixed up with a playground's plist. The bundle identifier was "com.apple.dt.playground.iOS-18300-13" and the executable and bundle names were "iOS" along with some other oddities.

This is the full diff in case anyone needs it for reference:

        <key>CFBundleDevelopmentRegion</key>
        <string>en</string>
        <key>CFBundleExecutable</key>
-       <string>iOS</string>
+       <string>${EXECUTABLE_NAME}</string>
        <key>CFBundleIdentifier</key>
-       <string>com.apple.dt.playground.iOS-18300-13</string>
+       <string>com.myCompany.${PRODUCT_NAME:rfc1034identifier}</string>
        <key>CFBundleInfoDictionaryVersion</key>
        <string>6.0</string>
        <key>CFBundleName</key>
-       <string>iOS</string>
+       <string>${PRODUCT_NAME}</string>
        <key>CFBundlePackageType</key>
-       <string>AAPL</string>
+       <string>APPL</string>
        <key>CFBundleShortVersionString</key>
        <string>1.0</string>
-       <key>CFBundleSupportedPlatforms</key>
-       <array>
-               <string>iPhoneSimulator</string>
-       </array>
+       <key>CFBundleSignature</key>
+       <string>????</string>
        <key>CFBundleVersion</key>
        <string>1</string>
-       <key>DTPlatformName</key>
-       <string>iphonesimulator</string>
-       <key>DTSDKName</key>
-       <string>iphonesimulator8.0</string>
-       <key>LSBackgroundOnly</key>
-       <true/>
        <key>LSRequiresIPhoneOS</key>
        <true/>
+       <key>UIMainStoryboardFile</key>
+       <string>Main</string>
        <key>UIRequiredDeviceCapabilities</key>
        <array>
                <string>armv7</string>
        </array>
+       <key>UISupportedInterfaceOrientations</key>
+       <array>
+               <string>UIInterfaceOrientationPortrait</string>
+               <string>UIInterfaceOrientationLandscapeLeft</string>
+               <string>UIInterfaceOrientationLandscapeRight</string>
+       </array>
 </dict>
 </plist>

Solution 2

I use Xcode6 GM. I encountered the same problem. What I did was to go to Build Settings -> Build Options. Then I changed the value of the "Compiler for C/C++/Objective-C" to Default Compiler.

Solution 3

Having the problem on DEVICE too (not just simulator)?

---

The other solutions only fixed it for me on simulator, not device.

For me this problem occurred (in Xcode 6) when I would try to change the main info.plist properties whilst trying to change my app name.

In info.plist I had changed Executable File name to something other than the default ${EXECUTABLE_NAME}...

I had mistaken this field for the field that changes the name of the app under the icon on the springboard.

Solution 4

In Xcode do the following

Window --> Organiser --> Projects --> The app with the issue --> delete button in Derived Data.

I then cleaned the project and voila

works

Solution 5

For me, a simple Product -> Clean worked great

View more solutions

Comments

[Bamaco]

I am getting the same problem with XCode 6.1. At first, the issue was just with the simulator, now, after following some leads in this post, I have the same error running my target phone as well.

[Srinivasan N]

I followed @YuAn solution. It works very well for the simulator. Thanks But when I try to build it on the device, I am still getting the message saying 'I don't have any permission to view it'. The myapp.app file in products directory in xcode and also in derived data directory is showing blocked even after trying to build after deleting the contents of the derived data.

[Krumelur]

Another (stupid) way to trigger this problem: Compile an app with only resources, and no source files. Don't ask me how I know that :)

[mazorati]

Product > Clean solve this for me

[Ravi]

In my case none of these did not work!! Once I delete pilst file from Xcode and again attach with project, it works like a charm!! Hope help you Guys!!

[mrunal thanki]

I have different solution for it. Please check my answer here stackoverflow.com/a/46546044/5013722

[monkey0506]

@Krumelur I just spent hours on that before I stumbled upon your comment. The project in question doesn't need any of its own source code -- it's a standalone game app built from the game engine "framework" and a game data file. The game engine framework is built as a dependency via Xcode, but the app isn't executable unless it has some (redundant/useless) source code of its own. THANK YOU.

[Mohd Iftekhar Qurashi]

I am also facing same issue in the when running app in Xcode 10.1 if any one have better solution please share

[Jason]

When cleaning failed to resolve it and my Info.plist settings were already as mentioned in the solutions below, restarting my machine worked like a charm. Good old turn it off and on again :)

[Narendar Singh Saini]

What worked for me is here: stackoverflow.com/questions/24924809/…

[drewag]

I tried the extreme of giving "everyone" Read & Write permissions but still no luck

[fingaz]

So the other thing that I can think of to try is to reset ACLs and Home Folders which I believe is commonly found on the recovery partition by enter resetpassword in the terminal app. But to further troubleshoot you could drag that folder to the shared folder at /Users/ and create a new admin to see if it is user specific.

[drewag]

thanks for the help! I actually discovered the problem (the info.plist of the project was corrupted)

[Fede Cugliandolo]

This answer should be marked as the correct one @drewag

[Slowburner]

In my case, this worked thank you. I'd been changing other similar fields in my <appname>-Info.plist file, and once I'd changed Executable File back to ${EXECUTABLE_NAME} as you suggested, it built and ran.

[Fabio Napodano]

it looks like there are different problems behind this cryptic error message, anyway this is what solved my ptoblem with XCode 6.1

[nburk]

To clear it up: 1. Go to Build Settings (Choose All and Combined) 2. Search for Build Options 3. Set the Compiler for C/C++/Objective-C to Default Compiler

[Bala Vishnu]

Thanks..Same was my case

[Eric]

One thing to note, is that mine was set to $(EXECUTABLE_NAME) and updating it to ${EXECUTABLE_NAME} fixed the problem for me.

[Srinivasan N]

I followed @YuAn solution. It works very well for the simulator but when I try to build it on the device, I am still getting the message saying 'I don't have any permission to view it'. The myapp.app file in products directory in xcode and also in derived data directory is showing blocked even after trying to build after deleting the contents of the derived data. Any Idea what went wrong?

[Nilesh Kikani]

Thanks a lots @Albert Renshaw, youe answer resolved my issue. I am searching solution for that since last two days.

[Pescolly]

Good reminder that sometimes the simple solution is the one that works.

[zumzum]

this worked for me BUT it keeps happening. I can't continually delete derived data every time I want to run the app in the simulator...

[WebOrCode]

Same problem, name of field is "Bundle display name" for changing name under the icon

[Jayprakash Dubey]

@Albert : I have default $(EXECUTABLE_NAME) name in Executable file but still getting the same build error..

[Paul]

This was the answer for me when using SpriteBuilder (Cocos2d-Swift)

[kiranpradeep]

Why are people up voting this copying of the highest rated answer?

[Joris Weimar]

Same. I had product name set to fixed value. When I changed the target name, the error showed up.

[Jayprakash Dubey]

@iOSRocks : Welcome buddy!

[JakeP]

Thank you, this helped a lot.

[tonyedwardspz]

I had this issue after upgrading OSX today. This had it sorted in under a minute.

[endavid]

I tried localizing the Info.plist but then it gave me a build error because it couldn't find the file anymore. I reverted my changes, and then I was getting this "permission" error thing. Since everything was obviously as it was before, the problem wasn't in the Info.plist itself. I cleaned the Build folder as yury.ku suggested and that worked for me.

[MobileMon]

Yeah happened to me when trying to change app name. Season developer so just went into plist absentmindedly and changed "Executable File" when in reality I mean to change "Bundle Name"

[Luca Torella]

yep, I had a similar problem. Info.plist file was in the binary file format. Had to convert it

[Ri_]

I don't know how you discovered this, and it wasn't my exact problem but it lead me to the solution so THANKS!!

[Ohad Schneider]

A similar thing happened to me. My Info.plist was not configured correctly, so XCode took the first Info.plist it happened to find in the project's folder, which belonged to some unrelated dependency.

[Tommy]

A clean and Xcode restart was required here under Xcode 7.2.1. Cleaning alone progressed me to an "unknown error" with no attempt to build.

[Alex]

thank god, you just saved me hours of pointless Xcode debuggin'

[Mike Gledhill]

This also fixed it for me. With a "different" application name, the program built, ran, and would even Archive (ready to become an in-house app). But when I attempted to make that in-house app with a manifest file, I'd get an error of "Missing required bundle identifier property in distribution manifest" error. Xcode. Each year giving us another reason to hate it just a little bit more.

[yeahdixon]

YUP this was it for me too .

[Jeremy Kelleher]

You can also change the name of Info.plist to FRAMEWORK_NAME_HEREInfo.plist

[user1105951]

this helped me. but I thought I can use folder reference. strange.

[emiliomarin]

This fixed it for me. It happened after I renamed my project. Thanks.

[Firas Shrourou]

The same here, copying from another projet

[SLi]

Yes. This helped me too.

[chadbag]

This lead me to my solution, which was I had gotten an extra Info.plist when I included the source for an external library into my code, and they had an Info.plist inside their assets group folder. Removing that extra Info.plist fixed my problem.

[mkll]

Worked for me too.

[JerseyDevel]

This is exactly what my issue was. I added another folder of swift files and it had a plist file in there. I deleted that plist file and all is well.. Thank you!

[Vyachaslav Gerchicov]

and? the question is about macOS, you answer for iOS

[Giriraj.Mulay]

I am facing same issue tried various solution but didn't worked for me.. Help will be appreciated

[Soylent Graham]

I also had this, (missing a main()) but with .cpp, for any readers that may believe the .m or .mm is significant.

[AZZ]

it's worked for me. I finally fixed by deleting the Exclude_Archs. 3q very much！ It's what you says, not a permission issue.

[Ilya Muradymov]

finally! –––– thank you, I've forgot about that setting!

[pyfyc]

It works for me too in xcode 12.1. However it says that the "Legacy Build System" property will be deprecated in future versions.

[Arshad Shaik]

It would be better, if you have explained in detail

[DoruChidean]

Using the legacy system fixed it for me too. Now I just need to find out how to migrate to the new one

[jwezorek]

let me know if you figure this out please. I havent tried.

[salvi shahzad]

where is the issue navigator?

[Aftab Ahmed]

Very well said @jwezorek! If one has run the code in New Build System and have changed to Legacy build system, it was giving this issue. We may have to change it back to Legacy may be once or twice and try again. I had run the code in Xcode 13 where it takes New Build system and had switched back to Xcode 12.

[ManuQiao]

@salvishahzad the left area of Xcode, where you see build warnings and errors. Cmd+5 is the shortcut under Xcode 13.