# Xamarin Archive suddenly failing - provisioning profile

**URL:** <https://discuss.bitrise.io/t/xamarin-archive-suddenly-failing-provisioning-profile/2886>\
**Category:** Builds\
**Tags:** xcode\
**Created:** [October 3, 2017, 8:11am UTC](https://discuss.bitrise.io/t/xamarin-archive-suddenly-failing-provisioning-profile/2886 "2017-10-03T08:11:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![clintvanquis](https://avatars.discourse-cdn.com/v4/letter/c/2acd7d/32.png) [@clintvanquis](https://discuss.bitrise.io/u/clintvanquis)\
**Post date:** [October 3, 2017, 8:11am UTC](https://discuss.bitrise.io/t/xamarin-archive-suddenly-failing-provisioning-profile/2886/1 "2017-10-03T08:11:40Z")

</div>

# Bitrise Build Issue Report template

## Description of the issue

Our BitRise workflows have started failing on an entitlement issue (push notifications) - the builds were previously working OK as of the 19th September.

The short error message is:

```auto
error: exportArchive: "your.app" requires a provisioning profile with the Push Notifications feature.

```

Full message is:

```auto
$ xcodebuild "-exportArchive" "-archivePath" "/Users/vagrant/deploy/Your 9-29-17 12.57 PM.xcarchive" "-exportPath" "/var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/ __export__ 465750104" "-exportOptionsPlist" "/Users/vagrant/deploy/export_options.plist"
2017-09-29 12:58:17.300 xcodebuild[3571:20588] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/Vanquis_2017-09-29_12-58-17.295.xcdistributionlogs'.
2017-09-29 12:58:18.495 xcodebuild[3571:20588] [MT] IDEDistribution: Step failed: <IDEDistributionSigningAssetsStep: 0x7fe919881c10>: Error Domain=IDEDistributionSigningAssetStepErrorDomain Code=0 "Locating signing assets failed." UserInfo={NSLocalizedDescription=Locating signing assets failed., IDEDistributionSigningAssetStepUnderlyingErrors=(
    "Error Domain=IDEProvisioningErrorDomain Code=9 \"\"Your.app\" requires a provisioning profile with the Push Notifications feature.\" UserInfo={NSLocalizedDescription=\"Your.app\" requires a provisioning profile with the Push Notifications feature., NSLocalizedRecoverySuggestion=Add a profile to the \"provisioningProfiles\" dictionary in your Export Options property list.}"
)}
error: exportArchive: "Vanquis.Mobile.Platform.iOS.app" requires a provisioning profile with the Push Notifications feature.
Error Domain=IDEProvisioningErrorDomain Code=9 ""Your.app" requires a provisioning profile with the Push Notifications feature." UserInfo={NSLocalizedDescription="Your.app" requires a provisioning profile with the Push Notifications feature., NSLocalizedRecoverySuggestion=Add a profile to the "provisioningProfiles" dictionary in your Export Options property list.}
**EXPORT FAILED**

```

We already have the push notifications feature within the provisioning file used, and we have been actively using push notifications in our app already, so I am a little bit stumped on where the issue might lay, do we need to manually create export options? I don’t quite know why we have not had to do this before.

## Environment:

The issue happens within [BitRise.io](http://BitRise.io) - on the stack: ‘Xamarin, Visual Studio for Mac, installed on macOS 10.12 (Sierra)’

The step failing is the Export-Xcarchive step 0.9.2 (latest) - with the above error message.

We are using ‘ad-hoc’ distribution type, as the build gets exported to Hockeyapp.

## Reproducibility

- Rebuild help? : No - I even tried re-building our previously working build from the 19th, which now fails.
- Does a rebuild without caches help? : No - Not using build caches at the moment.
- If you have multiple different build configurations (workflows), does the issue affect all/more than one? : Yes, all of them.
- If it’s an issue which happens sporadically, what’s the frequency? : All builds
- Does upgrading the build Step to the latest version help? : No - already on latest step lib version
- When did the issue start? : First instance we saw it happen was Friday 27th September, trying to re-build our old build from the 19th September, which was previously working.

### Linux/Android stack builds

Not a Linux/Android build.

### Other stacks

Not attempted this, but not sure why it would make a difference as our previous builds worked O.K - and re-running them now does not work.

## Build log

Have sent the build log to Gergely yesterday, thank you.

---

<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:20am UTC](https://discuss.bitrise.io/t/xamarin-archive-suddenly-failing-provisioning-profile/2886/2 "2017-10-04T08:20:43Z")

</div>

Thanks for the issue report @clintvanquis ! Our dev team is looking into this right now! 🙂

---

<div class="post-metadata">

**Author:** ![phdesign](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/phdesign/32/928_2.png) [@phdesign](https://discuss.bitrise.io/u/phdesign)\
**Post date:** [October 26, 2017, 3:26am UTC](https://discuss.bitrise.io/t/xamarin-archive-suddenly-failing-provisioning-profile/2886/4 "2017-10-26T03:26:06Z")

</div>

Was there a resolution to this? I’m getting a similar error using xamarin-archive@1.5.0 \> export-xcarchive@0.9.2.

---

<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 28, 2017, 8:15am UTC](https://discuss.bitrise.io/t/xamarin-archive-suddenly-failing-provisioning-profile/2886/5 "2017-10-28T08:15:09Z")

</div>

@phdesign please create a new #issues:build-issues report and we’ll look into your case ASAP! 🙂
