Signing errors with use_frameworks! and unique provisioning profiles

Question

I am pasting my last post from Initial discussion here:

https://github.com/CocoaPods/CocoaPods/issues/4331

This issue has been around for almost a year, and stil

Answer 1

Ok, so I solved this time this problem my own way. As usually, the solution is easier than ever thought.

The cause of bugger error ERROR ITMS-90171 was this time a directive in podspec file.

This one: s.resource = 'MyPod/*'

No idea how I missed that one, but 'MyPod/*' literally says, include everything in MyPod's directory which besides the graphics assets contained the *.swift files as well.

So a little fix by changing that line to: s.resource = 'MyPod/Graphics.xcassets' fixed the problem. No ERROR ITMS-90171 any more.

---

However, Here we still have to live with a workaround (proposed by @DimaVartanian) that fixes the code-signing requirement for frameworks provided by cocoapods.

The fix itself is to add this code to base project's 'Podfile':

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['EXPANDED_CODE_SIGN_IDENTITY'] = ""
      config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
      config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
    end
  end
end

That will go(after 'pod install') through all pod targets in project and remove the code signing requirement by changing certain settings as you can see in code.

There are some rumours around, that this workaround will not be required anymore after upgrading to XCode 8. I have not found any official confirmation on this but I hope it is true.