Xcode cannot open Info.plist - error says "no such file"

I switched to Xcode 4 and loaded my project, which worked fine in Xcode 3. When I run it, I get an error message:

The file "Info.plist" cannot be opened because there is no such file.

I looked at the file in Xcode and it is. So why can't it be open?

+55
xcode xcode4 info.plist
May 26 '11 at 22:36
source share
10 answers

There is not enough file in the Xcode project folder. Have you confirmed that the file is correctly specified in the settings of the target installation of the application so that it correctly copies it to the application package? This is not quite the same as a standard resource (i.e., it did not become a target member in the settings of the target membership flags), but rather an assembly setting because of its importance in a correctly formatted bundle.

Go to the project (select it in the Project Navigator), select the application target in the list of goals, then go to the "Build Settings" tab. In the "Packaging" section, make sure that "Info.plist File" is correctly set to the location / file name.

+127
May 28 '11 at 15:50
source share

Go to goals. right click on the test target. yourProjectTests and delete it

+14
Jan 13 '15 at 12:16
source share

For me, the problem was that some of the .storyboard files had different deployment goals after merging. This is fixed by setting all storyboard files to "Project Deployment Goal". enter image description here

+10
Aug 31 '15 at 20:17
source share

Xcode 8

Select the project file in the left pane. Then open the general tab, and they added a beautiful button that allows you to select a file. (You may need to add it to your project structure)

enter image description here

+6
Nov 15 '16 at 15:00
source share

For me, this happened as a result of enabling the localization of the plist file (to indicate a language-specific application identifier on the springboard).

In the goal settings > builds> packaging> info.plist file, I changed the path from AppName / AppName- info.plist to AppName / Base. lproj / AppName-info.plist , and everything worked as expected .

Remember that its lproj is like in a small L, and not in the capital I.

Hope this helps.

+4
Nov 18 '15 at 13:53 on
source share

in Xcode 4.6, if appname-Info.plist does not appear in the project → target / info, go to the summary tab and it will ask for the appname-Info.plist file. Select the correct file from the sentences.

+1
Jun 29 '13 at 7:39 on
source share

Under Goals> Packaging> Info.plist File, verify that the file path is correct.

+1
Oct 17 '13 at 4:51 on
source share

In my case, the file was there, but distorted. If you recently edited your Info.plist in a text editor, discard this change and try again without violating the markup.

0
Sep 16 '15 at 12:19
source share

For me, the problem was that the error was referencing Info.plist from the library that I used, and not the actual .plist file from the project.

Perhaps this will help someone in the future.

0
Jan 24 '16 at 12:28
source share

In my case, one of the keys was skipped when adding the ATS match flag

 <key>NSAppTransportSecurity</key> 

Instead of the correct one as shown below

 <true/> <key>NSAppTransportSecurity</key> <dict> <key>NSAllowsArbitraryLoadsInWebContent</key> <true/> <key>NSAllowsArbitraryLoads</key> <true/> <key>NSExceptionDomains</key> <dict> <key>some-service1.com</key> <dict> <key>NSExceptionAllowsInsecureHTTPLoads</key> <false/> </dict> <key>some-service2.com</key> <dict> <key>NSExceptionAllowsInsecureHTTPLoads</key> <false/> </dict> </dict> </dict> 

I had this

 <dict> <key>NSAllowsArbitraryLoadsInWebContent</key> <true/> <key>NSAllowsArbitraryLoads</key> <true/> <key>NSExceptionDomains</key> <dict> <key>some-service1.com</key> <dict> <key>NSExceptionAllowsInsecureHTTPLoads</key> <false/> </dict> <key>some-service2.com</key> <dict> <key>NSExceptionAllowsInsecureHTTPLoads</key> <false/> </dict> </dict> </dict> 

Although some of the online XML validators did say that the XML files were correct (which was not), I used

 plutil filename.plist 

go to the directory where the plist file is present (from the terminal) and find out the exact line number in which there were problems

0
May 31 '17 at 11:55
source share



All Articles