Shulou(Shulou.com)06/03 Report--

Invalid Signature-Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target.

Signature error is a very normal problem, which is usually caused by forgetting to change the signature when publishing app. This problem can be easily solved in the xcode3 era. But I have come across it twice on xcode4. It's really depressing. All the certificates that are not used this time are deleted according to what is said on the Internet, which can be solved in general. But it's not a big deal, huh? Especially when maintaining several app at the same time, we can't do this every time. After some efforts, we finally understand how to solve this problem thoroughly on xcode4, and write down the steps to solve it.

First of all, make sure that all the places where signatures appear here are the app signatures you want to submit, such as the above picture. Although the signatures behind Debug and Release are official signatures, the signatures used by Any SDK and Any IOS SDK are not formal, so they have been modified correctly.

Secondly, when packing, pay attention to whether the signature file followed by identity is to be used.

Basically, these two places are confirmed, so I said byebye to Invalid Signature.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.