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

Question

I have been with this problem already 8 hours unable to solve it.

Whats Cool JLD$ codesign -vvvv build/Distribution-iphoneos/Whats\\ cool\\?.app
build/Distributi         


        

Answer 1

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.

Answer 2

I passed days on this problem, for me it's because the name of the application contains arabic caracters :(, So apple on xcode 12 doesn't accept arabic caracters ? on xcode 10 i publish without any problem

it's very complicated to be a developper on ios

Answer 3

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.

Answer 4

In my case, I got that error because the disk image I created to distribute my app ran out of space and ditto did not copy all files from the build folder to the disk image. As the script I used generates so much noise, I missed the warning of ditto that it ran out of space in the target disk image. Unfortunately, ditto should have aborted the whole procedure, instead of burying the warning into a myriad of other paths of smaller files that it managed to copy.

Answer 5

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.

Answer 6

Another problem could be your app contains image file name with none English characters in your app. Such as 'ş ç ğ'. If you remove those images or change the file name it will proceed.