This is a migrated thread and some comments may be shown as answers.

Invalid Code Signing

1 Answer 54 Views
AppBuilder in-browser client
This is a migrated thread and some comments may be shown as answers.
This question is locked. New answers and comments are not allowed.
Robin
Top achievements
Rank 1
Robin asked on 17 Oct 2013, 05:47 AM

I tried to publish my iOs app through Icenium Mist. It got uploaded, but shortly after the binary is rejected:

"Invalid Code Signing - The executable 'Payload/Cordova300.app/Cordova300' must be signed with the certificate that is contained in the provisioning profile."

To solve this I tried the following:
1. Revoke existing certificates in the "Certificates, Identifiers & Profiles" page and delete the mobile provisioning profile
2. Delete the existing certificates and mobile provisioning profiles in Mist
3. Make a new .csr in Mist, create a new production certificate and import it to Mist
4. Make a new mobile provisioning profile, linked to the new production certificate
5. Import new mobileprovision to Mist (and confirm that the certificate belonging to it in Mist is the new one)
6. Publish app again

Yet the binary is rejected with the same error!

I have published several apps with Mist before and never encountered this error. Now my customer is waiting and I don't know how to solve it.

1 Answer, 1 is accepted

Sort by
0
Robin
Top achievements
Rank 1
answered on 17 Oct 2013, 08:48 AM
Ok, now I feel quite stupid.

In case someone else should encounter the same "problem":

In mist, open the project properties. Click iOs. Under "code signing identity" make sure to select the proper one. 

For some reason my wildcard provision was selected here. When changed to the correct identity it works fine.
Tags
AppBuilder in-browser client
Asked by
Robin
Top achievements
Rank 1
Answers by
Robin
Top achievements
Rank 1
Share this question
or