Embedded binary is not signed with the same certificate as the parent app yet they are identical

Question

An app extension is causing a code signing issue. This app is already on the Appstore (with this extension) yet overnight for some reason when I have come back to this ap

Answer 1

When I had this issue I went to the Apple Member Center and realized that the Provisioning Profile (for the extension) that I had created was marked as 'Invalid'. I just re-created the Provisioning Profile with the same certificate that the app is signed with and then downloaded it via Xcode > Preferences > Account > refresh.

Once I had the new provisioning profiles I selected them in the build settings. I selected the provisioning profile that was just created and also selected the corresponding certificate in the Code signing entity in the build settings and that fixed the issue.

Note that the extension has its own app id and hence its own provisioning profile.