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

User · Answer

For me  a simple Product -  Clean worked great

User · Answer

I m using Xcode 6 GM  I encountered the same issue   What I did was to go to Build Settings -  Build Options  you can search  compiler    and then changed the option of the  Compiler for C C   Objective-C  to Default Compiler

User · Answer

I had similar issues  Apparently I ve included Info plist from outside project folder  That lead to the same error  shown after every build  except after I run it after cleaning the project    To fix it I simply had to include Info plist from the project folder

User · Answer

I had this similar problem  Somehow my value for the key Executable File got mixed up  Just change it back to    EXECUTABLE NAME   Under your project   Info   Worked for me

User · Answer

Product -  Clean  command shift K  fixed it for me

User · Answer

with X-code 6 3 2    Build Settings  Options    All - Build Options - Compiler for C C   Objective-C - Default compiler  Apple LLVM 6 1    Then rebuild the project  and it runs ok

User · Answer

My Application was working fine on XCode 9 4  but when I opened my project in XCode 10 I was experiencing this issue  For me the issue was the build setting  I found the answer in this page https   forums developer apple com thread 112141   In short go to File   Workspace Settings      Build System and change it to  Legacy Build System

User · Answer

I had similar issue  xCode 6 2  for sample code downloaded  I tried to set Executable Name to Default in Info plist but this didn t worked    Instead change Compiler for C C   Objective-C to Default compiler  Apple LLVM 6 0  instead of Unsupported Compiler com apple compilers llvmgcc42  for project

User · Answer

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

User · Answer

Please also check if you have added any third party lib with plist  Some time third party lib has the info plist causing the issue

User · Answer

For me the error was in the  plist file at the key CFBundleExecutable  I had renamed the executable removing a space that was between two words   Eg  from  Wild Racer  to  WildRacer    Took 1 day to spot it     Xcode is soooo unhelpful in the debugging

User · Answer

I had this issue when my appdelegate class was not linked against my main app target but a separate static framework  Linking it directly against the target app fixed the issue

User · Answer

Well in my case  I just rename the Bundle Name and Executable file values in info plist same as project name  It worked for me

User · Answer

Don t know if the problem is related but maybe it can be a solution for anyone pulling the hairs like me    In my case  I have a project with a lot of targets  Each target is a customisation of that base project which is a Cocoa Touch Static Library and the targets  Applications  Even if the main file is added into the library compilation  but not in each target  that error message appears  So what I did  Manually added the main file to each target in the Compile Sources section and bingo  all fine

User · Answer

My solution was    Enter this in your Terminal  open   Library Developer CoreSimulator Devices  Delete the appropriate folder Compile again an it should work

User · Answer

1  Go Firstly  Build Options   2  Then changed the value of the  Compiler for C C   Objective-C  to Default Compiler   clean and working  -

User · Answer

I had the issue that the AppDelegate was missing   Creating a minimal one solved the issue   import UIKit   UIApplicationMain final class AppDelegate  UIResponder UIApplicationDelegate

User · Answer

Please check if you have changed Executable file      EXECUTABLE NAME  to any other name  If you have changed this name then it shows this error  Please replace it with   EXECUTABLE NAME

User · Answer

I ve fixed it by cleaning a build folder  Just went to  Product  menu and Option Click  Clean   After that a problem was resolved

User · Answer

None of the solutions worked for me in Xcode 10 3 when I added two objective-c files to my project  I fixed by following the below steps    Go to Build Phases Check if the  m file is present inside Compiler sources  If not add it Add -objc flag for compiler flags right next to the  m file

User · Answer

For me error was in file info plist  field Bundle identifier  Somehow it was modified to   com myCompany   PRODUCT NAME rfc1034identifier    from   com myCompany   PRODUCT NAME

User · Answer

The error message is generic and doesn t actually tell you what it really mean   For me I had to restore earlier github reversions which gave   armv7 armv7s arm64   to the architecture

User · Answer

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

User · Answer

I ve had this error with a number of my older projects that I am getting out of the cupboard to update  It seems that using Xcode 6 with older code seems to bring this about for some reason    I have fixed this in all projects that I have done this with by    Delete Derived Data   in Product  do a clean  go to Build Settings in the project Target and go to Build Options and  change the value of the  Compiler for C C   Objective-C  to  Default Compiler

User · Answer

Select Scheme Menu by pressing needed button on the right of run stop buttons       Press Edit Scheme           Select your executable

User · Answer

I changed name to new name then I returned the old name to my project and it helped me

User · Answer

I got same error on my Xcode 6 1 1 for a project downloaded from gitHub which was committed 4 years ago  For me  setting Architectures to the default value Standard architectures armv7 arm64  and Compiler for C C   Objective-C to Default Compiler in Building Settings worked

