I was stuck with this problem for few hours, but graceful solution is finally found.
My method doesn't use "manual files linking", only pure podfile usage.
I faced this problem when I have updated my pods ('pod install' or 'pod update') after adding another target to the project.
My solution is:
Go to your podfile and make sure you have defined "target ..." block for each target of your project (voila! seems like not documented, at least I didn't find it).
For example you have 2 targets: "theApp" and "theApp Lite". In this case your pod file must look like this:
target 'theApp' do
# ...your pods and options here
end
target 'theApp Lite' do
# ...your pods and options here
end
Then do "pod install" or "pod update" to update your libraries.
Then go to each target's General settings and make sure you have proper (corresponding to you target) "libPods...a" (or "libPods...framework", in case you use "use_frameworks!" podfile option) file linked under "Linked Frameworks and Libraries" section. Remove garbage/wrong/confused links if any. Add manually if missing (must appear under "Workspace" group/dir when you hit "+").
Under "Build Phases" you should observe "[CP]"-prefixed items for each target.
After this I had no problems with building.