Invalid Signature (Invalid Binary) on Itunes Connect

Invalid Signature (Invalid Binary) on iTunes Connect

In Xcode, at the target level do the following:

1. First choose the provisioning profile for the Release configuration. (For Any SDK)
   The provisioning profile must match the app's Bundle ID (As you can see in the General tab).
2. In the code signing identity, tap on the sub-menu for Any iOS SDK and make sure you choose Automatic. If you can't see below.
3. Clean All and Archive.

Choosing CodeSign identity:

In step 2, if you can't choose Automatic, then it means you might not have a match between the AppID and the app's Bundle ID.
The AppID is pointed by the provisioning profile you chose.

If this is the case, then login in the developer portal and make sure that the provisioning profile you used points to the correct AppID.

To verify the the .ipa or .app before you submit try these commands.
Then look at the printout, and see if all looks right. Also verify the expiration date.

$cd <where the app is>
$unzip *.ipa
$cd Payload
$codesign -d --entitlement - *.app
$codesign --verify -dvvv *.app
$security cms -D -i *.app/embedded.mobileprovision

Invalid Signature - Itunes Connect

After a lot of debugging I just created a new ionic project via cli and copied my src folder into it. So some configuration was messed up. Can't tell which one.

Invalid Signature - Itunes Connect

After a lot of debugging I just created a new ionic project via cli and copied my src folder into it. So some configuration was messed up. Can't tell which one.

---

Related Topics