User · Answer

On my part  what trigger this error was that I had  at the root of my resources folder  a folder with the same name as my final executable file   So  when launching the executable  I think Xcode found the folder and had problem executing a folder   -

User · Answer

I was able to restore my project from a pre-xcode 6 1 backup   Once I open my workspace from a different directory  I was able to run my target without this error  The simulator also works fine now

User · Answer

In my case it helped just to close Xcode  repaired the permissions with the Disk Utility  Only after a reboot it worked like a charm

User · Answer

In my case main m containing the main      function was not contained in the list of  Compile Sources  in  Build Phases   To check if this is the case  enter into Build Phases and look  if your main m appears in the  Compile Sources  list

User · Answer

I recently meet the same problem for running an old project  initially created in Xcode 4 x  in Xcode 6 0 1   I fixed the problem by changing the Architectures in Building Settings to the default value  which is  Standard architectures armv7 arm64      Hope this could help anyone who got similar problems

User · Answer

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            lt key gt CFBundleDevelopmentRegion lt  key gt           lt string gt en lt  string gt           lt key gt CFBundleExecutable lt  key gt  -        lt string gt iOS lt  string gt           lt string gt   EXECUTABLE NAME  lt  string gt           lt key gt CFBundleIdentifier lt  key gt  -        lt string gt com apple dt playground iOS-18300-13 lt  string gt           lt string gt com myCompany   PRODUCT NAME rfc1034identifier  lt  string gt           lt key gt CFBundleInfoDictionaryVersion lt  key gt           lt string gt 6 0 lt  string gt           lt key gt CFBundleName lt  key gt  -        lt string gt iOS lt  string gt           lt string gt   PRODUCT NAME  lt  string gt           lt key gt CFBundlePackageType lt  key gt  -        lt string gt AAPL lt  string gt           lt string gt APPL lt  string gt           lt key gt CFBundleShortVersionString lt  key gt           lt string gt 1 0 lt  string gt  -        lt key gt CFBundleSupportedPlatforms lt  key gt  -        lt array gt  -                lt string gt iPhoneSimulator lt  string gt  -        lt  array gt           lt key gt CFBundleSignature lt  key gt           lt string gt      lt  string gt           lt key gt CFBundleVersion lt  key gt           lt string gt 1 lt  string gt  -        lt key gt DTPlatformName lt  key gt  -        lt string gt iphonesimulator lt  string gt  -        lt key gt DTSDKName lt  key gt  -        lt string gt iphonesimulator8 0 lt  string gt  -        lt key gt LSBackgroundOnly lt  key gt  -        lt true  gt           lt key gt LSRequiresIPhoneOS lt  key gt           lt true  gt           lt key gt UIMainStoryboardFile lt  key gt           lt string gt Main lt  string gt           lt key gt UIRequiredDeviceCapabilities lt  key gt           lt array gt                   lt string gt armv7 lt  string gt           lt  array gt           lt key gt UISupportedInterfaceOrientations lt  key gt           lt array gt                   lt string gt UIInterfaceOrientationPortrait lt  string gt                   lt string gt UIInterfaceOrientationLandscapeLeft lt  string gt                   lt string gt UIInterfaceOrientationLandscapeRight lt  string gt           lt  array gt    lt  dict gt    lt  plist gt

User · Answer

None of the provided answers worked for me  In my case  I finally fixed the error by updating the target architectures in Build Settings Architectures Valid Architectures to   ARCHS STANDARD   as arm64 was missing  This was not prohibiting the project to build  although a warning was issued recommending updating the valid architectures  but the  app could not be opened  error was shown at run time   I surmise this error is rather generic and not always linked with a permission issue  but may be displayed when the generated app package is invalid

User · Answer

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

User · Answer

My goodness   I spent hours to resolve this issue   On XCode 7 3 I was having project with no issues   Mistake I did  I just Added physical folders and moved my files into them  problem started   I 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 was about create new project and then I just deleted those physical   folders I added  clean build and YESS     It works

User · Answer

I found that changing my compiler to LLVM 6 0 in the Build Options was enough for me  xcode 6 1

User · Answer

I would go to the folder where your Xcode docs are and hit command   I to get info  At the bottom  hit the lock to unlock the folder to edit permission  If permissions look good  check the box that says to apply to enclosed folders and let that do it s thing  I haven t seen this personally and not sure if that s what you were saying in your post when you edit the build permissions

User · Answer

I had the same issue with Xcode 10  amp  react-native   All the above solutions didn t help me    My solution   Create a new project with the same name  And change project  amp  workspace files with the ones from the duplicated project  And it works     after some small build-issues with path etc

