- This topic has 37 replies, 6 voices, and was last updated 12 years, 1 month ago by
.
-
Posts
-
Same thing happened to me again today, tried 3 times to upload binaries all failed code sign. Closed application loader and Xcode, restarted loader and it went no problems. Something not quite right here I think.
Two days later and Apple still rejecting the ipa file with not signed message.
I redid all the files and it now installs on the device fine but will not be accepted by Apple…A new code-signing issue sounds odd. We have not made any changes to App Center Builder. We will try an upload shortly. In the meantime please note that the apple ios dev center has been down all day (last 6 hours). I would not be surprised if there is some relationship between the 2 issues.
Wayne,
Thanks for the info, its is getting quite frustrating, especially now that it is installing on the device fine. My only other idea was to create a new app for it but as I stated I was trying to avoid that. If it would help I can always set you up a user account on my itunes connect so you can see whats its doing. Not sure if that would give you any more info though.
Wayne,
any update on the dev center being down?
Also, do you know if you have to have xCode installed to upload the app? I am uploading the same way as I did in the past but that was a year ago and now Ive heard you must have xcode installed to upload (the mac version I am using wont let me install xcode).
No you don’t need xcode there is a stand alone application uploader, just use that, but you will need OS 10.5.3 or later to use it.
Paul
paul
thanks for clarifying, that is what I have been using, and failing with. Juts wanted to make sure they didnt change procedures…
We have not had a chance to test appstore uploads in the last couple of days. I talked to Kyle at appstoreuploader.com. He reported no issues with app uploads over the last couple of days. If you would like to sync w/ him send email to uploads at appstoreuploader dot com.
I still have not been able to update the app. But I am working on a new one that will be ready in a couple days, so I will see if I have the same problem.
Can you confirm that you are:
1) using an app store distribution certificate
2) the certificate has not expired (they are usually issued for only 12 months)Hi Cincy
Just wondering if you managed to sort it out? Just to let you know that i uploaded a app to the store today with no problems, So the Apple side is working now.
thanks
Paul
Sadly, no. I tried again last night but still got the same message. Ive kind of given up on it for a few days. Maybe this weekend I will try yet again to redo all the certifs for it.
Could it be possible that the certificate name does not match the original one for the app? Would that stop it from the signing process?
It certainly seems like its something on my side so I dont want to pay a 3rd party to upload as it seems what I am doing will work as long as I can get the certificate right.Hi CincyPlanet,
That could very well be the problem. We are religious about how we manage our confidential certs/profiles. All our data is backed up and recoverable to avoid such problems. Thus I can’t say what the issue is with itunes uploads since we have never crossed up my signing data. You might consider consulting kyle at appstoreuploader.com since he probably uploads more apps than anyone. We can only google to see if others have such problem and try to learn from their experiences.
