Xcode6:Embedded binary is not signed with the same

Question

After I add Today App Extension Target,I become impossible to compile project. below is 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: iPhone Developer: (Developer name) (number)

Parent App Signing Certificate: iPhone Developer: (Developer name) (number)

but Embedded binary certificate and parent app's cerificate are the same. So I'm confusing now...

Answer 1

I had discrepancies under Code Signing. My Extension and Main app had different certificates selected. Once I set both to use distribution it worked fine.

Answer 2

In my case the profile my extension target uses contains different certificates than the profile the parent target uses contains. This was exactly the error messages complained about!

The reason was I generated a new certificate for the extension profile.

So log in to developer.apple.com to see if these profiles contains different certificate.

Answer 3

I had a similar issue. For me the issue was with the certificate showing, 'signed by unknown authority'. I had followed the below steps and it is resolved. The problem was missing apple WWDR intermediate certificate.

We must also install the WWDR intermediate certificate issued by Apple’s worldwide developer relations. It can be downloaded from the portal or directly at http://developer.apple.com/certificationauthority/AppleWWDRCA.cer Make sure you add this to your keychain as well.

To add the certificate: open your keychain utility software on your Mac computer, then go to File→Import items, then select AppleWWDRCA.cer.

Answer 4

For Xcode 8 beta 3

My build numbers were off on my different Targets in my Xcode project file.

My iOS target had a build version 3, but my watch app target and my share extension target both had build version 1.

All I did was match all the targets' build numbers (changed them all to 3) and it fixed the issue.

Hope this helps.

Answer 5

In the case of using WatchKit, make sure that your Watch App has the correct "Team" selected in the Watch App Target settings (under General > Signing > Team). I had set the phone app's team, but not the watch app's team.

Answer 6

I had to select my app under 'Targets', then go to the 'Capabilities' tab and click 'Fix Issues' under the 'App Groups' section