I have issues with POD installation.
In "ProjectName"[Demo] and "ProjectName"[Release] I get the error:
"...target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES build setting defined in `Pods/Target Support Files/Pods-ProjectName-Demo/Pods-ProjectName-Demo.debug.xcconfig'. This can lead to problems with the CocoaPods installation"
I have set "Always Embed Swift Standard Library" to NO
Edit: I have done the suggested steps in the suggested duplicate post thread, but still got error
I was able to fix this problem by doing the following:
1.Go into Build Settings
2.At the top select All and Combined
3.Under Build Options you should see Always Embed Swift Standard Libraries and it is bold.
4.Click on it and click delete. It should now be unbolded.
5.Pod install and the error/errors should go away!
For more details please refer this link.https://github.com/CocoaPods/CocoaPods/issues/5981
Related
New to Xcode (dabble a little). I paid a developer to build an iOS app for me. He sent me the source code and I have opened it in Xcode 13.2.1. I needed to edit the info.plist to include a description why location was required (got this done). When I try to run the build, I get the error 'no such module 'IQKeyboardManagerSwift'. In AppDelegate, I see 'import IQKeyboardManagerSwift --- No such module 'IQKeyboardManagerSwift'. I went to the Podfile directory and ran 'pod install'. Output says:
Analyzing dependencies
Downloading dependencies
Generating Pods project
Integrating client project
Pod installation complete! There are 7 dependencies from the Podfile and 8 total pods installed.
I'm still getting the error when trying to run the build. I tried cleaning the build folder and running the build again but still, same error. What am I missing?
I'm not sure why this happens, but one way to solve your issue is to go into your build settings and define the Framework Search Paths to a folder that contains the frameworks in question. If the frameworks are placed in your project directory, simply set the framework search path to $(SRCROOT) and set it to recursive.
Is the codebase completely in Swift?, else you will have to include import in the Bridging header file
If in swift you can try:
Select project name -> Select Build Settings(tab) and search Framework Search Paths double click and set the desired path($(SRCROOT)) to recursive
The missing module handles a number of keyboard behaviors so you don't have to reinvent that wheel. Check out the developer's website and get it for yourself. I've been using it for years. The developer has helped me more than once get past some obstacles.
I am tryin to install Firebase using cocoapods so I may send push-notifications to user devices. However, everytime I follow the instructions step by step, I get this error that says "framework not found FBLPromises". Anyone have any ideas how to fix? Everything I have looked up online does not work.
The following worked for me:
What probably happened (for anyone still looking) is that after running
pod install
in your project's directory, you are still building the ".xcodeproj" file instead of running the newly created ".xcworkspace" from the pod install. Remember, after pod installing, you MUST do edits on and work with the .xcworkspace instead.
Go to your Pod target and add arm64 in Excluded Architecture
I was having the same issue, and I solved it by going to Product > Scheme > Edit Scheme... and selecting Find Implicit Dependencies. After that, the project was able to build correctly.
Probably late but I managed to fix it by linking FBL promises in my podfile to the rest of the project!
Click on the project > Targets. Select your target. Then click on Build Settings. Find "Runpath searches path" and add "$(PODS_CONFIGURATION_BUILD_DIR)/PromisesObjC". It worked for me, but it gave me another error dealing with another missing lib, so I had to do it again until all libs were found.
Go to your Pod target and set Build Active Architecture Only = YES For Debug Environments
Simply setting Build Active Architecture: Debug - Yes, Release - No fixed this for me. I had it set to No, No before. I think this matches the setting in the Pods project.
Open Podfile by typing the command open Podfile in the folder of the project using the terminal.
Type pod Promises
Done
While installing swift pod - Nimble, Quick, - I have faced weird problem. I saw success message for all the pod after pod install but all the frameworks showed me as red. And when tried to import these modules started showing me error as "No such module".
You can build Nimble and Quick separately just go to the manage schemes and check Nimble and Quick in the show column. After that just build both Nimble and Quick.
After trying lot of options - even suggested by #Vital - I have seen this problem comes very often. I created a new project and above answered didn't worked.
If you go to the link CocoaPods TroubleShooting page and refer #4. Solution seems to work always as it builds pods before building the project target. This is very useful in case you see pod frameworks are red in color and it's not able to find in derived data.
Open the project with the .xcworkspace file not with .xcodeproj.
with the reference of this Xcode has started making archives, not apps. How do I change it back? question and answer i have to change my "Skip Installation" flag but i am unable to find this flag. I am using xcode 4.4.1.
Kindly help me how can I fix it?
Go to project - build settings. In the search field type "skip". It will show you the Skip Install option in Deployment.
If your trying to run an iphone project downloaded from the internet in Xcode and you encounter "Library not found for -lxxx", where -xxx is some third party library where would you look to set the library path? I am not sure where this is setup, in the SCM->library path is blank and everything else seems to match the configuration window for other working projects
When I look at the build log i see the following in the linker output:
-ObjC -ljson
How can i configure the project to not try to link in that library at build time?
if using cocoapods and getting this error, try updating the cococapods$ sudo gem update cocoapods Then update the pod for the project$ pod updateI don't know the exact reason but I think it was because the old version didn't set the libraries properly for the new XCode.Hope this helps.
Within the build tab of project settings there is a field for linker options, I removed the -ljson from here to solve the issue.
Either you need to add that library to add your project or you can remove from the project and delete all the reference.
This may help you, just click on the library and change the 'required' option.
This might be helpful in some cases:
Xcode > Preferences > Locations > Locations > Advanced, select Unique.
I was facing a similar issue and chaging to "unique" from "legacy" solved the problem