I am trying to upload a signed ipa file to the app store but I keep receiving an error message saying:
ITMS-90035: Invalid Signature - A sealed resource is missing or invalid. The file at path [Inuttut.app/Inuttut] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate.
I'm building the app with Cordova/Ionic 3. I have a valid Distribution signing certificate and provisioning profile for the app. I have triple checked that the bundle id is correct, and I have also set the Xcode build to use the legacy build.
One thing that has me wondering is that when I'm in Xcode and select "Automatically manage signing" it sets my signing certificate to iPhone Developer instead of iPhone Distribution. Signing the app this way and uploading it produces the same error as unchecking "Automatically manage signing" and manually selecting the iPhone Distribution certificate.
I found the problem. Frustratingly, it had nothing to do with my distribution certificate or anything like that, so kudos to Apple for the wild goose chase. It was simply because I have some assets which have non-ASCII characters in the filename. This is exactly the kind of linguistic bias that makes developing software for non European languages difficult. In any case, I recommend looking for any files like that - hopefully my pain and suffering over the past few days will help somebody else.
P.S contacting Apple directly was a fruitless and infuriating experience, so don't bother.
I have the same problem, and fix by suggestion in your answer. But I want to provide some more detail to make it more clear
For me this problem was fixed by changing Product Name from our local unicode name to ascii english name
Keep in mind that Product Name differs from Display Name which is displayed below app icon as your app name. So don't worry about changing Product Name requires change your app name, just choose an ascii name and error gone
I am in the process of submitting my first Ionic application to the store. However I am receiving an error every single time that I try to submit my binary to the store:
Invalid Signature - A sealed resource is missing or invalid. The binary at path [Who Paid Last?.app/Who Paid Last?] contains an invalid signature. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate....
I have verified that my certificates are correct. I have even tried moving my .git folder outside of the directory, but still no luck. I have tried about 7 different configurations and still the same result time and time again.
The crazy thing is that after my archive has been built, I validate using XCode's validator. The validator says that my .ipa has zero errors and that it is ready for submission, but iTunes Connect says differently.
I have also tried following this tutorial on troubleshooting but without any luck.
The issue had to do with the name of my app. The name of my application is Who Paid Last?, and come to find out, the "?" in the name is what was causing the issue. As soon as I removed it, the app was submitted just fine with out any issues.
I had a similar issue, but my error message was "Invalid Signature. Code object is not signed at all. The binary at path [myApp.app/www/js/02_jshint.js] contains an invalid signature...."
Deleting the #!/usr/bin/env directive from the top of my 02_jshint.js file, then building the iOS version of your project from the CLI worked for me.
As described in this SO entry, I am getting errors in iOS app Application Uploader.
These are the values I have:
in KeyChain I have this certificate:
iPhone Distribution: ExampleCompany (DistCertificateID)
In my developer.apple.com account I have defined app:
Name: LongReadableName
Prefix: DistCertificateID
ID: com.example.*
Name: Xcode iOS Wildcard App ID
Prefix: DistCertificateID
ID: *
These are the errors I am getting:
This bundle is invalid. The application-identifier entitlement is not
formatted correctly; it should contain your 10-character App ID Seed,
followed by a dot, followed by your bundle identifier:
0000000000.appname
and
The Bundle ID DistCertificateID.appname defined in your Xcode Project
does not match the Bundle ID that you entered for this app in iTunes
Connect appname.
Above has let me to conclude I possible submitted the app incorrectly (?) to iTunesConnect since that is the only conclusion that makes any sense to me.
(For reference, and if I understood everything correctly, I believe both the specific and wildcard app ID is appropriate for me since I do not need to use inapp-purchases or anything like that.)
When submiting an app in iTunesConnect I can choose between
Xcode iOS Wildcard App ID - *****
LongReadableName - com.example.*
I am completely lost on how I can ever choose a BundleID / BundleID Suffix that obeys both what is written in iTunesConnect (?) and the errors I am getting in Application Uploader right now. Could anyone point me to values I could use that would not collide with Application Uploader requirements?
...
Newest update #1
I decided to drop using wildcard app IDs since I can see that has caused other people problems. Hence I chose the other option in iTunesConnect resulting it in showing me BundleID as being com.example.appname. I then made sure 1) my provisioning for distribution used DistCertificateID.com.example.* 2) to set CFBunldeIdentifier (in Delphi) as same shown in iTunesConnect. I then built and deployed followed by submitting it to Application Loader. That resulted in error message:
The Bundle ID com.example.appname defined in your Xcode Project
does not match the Bundle ID that you entered for this app in iTunes
Connect com.example.appname.
As you can see, the bundle ID is now the same, but still it complains. I do not understand why :(
Newest update #2
I actually made a small typo error last night when I tried above. Guess I was too tired. Above solution works! (I will make it an answer.)
Ditching the wildcard app ID worked for me. Hence I chose the other option in iTunesConnect resulting it in showing me BundleID as being com.example.appname. I then made sure 1) my provisioning for distribution used DistCertificateID.com.example.* 2) to set CFBunldeIdentifier (in Delphi) as same shown in iTunesConnect. I then built and deployed followed by submitting it to Application Loader.
This is the error I'm getting when I try to install my app on my iPhone.
More details:
It did work at one point. I used a different computer recently, working on a different project and had to create a new certificate. This invalidated my other projects (profiles). I went back to working on the first computer and uploaded the certificate from that one. I recreated the app profiles and downloaded the provisioning files based on that previous certificate. None of that worked. In the end I had to start over from scratch as shown in the answer below.
I finally got it to work by starting over from scratch. I think the problem was that when I went to a new computer and uploaded a new certificate I had to revoke the old certificate. It seems that once it's revoked that maybe it can't be used again.
So I recreated my signing certificate, recreated a p12 file from it, recreated (modified) the app profile (making sure to select my certificate again and selected all of my devices again), redownloaded the mobile provisioning file, reselected these in the iOS configuration screen and restarted Flash Builder and it worked again.
I had tried to use a wildcard, "com.myactualdomainhere.*" and I couldn't get that to work but I didn't do all the steps above (I didn't recreate my signing certificate) and if you can't reuse a certificate then that may have been the issue.
So I did all the steps above and used the app name, "com.myactualdomainhere.MyApp" and made sure it matched in the application descriptor file (for AIR apps) com.myactualdomainhere.MyApp.
It would be nice if someday they could simplify this process and give better error messages. Maybe they could verify the different parts along the way, for example, "your certificate is ok, your app profile checks out, but your app id is incorrect."
Also, MilkyWay posted a link to a post that has some more helpful information.
I experienced this error working with code from another vendor. As it turns out, they were trying to compile the IPA with an Entitlements.plist file. I just deleted that block of code (below) and it compiled just fine.
<Entitlements>
<![CDATA[
<key>get-task-allow</key>
<true/>
]]>
</Entitlements>
I've just been stuck with this problem this morning, took a while to figure out so thought I'd post incase anyone else has the same issue.
We had a problem adding a device to our provisioning profile, an iPhone 5 on iOS7. It turned out that the application we were using to get the UDID (UDID+) was giving us the wrong UDID. When I used the ID returned by
adt -devices -platform ios
It worked.
In my case it was at matter of unaccepted characters in some embedded folders. Folder names that contained special characters (æ ø å or whitespace) resulted in an ApplicationVerificationFailed error. (Not exactly the most precise error description I have encountered.)
I know this is an old thread, but if anyone else is Googling around and finds this thread and it does NOT fix your issue, I wanted to share my experience on this one. If you've confirmed that your certificates and provisioning profiles are all good and are still getting this, I determined that you will receive this exact same error if you have your app configured for TESTFLIGHT. In other words, in your APPNAME-app.xml make sure that the following is commented out within the IOS entitlements section:
<key>beta-reports-active</key>
<true/>
Once I commented that out, I was able to resume debugging locally. Pissed that I spent a day on this, but at least it's working now.
This can also happen if you change your Apple ID password.
My problem was that in my Application ID under apple developers, my app wasn't checked for PushNotification, but within my xml application descriptor, I had the entitlments for push notifiaction (aps_development).
Once à removed the APS value from my XML, worked all good.
If you haven't compiled in a long time, be sure you set your compilation settings to device testing and make sure you are using your testing provisioning profile. I got this today because my settings were still on app store.
The problem for me was that I was using a .p12 file which was meant for Apple Push Notifications instead of the .p12 file of my Developer certificate..
I used the .p12 I exported from my developer certificate and it works great..!
In my case it was incorrect application id problem (different compiled app id then app id I have defined apple)
sometimes this error occurs because of you bin-debug folder.
if that folder has some unknown character or something this error occurs.
I suggest if in that case you have to clean the project or find that file and change it's name
If it was working previously, just restart the flash builder.
I did some tests today on test flight with the Entitlements tags. It need to be remove when testing localy or I get the same error.
Like jbyun94 mentionned, get rid of unknown characters in filenames.
I had files in conflict from dropbox that prevented the app from compiling.
Removed them and everything worked again (though I'd lost a couple of hours :/)
While upgrading an existing app, I'm getting the notorious:
"The binary you uploaded was invalid. The signature was invalid, or it
was not signed with an Apple submission certificate."
I believe it is due to the fact that I am using the wrong App ID. I forgot the one I used in the original app. Is there a way to determine the original App ID? I now using xcode 4 the original app was done back in iOS 3.0 days.
If the app is available on from the store or if you still have the bundle you submitted open it up and find the binary. On the binary run
strings - appBinary | grep -A 1 application-identifier
this will show you the appID that was used.
Incidentally this didn't completely solve my problem. However closely examining the strings on the binary I was trying to submit revealed the app was being signed by my developer cert and not my distribution cert (despite the xcode settings) there fore I changed all builds to use my distribution cert's and it then worked.