I'm receiving the error message that I think another user received - that my bundle was not signed using an Apple submission certificate:
I'm using the correct certificates and mobile provisions that we have used in the past and have checked that they are not expired etc. I've updated the Signing Tool to 3.0 and have also installed the latest Application Loader. Am I missing something?
I did a web search of this error and a couple different forums suggested changing the trust settings of the "Apple Worldwide Developer Relations Certificate Authority" from "Always Trust" to "Use System Defaults." That is done in the KeyChain app.
Hm. Mine was already set to Use System Defaults. I'm working with Customer Service and will update if I get it resolved. It's just odd that I have never had this error with the DPS Classic apps I have uploaded using the exact same certificates.