Trying to build an iOS 9/watchOS 2 app for AdHoc distribution but keep getting code signing issues

Question

Created Jul ’15

Replies 20

Boosts 0

Views 13k

Participants 15

So I'm trying to build my app for distribution for AdHoc beta testing, but I keep running into code signing issues. Building and running on decide (both phone and watch) work fine, but when I try to create an AdHoc distribution build, I run into this 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]

I get this error during the step where it is validating the embedded WatchKit App binary.

I've tried to follow the instructions creating a Distribution signing certificate, installing it, and then creating AdHoc provisioning profiles for each of my iOS app, the WatchKit app, and the WatchKit extension. I set the code signing identity for the release build setting for all three to my distribution certificate, and I've set the provisioning profiles for all three to their respective AdHoc profiles, but I keep getting this error.

I double checked my WatchKit App target and the code signing identity and provisioning profile are definitely there, so I'm not sure why it's complaining that it's not code signed.

Boost

Answer 1

fehners OP

Aug ’15

Same here.. frustrating

Dear developer,

We have discovered one or more issues with your recent delivery for "[My App]". To process your delivery, the following issues must be corrected:

Invalid Executable - The executable '[My App].app/Watch/[My App]Watch.app/PlugIns/[My App]Watch Extension.appex/[My App]Watch Extension' does not contain bitcode.

Once these issues have been corrected, you can then redeliver the corrected binary.

Regards,

The App Store team

0

Answer 2

rt_mpow OP

Aug ’15

Might be that everyone misunderstood the documentation? Opened a thread about this: Is bitcode mandatory for all targets if you have a watchOS 2 App?

I hope I'm wrong but today I realized we all might have misunderstood the (not very clear) documentation.

0

Answer 3

rsdcoufal OP

Aug ’15

We were also having this problem, but it seems to have been resolved in XCode 7 Beta 6.

We can now build our ios target (ENABLE_BITCODE set to NO) and our watchapp/watch extension (ENABLE_BITCODE set to YES) without the "Embedded Binary Signing Certificate: Not Code Signed" error. We're distributing this app (signed using a in house enterprise cert) to users who can all run it.

0

Answer 4

lunaropolis OP

Sep ’15

Can also confirm that we have a watchOS 2 target that has bitcode enabled and a parent target that has it disabled. We use CocoaPods in our parent target. We had to go in to each target in our CocoaPods project and turn bitcode off because our parent target links against it. Everything archives perfectly fine now.

0

Answer 5

bgfriend0 OP

Oct ’15

I've been working through this issue via a radar. Last night Apple instructed me to test against Xcode 7.1 beta 3, and I am happy to say the issue is resolved for me.

0