Apple Store submit fails with Error ITMS-90046, but Associated Domains is not among entitlements

Question

When I first built my app & Watchkit app, I had the \"Associated Domains\" capability enabled. I\'ve disabled it in the \"Capabilities\" panel of both the watchkit exten

Answer 1

To fix this issue:

• log into Apple Deveveloper Center
• Go to Certificates, Identifiers & Profiles.
• Go to Identifiers/App IDs.
• Select your App ID and Edit
• Uncheck Associated Domains
• Save

You will have to regenerate any provisioning files associated with the App ID. For some reason the "Associated Domains" got checked for my app. Deselecting it made the AppStore submission work.

Answer 2

As other stated in ERROR ITMS-90164/90046: Invalid Code Signing Entitlements I was able to solve the issue by performing Clean build. For the record, I was getting error code ITMS-90164.

Answer 3

• Was getting: "The executable was signed with invalid entitlements" messages
• Searching with Google gave some useful hints, but the ^ message did not stop
• Went to: Xcode > Window > Devices
• Then: At the lower left-hand corner of the Devices Window I selected the "Show the device console" button
• Starting from the button of the log I scanned the information and found the problem and fixed it in a short amount of time
• In my case it involved com.apple.developer.associated-domains entitlements, and I needed to keep associated-domains
• I will use the device console in the future whenever there are device error messages, what a time saver
• Solved the problem in a short amount of time
• BTW, THANK YOU all for your help

Answer 4

I think this is a bug.

I managed a workaround by simply inserting a new Array item in the Entitlements.plist of both the companion app and the Watchkit extension: "com.developer.apple.associated-domains" and a valid domain for the webcredentials: string. While this will have no practical effect as neither my provisioning files nor the Capabilities tab of the app or extension are enabled for associated domains, it stopped whatever code scanner at itunesconnect was tripping over an invalid value of "*" for the non-existent key.

Answer 5

If you want to use associated-domains, make sure each entry in Entitlements.plist > com.developer.apple.associated-domains uses the following format:

<service>:<fully qualified domain>[:port number]

eg.

webcredentials:www.example.com
applinks:www.example.com
activitycontinuation:www.example.com

Keep in mind [:port number] is optional, but <service> and <fully qualified domain> are required!

Answer 6

From the App submission failed errors what I understand is possibly your provisioning profile still have the "associated-domains" enabled and its missing in your application "entitlements" file.

So obviously there will be two scenarios.

Scenario 1: Do you want to support "associated-domains". This should be enabled for features like "Universal Links".

Please refer the following link:

https://developer.apple.com/library/content/documentation/IDEs/Conceptual/AppDistributionGuide/AddingCapabilities/AddingCapabilities.html

In this case please don't manually edit your "entitlement" file. Instead follow the steps.

1. Select your project file in Xcode.

2. Select appropriate Target under "Targets"

3. Select "Capabilities" which is next to "General"

4. You can see an option for "Associated Domains" as given below.

5. Enable "Associated Domains". If you enable "Associated Domains" Xcode will ask you to login to the Developer account and it will be in sync with your AppId and Provisioning profile.

As mentioned in the above screenshot it will do two things while enabling "Associated Domains"

• Add the Associated Domain entitlement to your entitlements file.
• Add the associated Domain feature into your App ID.

If there is any issue in syncing your settings from Xcode and Developer account , please check the following checkbox is enabled.

Also make sure that your , In House and App Distributions provisioning profiles are properly updated and in sync.

Most the work will do by Xcode itself, we just needs to listen and understand.

Scenario 2: Your App don't need the "Associated-Domain" capability. In this case , Please follow the Answer given by @Ciprian Rarau. Its well explained.