Xcode Cloud - ITMS-90166: Missing Code Signing Entitlements

Question

philippefromlondon OP

Created Mar ’22

Replies 7

Boosts 0

Views 3.1k

Participants 8

Good morning

We're happy to have access to Xcode Cloud. However, we get the following error during the "Prepare Build for App Store Connect" phase:

Archive - iOS encountered a failure that caused the build to fail.

Prepare Build for App Store Connect

ITMS-90166: Missing Code Signing Entitlements. No entitlements found in bundle 'com.***.***.iOS-NotificationService-Ext' for executable 'Payload/***.app/PlugIns/iOS-NotificationService-Ext.appex/iOS-NotificationService-Ext'.'

An entitlement is missing for our notification service extension? It is strange knowing that we can build, archive and upload to App Store Connect successfully locally from any Xcode.. It just fails with Xcode Cloud making the service sadly useless for us.

Any idea? recommendation?

Answered by chrisheinrich in 710712022

I hit this issue too, but there was an easy fix. Just add an Entitlements file to your plugin (in my case the Notification Extension) and give it some dummy capability like Associated Domains. After that it will generate an entitlements file and associate it with the target (you can go to the target's build settings and type code signing to confirm). After adding this file the archive got pushed successfully to ASC

Boost

Answer 1

Sven OP

Mar ’22

Good morning,

I don't have any solutions at the moment but we're noticing the same problem. The error occurs on all of our extension targets like Widget, Watch Extension and NotificationService/-Content. I downloaded the archive to compare it with a locally built target. It's missing the embedded.mobileprovision file in the app folder as well as in the plugins folder. So this was the only difference I could notice.

Also it doesn't change anything if you sign the app automatically - usually we use manual signing build settings.

I'm also interested in any recommendations.

Best Sven

2

Answer 2

J0hn OP

Mar ’22

Hey, me too! My guess is it's a passing validation bug with the beta. Could be worth submitting a feedback for, though.

2

Answer 3

chrisheinrich OP

Apr ’22

Accepted Answer

I hit this issue too, but there was an easy fix. Just add an Entitlements file to your plugin (in my case the Notification Extension) and give it some dummy capability like Associated Domains. After that it will generate an entitlements file and associate it with the target (you can go to the target's build settings and type code signing to confirm). After adding this file the archive got pushed successfully to ASC

2

Answer 4

chrisheinrich OP

Apr ’22

I hit this issue too, but there was an easy fix. Just add an Entitlements file to your plugin (in my case the Notification Extension) and give it some dummy capability like Associated Domains. After that it will generate an entitlements file and associate it with the target (you can go to the target's build settings and type code signing to confirm). After adding this file the archive got pushed successfully to ASC

0

Answer 5

stephenbrown90 OP

May ’22

We have been seeing the same issue for over a month now.

Has there been any progress on this? Feedback assistant has not provided any responses.

I don't feel like adding a dummy entitlement to our widget and intent is a great solution.

0

Answer 6

DTS Engineer OP

Apple

May ’22

Feedback Assistant has not provided any responses.

What was your bug number?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 7

DTS Engineer OP

Apple

May ’22

This is resolved if the Xcode Cloud workflow uses Xcode 13.4. This Xcode update was released earlier this week. If you continue to see this, please update your report in Feedback Assistant, and please post the FB number here.

0