iOS error “Embedded binary is not signed with the same certificate as the parent app”

Question

Those are my first steps in IOS applications development and I\'m facing some problem that I can\'t figure out.

error: Embedded binary is not signed with the         


        

Answer 1

Swift 5 . Simple way in my case check this screen shot i am done

Answer 2

Sometimes none of the solution on Stackoverflow works. In that case,

Solution

1. Make sure that there is no red mark/issue in any of the sections of Signing(Debug), Signing(Release) and Enabled capabilities in both of MainApp and EmbeddedApp
2. Make sure that both certificates and provisioning profiles are installed under login/system keychain.

3. Make sure that your certificate is never ever set as Always Trust. Access must be kept as Use System Default

Answer 3

This error is also shown when deployment target of your Today extension is newer than the parent app. They must be the same.

I have iOS app set to 10.0 and added Today extension which was automatically set to 11.4 as the latest. This caused the error to appear. Simply changing the Deployment target of the extension target to 10.0 resolved the issue.

Answer 4

I was having this issue when I migrated to Xcode 10 and managed to fix it by updating the architectures in "Build Settings"> "Valid Architectures" for the Watch target to

$(ARCHS_STANDARD)

This thread helped me out a lot: https://forums.developer.apple.com/thread/107563

Answer 5

Check if you have more targets like oneSignal or other else and check if you have the same team of the main target.

Answer 6

Oddly enough, I had to remove the products folder from my project in order to fix this error. Xcode crashed then, after reopening, worked like a charm!