Failed to load Info.plist from bundle

Question

Cannot run app. Failed to load Info.plist from bundle error occurs. When I CMD+K clean the project, it runs fine. But I have to clean the project every time I make changes and run the app.

Following is the screenshot of my podfile:

Have you found solution? I have to delete and reinstall app every time or have to do `CMD+SHIFT+ALT + K`. — Max, Jan 05 '17 at 11:18
I answered on similar question https://stackoverflow.com/a/73953023/5262417 — mqz.kim, Oct 05 '22 at 04:55

score 80 · Answer 1 · answered Feb 06 '17 at 12:11

80

I had tried all suggestion and none of them work Then I tried to Reset content and Setting of simulator and it worked for me. :)

answered Feb 06 '17 at 12:11

Reema

1,200
10
10

4

FWIW this is not in the simulated phone itself, but in the Mac menu while you're running the Simulator app, up near the Apple in the upper left portion of your screen: Click "Simulator" then "Reset Content and Settings..." – Brooks Hanes May 03 '17 at 14:42
In addition to resetting the contents in simulator, also shutdown Xcode and clean the derived data folder. That worked for me. – ArdenDev May 13 '17 at 01:14
this happened to me when I changes the BundleID of the app. Resetting content did the trick. – nefarianblack Oct 05 '17 at 09:25
I try but it still doesn't resolve this issue. FYI, my build is based on React-Native. – anticafe Jan 16 '19 at 09:30

Musa almatri · Answer 2 · 2018-10-08T19:23:40.430

30

Simply

Just quit the simulator and open it again and it should works fine

edited Oct 08 '18 at 19:23

answered Jan 26 '17 at 13:12

Musa almatri

5,596
2
34
33

score 17 · Answer 3 · answered Aug 14 '20 at 12:10

17

None of the above suggestions worked for me.

Changed the Embed setting for the complained framework to Do Not Embed resolved the issue. :)

answered Aug 14 '20 at 12:10

Vittal Pai

3,317
25
36

3

Thanks a lot ! This should be the accepted answer – Mahdieh Shavandi Aug 18 '21 at 15:29

score 14 · Answer 4 · answered Nov 10 '20 at 05:21

14

If you're still running into this issue after trying all the reset, checkout this answer to a similar question: https://stackoverflow.com/a/61846384/1341768

In your podfile replace:

use_frameworks!

with :

use_frameworks! :linkage => :static

answered Nov 10 '20 at 05:21

otusweb

1,638
1
19
30

score 9 · Answer 5 · edited Jun 08 '17 at 11:46

9

1: Remove app from simulator,

2: Product > Clean ,

3: Simulator > Hardware > Reboot ,

It solved my problem. In case it doesn't resolved, change your bundle identifier.

edited Jun 08 '17 at 11:46

Ashish Gupta

737
11
18

answered May 24 '17 at 10:44

Vinay Krishna Gupta

475
7
12

I did already mention in the question that I am already cleaning the project and it solves the problem temporarily i.e. I need to do it every time and it's not a permanent solution. – Chanchal Raj May 25 '17 at 08:58
Check your Bundle Identifier too. I corrected it and it solved my problem. – Vinay Krishna Gupta May 25 '17 at 11:26

score 8 · Answer 6 · answered Aug 28 '19 at 02:02

8

It was duplicated frameword when you config. Please check again in Embedded Binaries and Linked Frameworks and Libraries. With some frameworks, you don't need add in both sections, please remove one. It worked with me

answered Aug 28 '19 at 02:02

Lê Tấn Thành

337
3
5

1

removing from Build Phases->Embedded Frameworks worked for me. – ugur Oct 13 '19 at 16:27

Aashish · Answer 7 · 2019-01-01T06:33:03.127

6

This error occurs due to 'RealmSwift'. When you try to write in realm in certain directory, this error occurs, due to the conflicts in overwriting with realm.

