iOS error “Embedded binary is not signed with the

2019-01-14 21:18发布

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 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 Developer: Emil Adz (9QNEF95395)

I can't understand, what is a Embedded Binary Signing Certificate?

I went over the questions with the same error here, but none of them was related to the problem presented here (Not Code Signed).

I tried to revoke my certificate from the Apple Developer Member Center and request another certificate, but the issue persists.

Does some know how it could be fixed?

9条回答
老娘就宠你
2楼-- · 2019-01-14 21:45

I got this error when the App Groups weren't set up correctly on all my App IDs in the Developer Portal. Therefor the App Groups in the app didn't work correctly and the Binary for the extension or the Watchkit app couldn't be signed.

查看更多
地球回转人心会变
3楼-- · 2019-01-14 22:00

The embedded binary is referring to a widget that you are deploying alongside with your app.

In your case, you are not signing your widget with any Signing Identity (since your error says "Not Code Signed").

To resolve this, go to your Project file, find your widget's target, and under the Build Setting tab, find the Code Signing Identity value. Choose the same code signing identity that you are using for your main app's target.

You will also need to create and configure a provisioning profile specifically for your widget when you want to release it.

查看更多
别忘想泡老子
4楼-- · 2019-01-14 22:00

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.

查看更多
登录 后发表回答