# Xcode 9 archiving failure - Code Signing Error: No profiles for ‘x’ were found

**URL:** <https://discuss.bitrise.io/t/xcode-9-archiving-failure-code-signing-error-no-profiles-for-x-were-found/2881>\
**Category:** Builds\
**Tags:** ios\
**Created:** [October 2, 2017, 6:47pm UTC](https://discuss.bitrise.io/t/xcode-9-archiving-failure-code-signing-error-no-profiles-for-x-were-found/2881 "2017-10-02T18:47:04Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![trick14](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/trick14/32/819_2.png) [@trick14](https://discuss.bitrise.io/u/trick14)\
**Post date:** [October 2, 2017, 6:47pm UTC](https://discuss.bitrise.io/t/xcode-9-archiving-failure-code-signing-error-no-profiles-for-x-were-found/2881/1 "2017-10-02T18:47:04Z")

</div>

# Bitrise Build Issue Report template

## Description of the issue

Archiving step fails with the log below:

> Code Signing Error: No profiles for ‘com.fishtrack.app’ were found: Xcode couldn’t find any iOS App Development provisioning profiles matching ‘com.fishtrack.app’. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild.

> [Log in - Bitrise](https://www.bitrise.io/build/e82a99ff841fe8ef)

## Environment:

Certificate And Profile Installer v1.9  
App Store Archive 2.3.2: auto-detect

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [October 4, 2017, 8:18am UTC](https://discuss.bitrise.io/t/xcode-9-archiving-failure-code-signing-error-no-profiles-for-x-were-found/2881/2 "2017-10-04T08:18:16Z")

</div>

Thanks for reporting @trick14, our dev team is looking into this! 🙂

---

<div class="post-metadata">

**Author:** ![dseither\_pg](https://avatars.discourse-cdn.com/v4/letter/d/96bed5/32.png) [@dseither\_pg](https://discuss.bitrise.io/u/dseither_pg)\
**Post date:** [October 4, 2017, 9:16am UTC](https://discuss.bitrise.io/t/xcode-9-archiving-failure-code-signing-error-no-profiles-for-x-were-found/2881/3 "2017-10-04T09:16:12Z")

</div>

I have the same issue, with build [https://www.bitrise.io/build/2dabdf8be6dbf6d1](https://www.bitrise.io/build/2dabdf8be6dbf6d1)

I already tried to replace the generated `export_options.plist` by the plist generated by Xcode (with automatic signing), but the error is still there. The profile that Xcode cannot find is definitely installed (see top of log) and is used sucessfully when archiving with Xcode on my dev machine.

---

<div class="post-metadata">

**Author:** ![dseither\_pg](https://avatars.discourse-cdn.com/v4/letter/d/96bed5/32.png) [@dseither\_pg](https://discuss.bitrise.io/u/dseither_pg)\
**Post date:** [October 4, 2017, 9:22am UTC](https://discuss.bitrise.io/t/xcode-9-archiving-failure-code-signing-error-no-profiles-for-x-were-found/2881/4 "2017-10-04T09:22:33Z")

</div>

It works when using the `export_options.plist` that Xcode generates when doing an export with manual signing. I’m trying to narrow it down to the necessary settings that are missing from Bitrise’s generated plist.

---

<div class="post-metadata">

**Author:** ![dseither\_pg](https://avatars.discourse-cdn.com/v4/letter/d/96bed5/32.png) [@dseither\_pg](https://discuss.bitrise.io/u/dseither_pg)\
**Post date:** [October 4, 2017, 11:01am UTC](https://discuss.bitrise.io/t/xcode-9-archiving-failure-code-signing-error-no-profiles-for-x-were-found/2881/5 "2017-10-04T11:01:37Z")

</div>

If I take the Bitrise-generated plist and add `<key>signingStyle</key><string>manual</string>`, it works. The isse is that according to `xcodebuild -help`, the `provisioningProfiles` key is ignored if `signingStyle` is not `manual`.

---

<div class="post-metadata">

**Author:** ![trick14](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/trick14/32/819_2.png) [@trick14](https://discuss.bitrise.io/u/trick14)\
**Post date:** [October 4, 2017, 10:07pm UTC](https://discuss.bitrise.io/t/xcode-9-archiving-failure-code-signing-error-no-profiles-for-x-were-found/2881/6 "2017-10-04T22:07:07Z")

</div>

Check out this

> [Xcode 9 GM - Failed to create target code sign properties mapping, error - #45 by viktorbenei](http://discuss.bitrise.io/t/xcode-9-gm-failed-to-create-target-code-sign-properties-mapping-error/2705/45)

You will find enough info which Bitrise is missing.

---

<div class="post-metadata">

**Author:** ![godreikrisztian](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/godreikrisztian/32/22_2.png) [@godreikrisztian](https://discuss.bitrise.io/u/godreikrisztian)\
**Post date:** [October 6, 2017, 7:39pm UTC](https://discuss.bitrise.io/t/xcode-9-archiving-failure-code-signing-error-no-profiles-for-x-were-found/2881/7 "2017-10-06T19:39:14Z")

</div>

Hi,

sorry for the issues with the `Xcode Archive & Export for iOS` step and thanks for all the reports, and lettings us test with your projects.

We released a new version ([2.3.3](https://github.com/bitrise-io/steps-xcode-archive/releases/tag/2.3.3)) of `Xcode Archive & Export for iOS` step.

Changes:

- fixed scheme - application target mapping
- fixed target - provisioning profile mapping
- handle if archive used NON xcode managed profile
- prefer archive team, if multiple code sign groups found

Please also update the Certificate and Profile Installer step to the new version: [1.9.1](https://github.com/bitrise-io/steps-certificate-and-profile-installer/releases/tag/1.9.1).

---

<div class="post-metadata">

**Author:** ![trick14](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/trick14/32/819_2.png) [@trick14](https://discuss.bitrise.io/u/trick14)\
**Post date:** [October 9, 2017, 6:29pm UTC](https://discuss.bitrise.io/t/xcode-9-archiving-failure-code-signing-error-no-profiles-for-x-were-found/2881/8 "2017-10-09T18:29:22Z")

</div>

It is not fixed in the latest version of steps.

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [October 10, 2017, 1:53pm UTC](https://discuss.bitrise.io/t/xcode-9-archiving-failure-code-signing-error-no-profiles-for-x-were-found/2881/9 "2017-10-10T13:53:18Z")

</div>

@trick14 please include the build’s log / url and we’ll check it ASAP!

---

<div class="post-metadata">

**Author:** ![godreikrisztian](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/godreikrisztian/32/22_2.png) [@godreikrisztian](https://discuss.bitrise.io/u/godreikrisztian)\
**Post date:** [October 12, 2017, 8:43am UTC](https://discuss.bitrise.io/t/xcode-9-archiving-failure-code-signing-error-no-profiles-for-x-were-found/2881/10 "2017-10-12T08:43:14Z")

</div>

It seems seems the source of the issue was a missing provisioning profile. Even if you use `Automatically manage singing` in your project you need to upload the managed profile to archive successfully.

---

<div class="post-metadata">

**Author:** ![dseither\_pg](https://avatars.discourse-cdn.com/v4/letter/d/96bed5/32.png) [@dseither\_pg](https://discuss.bitrise.io/u/dseither_pg)\
**Post date:** [October 17, 2017, 10:58am UTC](https://discuss.bitrise.io/t/xcode-9-archiving-failure-code-signing-error-no-profiles-for-x-were-found/2881/11 "2017-10-17T10:58:53Z")

</div>

Thanks! I removed our custom `export_options.plist` content after upgrading to the new step versions and it works as expected 🎉
