WachOS2 Code Signing Issues on Archive

Originator:brian
Number:rdar://22260851 Date Originated:8/12/15
Status:Closed Resolved:8/14/15
Product:Developer Tools Product Version:Xcode 7 beta 5
Classification:Serious Bug Reproducible:Always
 
Summary:
When attempting to archive an iOS 8, iOS 9 app with a WatchOS 2 extension, code signing fails with the error If bitcode is disabled for the iOS app and enabled for the WatchOS 2 app.

error: Embedded binary is not signed with the same certificate as the parent app. Verify the embedded binary target's code sign settings match the parent app's.  
  Embedded Binary Signing Certificate: Not Code Signed  
  Parent App Signing Certificate: iPhone Distribution: [My signing certificate]  

This is a serious issue that halts development for us as 3rd-Party libraries have not upgraded to supporting bitcode and may not for some time.

Steps to Reproduce:
1. Add a WatchKit App to existing iOS app.
2. Disable bitcode for iOS app
3. Choose Product > Archive
4. Build fails with error:

error: Embedded binary is not signed with the same certificate as the parent app. Verify the embedded binary target's code sign settings match the parent app's.  
  Embedded Binary Signing Certificate: Not Code Signed  
  Parent App Signing Certificate: iPhone Distribution: [My signing certificate]  

Expected Results:
Building an iOS 8, iOS 9 app that does not use bitcode with a WatchOS 2 app that does use bitcode, should allow me to archive and distribute my iOS and watchOS2 app.

Actual Results:
Build fails with a code signing error.

Version:
OS X 10.11 Beta (15A244d), Xcode 7 beta 5 (7A176x), iOS 9 beta 5, watchOS 2 beta 5, iPhone 6 Plus

Notes:
This is a well reported issue on the developer forums: https://forums.developer.apple.com/thread/10392?q=Code%20Si

Configuration:
MacBook Pro 15" (Late 2013) OS X 10.11 Beta (15A244d), Xcode 7 beta 5, iOS 9 beta 5, watchOS 2 beta 5, iPhone 6 Plus

Comments

Duplicate of 22007571 (Open)

Engineering has determined that your bug report is a duplicate of another issue and will be closed.

The open or closed status of the original bug report your issue was duplicated to appears in the yellow "Duplicate of XXXXXXXX" section of the bug reporter user interface. This section appears near the top of the right column's bug detail view just under the bug number, title, state, product and rank.

If you have any questions or concerns, please update your report directly here: http://bugreport.apple.com/.

By brian at Aug. 24, 2015, 7:25 p.m. (reply...)

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!