# iOS Auto Provision v1.1.0

**URL:** <https://discuss.bitrise.io/t/ios-auto-provision-v1-1-0/5061>\
**Category:** Changelog\
**Tags:** step\
**Created:** [May 11, 2018, 9:48am UTC](https://discuss.bitrise.io/t/ios-auto-provision-v1-1-0/5061 "2018-05-11T09:48:59Z")\
**Posts on this page:** 1\
**Page:** 1

<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:** [May 11, 2018, 9:48am UTC](https://discuss.bitrise.io/t/ios-auto-provision-v1-1-0/5061/1 "2018-05-11T09:48:59Z")

</div>

We have released a new version ([1.1.0](https://github.com/bitrise-steplib/steps-ios-auto-provision/releases/tag/1.1.0)) of `iOS Auto Provision` step.

Changes:

**NEW INPUT:** `generate_profiles` - Should the step try to generate Provisioning Profiles even if Xcode managed signing is enabled in the Xcode project?

In case of **Xcode managed codesigning** projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.

If this input is set to: `yes`, the step will try to manage the Provisioning Profiles by itself ( **like in case of Manual codesigning projects** ), the step will fall back to use the Xcode managed Provisioning Profiles in case of an issue.

**This input has no effect in case of Manual codesigning projects.**