You may want to Reset Content & Settings in simulator and also try cleaning your build folder in Xcode using Cmd+Shift+Option+K

edited Jan 01 '19 at 06:33

answered Apr 03 '17 at 07:48

Aashish

2,532
2
23
28

I did already mention in the question that I am already cleaning the project and it solves the problem temporarily i.e. I need to do it every time and it's not a permanent solution. Even trying reset the content and settings of the simulator solves the problem temporally. – Chanchal Raj May 25 '17 at 08:59
Well, this error occurs due to 'RealmSwift'. When you try to write in realm in certain directory, this error occurs, due to the conflicts in overwriting in realm. – Aashish May 25 '17 at 09:16

score 4 · Answer 8 · answered Nov 29 '19 at 14:04

I had this problem when integrating Firebase to my project. The issue was that Xcode automatically configured project to "Embed&Sign" the libraries when I drag&drop them into "Framworks, Libraries, and Embedded Content" section.

To fix that, I manually set them to "Do Not Embed".

Daniel Zhang · Answer 9 · 2019-07-02T04:09:08.910

I encountered this error in one of my projects and narrowed down a set of exact conditions that are able to reproduce it, thereby preventing installation to the simulator.

With Xcode 10.2.1, I was testing linking a framework. I noticed in the project navigator panel that two instances of it were present. This could have been due to my multiple attempts.

Inside the Xcode project package, I opened the file MyProject.xcodeproj/project.pbxproj and confirmed that the two instances were identical. The following snippet shows an example of how this was represented.

/* Begin PBXFileReference section */
...
    65C8CE8522CA0D3500271FFD /* MyFrameworkForiOS.framework */ = { 
        isa = PBXFileReference; 
        lastKnownFileType = wrapper.framework; 
        name = MyFrameworkForiOS.framework; 
        path = "../my-frameworks/out/MyFrameworkForiOS.framework"; sourceTree = "<group>"; 
    };
    65C8CE8722CA0D3800271FFD /* MyFrameworkForiOS.framework */ = {
        isa = PBXFileReference; 
        lastKnownFileType = wrapper.framework; 
        name = MyFrameworkForiOS.framework; 
        path = "../my-frameworks/out/MyFrameworkForiOS.framework"; sourceTree = "<group>"; 
    };
...
/* End PBXFileReference section */

By removing a duplicate reference in the project navigator (with command-backspace), I was able to install my app to the simulator without the error.

What didn't matter was the contents of Info.plist in my framework as it only had an empty root dictionary. Therefore, the error message may be misleading relative to the actual cause.

score 1 · Answer 10 · edited May 23 '17 at 10:31

1

It is annoying. Temporary I remove app on simulator then rebuild project work but still waiting for a better solution This problem likely to a problem with core data i have meet in the past.

Update: this solution work for me: https://stackoverflow.com/a/24042126/5387768

edited May 23 '17 at 10:31

Community

1
1

answered Oct 31 '16 at 02:12

Suke

138
1
8

But I am not using CoreData. – Chanchal Raj Oct 31 '16 at 03:42

score 1 · Answer 11 · answered Mar 06 '17 at 09:45

1

Remove the app from the Simulator worked well.

answered Mar 06 '17 at 09:45

Pau Ballada

1,491
14
13

score 1 · Answer 12 · answered Jan 14 '20 at 01:50

1

Search for "Erase all content and settings" in help for emulator

answered Jan 14 '20 at 01:50

Amit Patel

1,795
16
20

score 1 · Answer 13 · answered Jan 31 '20 at 12:28

1

swift 4,5

i had same problem, after some analysis i just found that i removed one of framework that cause this error. adding framework again solved t for me.

answered Jan 31 '20 at 12:28

MALIKK HABIB UR REHMAN

820
9
15

score 1 · Answer 14 · answered Mar 13 '20 at 06:46

Issue: Same issue came on Xcode-11 and none of the above methods worked.

