Configuring third-party frameworks for code signing modifies them
| Originator: | cpickslay | ||
| Number: | rdar://26806567 | Date Originated: | 6/14/2016 |
| Status: | Open | Resolved: | |
| Product: | Xcode | Product Version: | 8 |
| Classification: | Serious bug | Reproducible: | Always |
Summary: If your app includes a third-party framework, iOS 10 requires that it is code signed. But code signing modifies the third-party framework's project file with your signing identity, which is problematic for keeping dependencies up-to-date. Developers can't reasonably push their identities to the source repo, and keeping the change on a downstream branch will lead to merge challenges as the upstream project changes. Steps to Reproduce: 1. Unzip the attached project and open it in Xcode 8 2. Select the "Framework Dependency Test" target 3. Select a Team under Signing in the General tab 4. Archive the app Expected Results: The archive should appear in Organizer Actual Results: The error "Signing for MagicalRecord for iOS requires a development team. Select a development team in the Target Editor. Code signing is required for product type 'Framework' in SDK 'iOS 10.0'" appears in the Check Dependencies phase. Version: Xcode 8, iOS 10 Notes: It can be fixed by selecting a signing identity on the Magical Record subproject, but that modifies the subproject's project file. It would be much more manageable if the signing identity for the app applied to its dependent frameworks as well. Configuration: Attachments: 'Framework Dependency Test.zip' was successfully uploaded.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!