# Codesigndoc problems

**URL:** <https://discuss.bitrise.io/t/codesigndoc-problems/1550>\
**Category:** Builds\
**Tags:** code-signing, ios\
**Created:** [April 25, 2017, 7:06am UTC](https://discuss.bitrise.io/t/codesigndoc-problems/1550 "2017-04-25T07:06:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![david.everlof.knowit](https://avatars.discourse-cdn.com/v4/letter/d/278dde/32.png) [@david.everlof.knowit](https://discuss.bitrise.io/u/david.everlof.knowit)\
**Post date:** [April 25, 2017, 7:06am UTC](https://discuss.bitrise.io/t/codesigndoc-problems/1550/1 "2017-04-25T07:06:21Z")

</div>

Hi!

I can easily archive + export i Xcode. I’m using my developer certificate to archive, and then I export for enterprise using the certificate for that.

However, since the codesigndoc only seems to do ‘archive’ it doesnt pick up the certificate I use to sign the export for enterprise.

Can I achieve this in any way?

Regards, David

---

<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:** [April 25, 2017, 8:32am UTC](https://discuss.bitrise.io/t/codesigndoc-problems/1550/2 "2017-04-25T08:32:46Z")

</div>

> [@david.everlof.knowit](#):
>
> Can I achieve this in any way?

Absolutely! Just run `codesigndoc` and then upload any missing profiles you want to use.

In short, `codesigndoc` collects the required signing files for doing an Archive, but indeed it does not do an export. Instead it tries to find all the Prov Profiles with your project’s bundle ID, as well as the Certs related to the Team.

This is usually enough even for distribution, if you use a single Apple Dev Team. If you use a separate team for distribution then you just have to download the Prov Profile from the Apple Dev Portal and upload to [bitrise.io](http://bitrise.io), and if required the Certificate/.p12 (identity) too.

---

<div class="post-metadata">

**Author:** ![david.everlof.knowit](https://avatars.discourse-cdn.com/v4/letter/d/278dde/32.png) [@david.everlof.knowit](https://discuss.bitrise.io/u/david.everlof.knowit)\
**Post date:** [April 25, 2017, 8:48am UTC](https://discuss.bitrise.io/t/codesigndoc-problems/1550/3 "2017-04-25T08:48:21Z")

</div>

Maybe I should have phrased it as:

“Can I achieve this in any way using the `codesigndoc`?” I can’t get it to pick up what I do in Xcode when I export?

I guess the answer is no then?

---

<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:** [April 25, 2017, 9:24am UTC](https://discuss.bitrise.io/t/codesigndoc-problems/1550/4 "2017-04-25T09:24:28Z")

</div>

If you use a single Team for both development and Deployment/Distribution then it should work. Otherwise you’ll have to upload the additional files, but only those which are related to the distribution type you set (e.g. if you set the **Xcode Archive** step to use `app-store` signing, you only have to upload the app store signing files, the base / required signing files are collected by `codesigndoc`. More info about “required” signing files here: [http://devcenter.bitrise.io/ios/code-signing-technical-details/#how-ios-code-signing-works-if-you-use-xcode-8-automatic-code-signing](http://devcenter.bitrise.io/ios/code-signing-technical-details/#how-ios-code-signing-works-if-you-use-xcode-8-automatic-code-signing) )