Answer You need to check first the issue, where it is coming from. In my case it was due to all Pod libraries info.plist file was missing. (God knows how it got missed).

Comment the "pod libraries" in "pod file" and run "pod install"
Uncomment the "pod libraries" in "pod file" and run "pod install" again.

and it worked.

score 1 · Answer 15 · answered Apr 01 '20 at 17:39

Have run into this a couple of times in iOS w/ React Native. Found that a couple of extra steps helped. What ultimately fixed was:

1: Erase all contents and settings from simulator

2: Delete node modules

3: Delete pods folder

4: Reinstall node modules

5: Reinstall pods

6: Delete top secret derived data folder for Xcode

7: Xcode -> Product -> Clean build folder

8: Close out of metro bundler

9: (optional) Buy a new Mac Book Pro

10: Run Xcode

11: Contemplate the 30 minutes you're never going to get back

30 minutes?!! More like my entire morning :C – Erik Escobedo Apr 22 '22 at 21:03 — Erik Escobedo, Apr 22 '22 at 21:03

score 0 · Answer 16 · answered Mar 23 '17 at 09:35

0

If resetting the Simulator did't work. Try to change simulator like from iPhone6 to iPhone5s. Then later run in iPhone6 simulator and reset the Simulator again. It will start working.

answered Mar 23 '17 at 09:35

Muzammil

1,529
1
15
24

score 0 · Answer 17 · answered Feb 24 '20 at 19:42

0

After trying all of the above perfectly acceptable solutions (some of which had worked for me in the past) I was running out of ideas to solve this issue - finally resorting to rebooting my MacBook which magically resolved the issue.

Sometimes...

answered Feb 24 '20 at 19:42

Neil Palethorpe

359
4
6

score 0 · Answer 18 · answered Aug 28 '20 at 06:42

Following the below steps solved the issue for me:

Update the cocoapods by brew upgrade cocoapods
Clean the build folder using cmd+shift+k
Delete the derived data folder using cmd+shift+alt+k
Erase content and setting of simulator
Remove the pods completely and reinstall by rm -rf Pods\ Podfile.lock && pod install
run the project by Xcode and the app installed successfully

score 0 · Answer 19 · answered Sep 09 '20 at 10:29

0

Remove Pods and
Install Pods again

is also one solution.

The reinstallation of Pods worked for me.

answered Sep 09 '20 at 10:29

RajaSekhar

11
1

score 0 · Answer 20 · answered Oct 29 '21 at 13:34

0

I tried many options like clean build, delete derived data, erase all content and settings in the simulator, etc. But still the issue exists.

At last, I restarted the machine then I can run the app perfectly.

answered Oct 29 '21 at 13:34

IKKA

6,297
7
50
88

score 0 · Answer 21 · answered Sep 06 '22 at 06:54

0

use this command in terminal : defaults delete com.apple.dt.Xcode

then delete derived folder of Xcode

finally delete node modules and pods

reinstall node modules and pods while Xcode is closed

then start you project as normal.

answered Sep 06 '22 at 06:54

Abdul Jaleel

1

score 0 · Answer 22 · answered Oct 18 '22 at 12:11

if none of the above solution works for you then you should reset xcode to default

steps:

defaults delete com.apple.dt.Xcode
defaults delete -app xcode
rm -rf $HOME/Library/Application\ Support/Developer/Shared/Xcode
rm -rf $HOME/Library/Saved\ Application
State/com.apple.dt.Xcode.savedState
rm -rf $HOME/Library/Preferences/com.apple.dt.Xcode.*
Restart macbook
Delete node_modules and pod folder
delete /Users/{YourUser}/Library/Developer/Xcode/DerivedData ( hint: click pref -> locations -> click arrow next to Drived DAta)
close xcode
install node_modules and pods
run project like normal.

Failed to load Info.plist from bundle

22 Answers22

Simply

Linked