- This topic has 5 replies, 2 voices, and was last updated 11 years, 9 months ago by
.
-
Posts
-
Dear Octavio,
I have built my app a couple of days before in the first place and it was OK. Today I tried to build it again (i.e., new version) but I have the following error code: “Failed: Unable to sign the application”. I thought there might be a corrupted “private.key” file. So I used the one I had in back up, but the error still exists and I can’t built my app. What should I do? Is it safe to delete all (i.e., .csr, .key, .cer, .mobileprovision) and start from the beginning?
thanx,
GeorgiaHi Georgia,
Can you provide more details:
1) is the build wizard submitting you content?
1a) if yes, please post a build #
1b) if no, please provide more details as to where the error is occurring in the iOS Build Wizard2) are you submitting private key, certificate and provision profile? Or .p12 file and provision profile?
Hi Octavio,
Here are the details you asked for:
1) is the build wizard submitting you content?
1a) if yes, please post a build #,Answer: BUILD #428127, status: Failed
1b) if no, please provide more details as to where the error is occurring in the iOS Build Wizard,
Answer: Digital Signature problem in the build wizard. It requires the private key file, and I enter it. Error Log, Failed: Unable to sign the application.
2) are you submitting private key, certificate and provision profile? Or .p12 file and provision profile?
Answer: I am submitting private key, distribution certificate and provision profile.
thanx,
GeorgiaHi Georgia,
Our dev team have looked at your build ID details and seems that there’s a problem with copying your private.key file to our server, that’s why your app coulndn’t be signed. Please rename/move your design and attempt a new build. This would be a different project in server, and you should be able to build your app. Let me know how it goes for you.
