I am trying to archive my app to submit to the app store. I have tried every single advice on this topic, but I still can't seem to get rid of the following error:
Archive submission failed due to the issues listed below.
ERROR ITMS-90046: "Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value '*' for key 'com.apple.developer.associated-domains' in 'Payload/FeedTheTribe7.app/FeedTheTribe7' is not supported."
I would appreciate any help.
Go to Dev Center > App Id > remove associated domains check
Sometimes the reason given below is also responsible for this error
If you install provisioning profile before installing distribution certificate cause this error
To solve this error, remove provisioning profile and reinstall it, will solve your problem.
If this problem still occuring, I removed all provisionning profiles listed as invalid and I reuploaded it and it worked fine.
See this conversation for different solutions but only the solution listed above worked for me.
https://forums.developer.apple.com/thread/12758
Please make sure that the version number in iTunes Connect is same as the app's version number given in Xcode.
Related
I'm getting dreaded errors like this:
ERROR ITMS-90164: "Invalid Code Signing Entitlements. The entitlements
in your app bundle signature do not match the ones that are contained
in the provisioning profile. According to the provisioning profile,
the bundle contains a key value that is not allowed:
'XXXXXXXX.com.xxxxxx.xxxxxx.xxxxx' for the key
'application-identifier' in
'Payload/XXXXX.app/Frameworks/Zip.framework/Zip'"
and this
ERROR ITMS-90046: "Invalid Code Signing Entitlements. Your application
bundle's signature contains code signing entitlements that are not
supported on iOS. Specifically, value 'development' for key
'aps-environment' in
'Payload/XXXXX.app/Frameworks/iOSDFULibrary.framework/iOSDFULibrary'
is not supported."
And it only happens when archiving and uploading to the appstore. Development on a physical device works just fine.
I already tried everything on this post without success ERROR ITMS-90164/90046: Invalid Code Signing Entitlements
My specific scenario is that the errors are happening on manually installed Frameworks, while the Cocoapods frameworks seem to be fine.
I just also noticed this which made me come and create the question. Right before uploading the build to the App Store, on the final summary page, I noticed that Cocoapods frameworks look like this:
While the problematic frameworks (non cocoapods) look like this:
Those extra entitlements look like are to blame, but I can't figure out how to remove them.
EDIT Aug 3:
Just wanted to add that I found official documentation about entitlements troubleshooting here here and here
But it all talks about the app itself and not the frameworks.
Can anyone help me figure this out?
Thank you
I am facing similar issue for my app. I have used xcode10.1 to generate xcarchive and upload ipa from xcode instead of using application loader.
ERROR ITMS-90164/90046: Invalid Code Signing Entitlements has multiple solutions.
I've been trying to upload a version of my game to the AppStore for the past two days.
I keep getting the following errors:
ERROR ITMS-90164: "Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: 'true' for the key 'get-task-allow' in 'Payload/Game.app/Game'"
ERROR ITMS-90179: "Invalid Code Signing. The executable 'Payload/Game.app/Game' must be signed with the certificate that is contained in the provisioning profile."
Using FlashDevelop, Air 19.0 (since the latest problems in AIR 20.0 - 21.0).
I haven't included the get-task-allow tag in my application.xml, I've doubled checked my certificates, provisioning profiles etc., and even recreated them - but nothing seems to make it work...
Feels like a certificates issue to me, but I can't find the problem.
I had the error ERROR ITMS-90164: "Invalid Code Signing Entitlements" with key get-task-allow and I simply did both a Clean and Clean Build Folder, and I was able to upload to the App Store with no problems. Interestingly enough, I had done a validation on the problematic ipa before and it passed App Store validation, but failed on the actual upload after the file was uploaded.
I had the same problem and solved with a simple Product -> Clean.
In your app descriptor xml try adding the entitlement for get-task-allow.
<iPhone>
<Entitlements><![CDATA[
<key>get-task-allow</key><false/>
]]></Entitlements>
<!--
<Entitlements>
</iPhone>
And yes it does sound like you are mixing up certificates and profiles somewhere along the line.
Are you sure you are using an AppStore profile? (i.e. not AdHoc or development).
Yes - I'm using an AppStore profile.
After some trials, I've deleted all certificates, mobile provisions etc. and re-created them. I've followed this advice as well:
ITMS - 90179 Invalid Code Signing / ITMS - 90209 Invalid Segment Alignment
And it's working now. Apple voodoo...
I want to distribute my app, but when I run it it shows me message:
The entitlements specified in your application’s Code Signing Entitlements file do not match those specified in your provisioning profile. (0xE8008016).
I already watch my distribution account and Capabilities in Xcode and
entitlements in them are the same. In what can be problem?
I also get this exception few times when I did something with provisioning profiles or capabilities, In my case its always in iCloudkit (xcode 6) issue, for some reason in app id (if you check in developer center) it assigned invalid or unwanted icloud containers to the app id. So i remove them and only added one correct container to fix this issue.
I had this problem recently, You will find many questions here with the same issue, check this question for the approved answer The executable was signed with invalid entitlements (iPhone build)
For me, I didn't do this. I tested the app on the device using the development certificate and the ad-hoc one, Then submitted it using the disruption certificate after making sure that there is nothing wrong with my certificates.
You probably need to check your Bundle ID value in both your .plist file and also here:
(This really is the most developer-unfriendly environment in use in 2016...)
I am trying to archive a new app, but when I do that I get this error:
Code Sign error: Provisioning profile 'BusinessIdeaLive' specifies the Application Identifier 'com.problemio.businessidea' which doesn't match the current setting '4MS3885ZWL.com.problemio.businessidea'
So I understand that there is a mis-match of '4MS3885ZWL.com.problemio.businessidea' and com.problemio.businessidea
But in the certificates I made, and my plist I have the '4MS3885ZWL.com.problemio.businessidea' so I am not sure why this error is happening. Any idea why the error occurs and how I can fix it?
Thank you!
Your plist should only contain "com.problemio.businessidea", without the 4MS3885ZWL prefix.
I had the same error. I restarted the xCode.
Selected proper provisional profile in both target and build settings and archived again solved the problem.
The app I'm currently working on was originally developed by someone else on another mac and has several provisioning profiles linked to it. I made a new provisioning profile about a month ago to test on the same device the original developer tested on and everything was working fine. Since the past couple of days I have received this error when running the app on a device:
NSUbiquitousKeyValueStore error: com.companyname.appname has no valid com.apple.developer.ubiquity-kvstore-identifier entitlement
I researched this error and came to the conclusion that my entitlements were wrong in some way. I then discovered they were turned off which is something I did to get the new provisioning profile to work on the device. I turned the entitlements on again and got this familiar error:
The executable was signed with invalid entitlements ... (0xE8008016).
I've tried a lot of suggestions from various sources on the internet to solve this problem but none of them seemed to work, which is why I originally turned the entitlements off (the one suggestion that worked).
The provisioning profile I created is listed as valid under the devices' provisioning profiles tab. There are 4 other provisioning profiles which are only listed in the libraries' provisioning profiles tab.
Can an app be uploaded to the store without an entitlements file?
Can the final distribution of the app and upload of the binary be conducted and the NSUbiquitousKeyValueStore error: won't be present?
Can anyone give me a fairly comprehensive step by step guide to completely removing the link between the old provisioning profile and the current entitlements or a way of changing the entitlements file to work with the current provisioning profile?
I am aware this sort of error is pretty hard to diagnose and solve but any help is appreciated.
I discovered the source of my problem to be that the provisioning profile I was trying to sign the app to had a wildcard* appID so therefore would not match. A pretty stupid error but one possibly other people may encounter.