iOS code signing fails: "A sealed resource is missing or invalid."

I just experienced this error trying to sign an archive with Xcode 4 on Lion. The problem turned out to be related to the fact that the archive had been zipped on one machine and transported to another --- the zip utility did not support symbolic links, and the app code signature uses a symlink inside the bundle, so the unzipped archive was invalid.

Possible solutions are:

1. Use the Finder's contextual (ctrl-click/right-click) menu and choose "Compress" to create the zip file, or:
2. Use the command line version of zip and provide it with the -y argument to preserve symbolic links.

Apple's new APFS file system has some bugs to process unicode characters and it is causing the issue.

Moving the whole project to the legacy MacOS Extended volume and archiving again solved the issue.

This isn't a specific answer I'm afraid, but something you may not have thought about.

From your command line snippet, it looks like you're code signing your app bundle after it's been built. Are you moving the bundle (.app folder or maybe an IPA or ZIP file) from another machine, or from another drive? I've had problems with moving app bundles between file systems that don't support symbolic links properly. Are you using a network drive, or have a local drive that's not formatted for Mac OS.

Solved. The problem was a '?' character on the product name. Shouldn't be like that but that's how it is. Nowhere apple says that that makes a codesign verification issue.