# Codesigndoc: Profile Export Incomplete

**URL:** <https://discuss.bitrise.io/t/codesigndoc-profile-export-incomplete/1354>\
**Category:** Builds\
**Tags:** code-signing, ios\
**Created:** [April 3, 2017, 9:39am UTC](https://discuss.bitrise.io/t/codesigndoc-profile-export-incomplete/1354 "2017-04-03T09:39:41Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![stherold](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/stherold/32/446_2.png) [@stherold](https://discuss.bitrise.io/u/stherold)\
**Post date:** [April 3, 2017, 9:39am UTC](https://discuss.bitrise.io/t/codesigndoc-profile-export-incomplete/1354/1 "2017-04-03T09:39:41Z")

</div>

# Bitrise Codesign Issue

## Description of the issue

Hi, I have the problem that just running codesigndoc and import everything is not enough to create an adhoc build with my distribution certificate. we have a newly created organization account and the provisioning is managed by Xcode 8.3. It only works when I import everything from codesigndoc and manually download the provisioning profile from apple developer and import it in bitrise. Is there a way to automate this tedious process with bitrise cli? I need to do that more often in the next days. So it would be cool to have an automated process…

---

<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 3, 2017, 9:44am UTC](https://discuss.bitrise.io/t/codesigndoc-profile-export-incomplete/1354/2 "2017-04-03T09:44:09Z")

</div>

> [@blackjacx](#):
>
> It only works when I import everything from codesigndoc and manually download the provisioning profile from apple developer and import it in bitrise.

Which prov profile do you have to download from Apple Dev Portal? Do you use separate teams for dev & distribution?

---

<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 3, 2017, 9:46am UTC](https://discuss.bitrise.io/t/codesigndoc-profile-export-incomplete/1354/3 "2017-04-03T09:46:19Z")

</div>

> [@blackjacx](#):
>
> Is there a way to automate this tedious process with bitrise cli? I need to do that more often in the next days.

Usually it’s enough to run codesigndoc once, and maybe add the additional prov profiles from Apple Dev Portal (which can be the case if you use separate teams for dev & distribution, in that case codesigndoc might not be able to find the distribution profile because it doesn’t know about it, as that’s only selected during distribution export).

Once you did this, and you have to update a Prov Profile you don’t have to run codesigndoc again, you just have to replace that one Prov Profile with the updated one.

---

<div class="post-metadata">

**Author:** ![stherold](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/stherold/32/446_2.png) [@stherold](https://discuss.bitrise.io/u/stherold)\
**Post date:** [April 3, 2017, 10:29am UTC](https://discuss.bitrise.io/t/codesigndoc-profile-export-incomplete/1354/4 "2017-04-03T10:29:07Z")

</div>

OK thanks, that roughly answers my question 😉 It would be nice if codesigndoc would download all provisioning profiles available for a team. Now I must always download the distribution certificate manually. But it works 🙂

---

<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 3, 2017, 10:56am UTC](https://discuss.bitrise.io/t/codesigndoc-profile-export-incomplete/1354/5 "2017-04-03T10:56:35Z")

</div>

> [@blackjacx](#):
>
> It would be nice if codesigndoc would download all provisioning profiles available for a team. Now I must always download the distribution certificate manually.

Definitely! We’re always thinking about enhancements, e.g. this one might also help: [Better / clearer message about what the exported signing files are for · Issue #40 · bitrise-io/codesigndoc · GitHub](https://github.com/bitrise-tools/codesigndoc/issues/40)

If you want to feel free to create a #Feature Requests, might make it easier to communicate related changes at a single place.

---

<div class="post-metadata">

**Author:** ![stherold](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/stherold/32/446_2.png) [@stherold](https://discuss.bitrise.io/u/stherold)\
**Post date:** [April 3, 2017, 11:36am UTC](https://discuss.bitrise.io/t/codesigndoc-profile-export-incomplete/1354/6 "2017-04-03T11:36:38Z")

</div>

Oh nice thank you 👍 Pro-Tip: I will try the code-signing tool from fastlane. Maybe this is able to export everything at once. And since this is open source as well, maybe you can learn something from it. Or maybe you can guide user to export everything using this tool, since it is highly maintained and used by others. Then you maybe can concentrate your resources on other tasks than the code signing part.

Cheers  
Stefan

PS: ❤️ Bitrise

---

<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 3, 2017, 11:49am UTC](https://discuss.bitrise.io/t/codesigndoc-profile-export-incomplete/1354/7 "2017-04-03T11:49:50Z")

</div>

Fastlane’s match is definitely an option, but you have to adapt/change your project to use it.

It’s up to you which one you prefer. Our tools work with any kind of Xcode project but you have to generate the profiles manually on Apple Dev Portal, the fastlane tools can automate the generation but you have to maintain a separate code signing repository and make changes to your Xcode project.

> [@blackjacx](#):
>
> Then you maybe can concentrate your resources on other tasks than the code signing part.

We’d love that, but we can’t require users to adapt to a 3rd party tool. You’re of course free to do so, if that fits your use case better.

---

<div class="post-metadata">

**Author:** ![stherold](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/stherold/32/446_2.png) [@stherold](https://discuss.bitrise.io/u/stherold)\
**Post date:** [April 3, 2017, 12:16pm UTC](https://discuss.bitrise.io/t/codesigndoc-profile-export-incomplete/1354/8 "2017-04-03T12:16:04Z")

</div>

Oh thats a good point! Thank you! This feedback helped a lot 🙂  
Keep On Rocking 👍

---

<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 3, 2017, 12:17pm UTC](https://discuss.bitrise.io/t/codesigndoc-profile-export-incomplete/1354/9 "2017-04-03T12:17:17Z")

</div>

Thanks, we definitely will - keep the feedback comin’, it helps tremendously!! 😉