User · Answer

Maybe consider installing the latest version of Xcode  I did that after trying all the other solutions  which did not work for me  and the issue was automagically fixed

User · Answer

I fixed this by clearing my derived data from the preferences in xcode

User · Answer

I got this issue in Xcode 10 1 after adding objective c files to my swift project  Got this working by following the below steps    Add  m file to compile sources under Target -  Build Phases Add -objc to the compiler flags right next to the  m file

User · Answer

Try  cmd shift k  to clean the project and rebuild  At least it worked for me

User · Answer

I ve had same this error in Xcode 8 2  The reason I found out for me  another Info plist is added in my project while adding library  manually copy    So that Xcode is getting confused for selecting correct Info plist       I just removed that Info plist from the added library     Then it is working fine without any permission alert

User · Answer

Sometimes opening old project in new version Xcode will get this message   Go to Issue navigator and follow the warning hint  Upate to reconmmented settings    Boom  magic

User · Answer

What we didn t do right was to not apply with the accurate code when signing in the Build Settings  We fixed the issue up this way  Enter into Build Settings    Code Signing    Code Sign Identity  Then  apply with your iOS Developer ID for  Debug   but be sure to apply with your iOS Distribution Profile for  Release  We didn t apply correctly  so we couldn t have permission to ask for the App from the server  actually  Anyway this post forced us to revise all the parameters and requirements  so we pretty appreciate all your answers  Regards  T

User · Answer

I came to this issue both on simulator and device    And there is a tricky phenomenon  If I copy the project to a new place  there is some chance this issue gone when I first run  But after I clean and run  this issue comes   I have try almost all the solution from the answers to this question  but neither do   With the help of the version control system git  I can check out the previous version of the code and to see what modification lead to this issue   In my project the HEAD version is workable  and my latest umcommitted modification will lead to this issue   So I checkout each file from the workable version of my code to locate the issue  When I checkout the coin xcodeproj project pbxproj coin is my app name   this issue gone   Solution  just checkout the workable coin xcodeproj project pbxproj  for my case I just use the HEAD version is ok   git checkout HEAD coin xcodeproj project pbxproj    To make it a summary    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- gt preference- gt locations- gt 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

User · Answer

As i have also faced this issue today morning and none of the answers helped me out particularly in my case  And after trying for hours  i figured out the issue   Actually while working in storyboard by mistake  i just renamed my  Main storyboard  to   storyboard  and changing it back to  Main storyboard  solved my issue   SOLUTION As per my issue   May be you have renamed any file due to which xcode couldn t load it and raised an issue  For example  as mentioned above the case of changing  Executable File  name Possible Issue area  May be the last few files you were working in

User · Answer

That s because you may using the repository cloned from the git or svn  Try to clone another new version and run it

User · Answer

Check permissions to read write for project folder  Right Click for project folder in Finder   Get Info

User · Answer

I had the same issue in my project  Later on found that third-party  fmdb for SQLite  file used in project contained Info plist   Simply deleting the Info plist file worked for me

User · Answer

What I did is here   I deleted VALIDARCHS from Project I deleted VALIDARCHS from Target Build Active Architecture Only   YES  for Debug   Architectures Standard Architectures   ARCHS STANDARD   Also  File - gt  Project Workspace Settings    New Build System Xcode Version 12 0  12A7209

User · Answer

I fixed this myself switching between  arm32  and  arm64  architectures  From the  Build Settings   I modified  Architectures  and  Valid Architectures  from  arm32  to  arm64  and it worked  After changing a number of other settings  switching between arm32 and arm64 no longer makes a difference  so I m skeptical if this was the route cause   Previously I tried all the other suggestions here    plist was unmodified EXECUTIBLE NAME was unmodified Build Clean Delete DerivedData Default Compiler

User · Answer

This message will also appear if you use  m files in your project which are not added in the build phase  compiles source

User · Answer

What solved it for me was setting Build Active Architecture Only from No to Yes

User · Answer

I updated my cocoa pods and added new supported architectures in build settings and that fixed it

User · Answer

I tried all of the listed answers and none of them was useful  The problem was due to existence of an another plist file linked from a submodule via cocoapods  Luckily this was my own module  so I just deleted this plist from the submodule project and reinstalled pods   solution  Later on I understood that the key of the problem was in the name of that second plist  simply info plist  You may rename the file and relink it via a sources section of a submodule  That second plist file had a unique name  so Xcode was not supposed to become frustrated  Even my target settings pointed on a main plist  not on a info plist  Looks like Xcode takes special consideraions about that name  The bug reproduced in Xcode 6 4 and Xcode 7 0

[swift] "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

Examples related to swift

Examples related to xcode5

Examples related to xcode6