Failed to load Info.plist from bundle
IosXcodeSwift3Ios SimulatorAlamofireIos Problem Overview
Ios Solutions
Solution 1 - Ios
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. :)
Solution 2 - Ios
Simply
Just quit the simulator and open it again and it should works fine
Solution 3 - Ios
None of the above suggestions worked for me.
Changed the Embed setting for the complained framework to Do Not Embed resolved the issue. :)
Solution 4 - Ios
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
Solution 5 - Ios
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.
Solution 6 - Ios
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
Solution 7 - Ios
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
Solution 8 - Ios
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".
Solution 9 - Ios
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.
Solution 10 - Ios
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
Solution 11 - Ios
Remove the app from the Simulator worked well.
Solution 12 - Ios
Search for "Erase all content and settings" in help for emulator
Solution 13 - Ios
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.
Solution 14 - Ios
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.
Solution 15 - Ios
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
Solution 16 - Ios
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.
Solution 17 - Ios
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...
Solution 18 - Ios
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
Solution 19 - Ios
- Remove Pods and
- Install Pods again
is also one solution.
The reinstallation of Pods worked for me.
Solution 20 - Ios
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.