The reason that happened in my case was some developer updated a pod A while I installed a new pod B (without updated pod A). So when I merged his codes I got the warning.
An easy way to fix this is to <1> remove libPods.a from General->Linked Frameworks and libraries <2> run pod install or pod update "an-existing-pod" again.
For step #2 the purpose is to update .xcodeproj file not to install pod again. If pod is already there cocoapods will just update .xcodeproj file.
It still happens from time to time to me. My solution is to search after the unknown UUID in your project file and simply delete all lines you'll find.
For my case, I re-run
pod install
and find this warnings aren't showing. This is due to merging the project file.The reason that happened in my case was some developer updated a pod A while I installed a new pod B (without updated pod A). So when I merged his codes I got the warning.
An easy way to fix this is to <1> remove libPods.a from General->Linked Frameworks and libraries <2> run
pod install
orpod update "an-existing-pod"
again.For step #2 the purpose is to update .xcodeproj file not to install pod again. If pod is already there cocoapods will just update .xcodeproj file.
Step 1:
Deintegrate your project from CocoaPods. Removing all traces of CocoaPods from your Xcode project.$
pod deintegrate ProjectName.XCODEPROJ
Step 2:
Install the pod Again$
pod install
It still happens from time to time to me. My solution is to search after the unknown UUID in your project file and simply delete all lines you'll find.
Terminal-command:
You should find something like this:
I don't know if you fixed this or not, but for future reference, I has the same issue.
On my case, after opening .pbxproj file on a text editor, realised that the first UUID pointed to the 'Copy Bundle Resources' of the 'Build Phases'.
Removing that and adding again fixed the issue for me.
Xcode 8 - 11
Target > General > Linked Frameworks and Libraries