Signature is a relatively simple case, and obviously the problem lies in the signature part. CodeResources stores the paths and hash values of all resource files in the package, and the whole package also has an overall hash value. This file can check whether the package received by Apple (or the package received by users) is complete or damaged. Of course, the fault packet will not be further processed. Collaborative design will include. * Hide files when signing the package, but Xcode will not copy such files into the target package when packaging. Perhaps the Xcode tool chain thinks that the signature is automatically generated by the program and the user will not intervene manually, so it must be reliable and has not been verified by CodeResources before submission.