Every Cocos creator Project that I export with jsb link will be rejected by iTunes connect. Uploading has no errors but 2 minutes later I receive an email saying “Invalid Signature - A sealed resource is missing or invalid. The file at path [xxxxxxx.app/binaryname] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate.” Does anyone have a hint where the problem could be. I did a lot of checks verifying code signing. All tests succeeded entitlement checking etc.
Well I suppose you could simply export it in mobile web and make a build using apache cordova. Well I said simply but its actually hard work. But I bet it will be worth it.
I’m using XCode 9. Did a full compile in XCode using Archive method and tried uploading from Organizer window. Uploading worked well and said everything is fine. 2 Minutes later my app got rejected. One Thing I recognized was that an empty project (no assets except a scene) made it all the way through to a valid binary. @jare what do you mean by publish as ipa and publish as app?
That was my first thought but I don’t understand why I can sign and upload a empty project successfully using same certificate, Provision Profile and bundle id.
Bad signing relates to the certificates itself, not cocos creator. You should check errors from Apple. I got errors for missing AppIcon assets. Cocos creator generates xcode template which doesn’t have that configuration.
For current version (1.6.2), try to fix it and god bless you!
Finally I found the Issue! I had Assets named with an space or an ä. Which seems to fail at apples server. Renaming these files solved the signing problem.
