- This topic has 18 replies, 6 voices, and was last updated 11 years, 7 months ago by
.
-
Posts
-
Just when you think you’ve cracked it and everything is wonderful apple slaps you back down. I submitted an app to iTunes and it was accepted just last week, I had a few bugs and needed to update so I did everything as before. All was good till I tried to upload the updated .IPA file to iTunes with Application Loader on my Mac I was hit with this:
“Application failed codesign verification. The signature was invalid, contains disallowed entitlements or it was not signed with an iPhone distribution certificate.”
I used exactly the same settings, same provisioning profile, same distribution certificate as before but alas no joy… has anyone experienced this?
Hi stickleback,
Could you please try to rebuild your app? During the process record the build number. Then, if you have the same problem uploading to the app store please send us the build #
I’ve had this happen before. Just go into the provisioning tool, redo your certificate and recompile. Will take you as long as it took to write that post.
Apple isn’t evil, they just have a process. Follow the process and you make money. Easy. My sixth app has just gone live. Never had an app rejected yet. Follow the process.
https://itunes.apple.com/us/app/proximal/id572222453?ls=1&mt=8
@1thinchip Thanks for your post but could you actually explain what you mean by redo your certificate? Do you mean request a new one or what?
Yeah, when this has happened to me, it just meant that the certificate had expired. (I’m assuming there’s nothing else terribly wrong with your app.) Go into the Apple provisioning portal, delete the existing App Store Distribution certificate, request a new one associated with that package. Download and recompile and see what happens. Good luck!
-1TC
Re Build#: 1656040
I have rebuilt the app and am still unable to upload the updated .ipa file to Apple for the reasons stated before, my distribution certificate is still current and I had no problems uploading the original .ipa file that was accepted by Apple and is on sale now. I am out of ideas on how to fix this, many solutions are available if you program in X-code, M1 is much easier to use so please can you help. One strange thing I did notice, the prov-profile I used for this app was for the app store only with no devices, how come I was still able to install it on my iphone and have it working perfectly.
dear friend i am having the same issue, and opened another topic:
http://www.genuitec.com/support-genuitec/viewtopic.php?f=19&t=5311any success?
Got any ideas??Thanks
@Macauba, I am at a loss to understand what is going on, I have the app working perfect on my iphone5 but get errors when I try to upload the .ipa to iTunes. I am hoping support will give me the answers. Meanwhile if you figure it out please let me know.
@stickleback,
The dev team is investigating this issue and hope to have some news for you by the end of the week, maybe sooner.
@stickleback,
I´ve tried everything, even revoking certificates and recreating them, creating a new Distribution Provisioning Profiles, but no success, my app works fine on my iPhone 5 also via adhoc, but when i try to upload i get the same error you got.
But what is driving me mad is that the first version uploaded fine, but this version 1.1, using the same certificates gave me errors.Hi stickleback, macauba,
We’ve checked [re]submission of apps built with MobiOne 2.3.1 to iTunes Connect via Application Loader and it works fine.
Please make sure
– that you’re using AppStore distribution provisioning profile;
– you’re using the same bundle id as for first application version;
– you are using correct AppIdThere are more requirements from Apple on apps being submitted not for the first time. You can find more information here: https://developer.apple.com/appstore/resources/submission/index.html and here: https://developer.apple.com/support/resources/itunes-connect.html
