# Auto provisioning with new bundle identifiers

**URL:** https://discuss.bitrise.io/t/auto-provisioning-with-new-bundle-identifiers/21184
**Category:** iOS
**Created:** [September 22, 2022, 12:11pm UTC](https://discuss.bitrise.io/t/auto-provisioning-with-new-bundle-identifiers/21184 "2022-09-22T12:11:08Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![stephen.bradshaw](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@stephen.bradshaw](https://discuss.bitrise.io/u/stephen.bradshaw)
#### Post date: [September 22, 2022, 12:11pm UTC](https://discuss.bitrise.io/t/auto-provisioning-with-new-bundle-identifiers/21184/1 "2022-09-22T12:11:08Z")

</div>

For an internal build test workflow, we have tried setting the bundle identifier of our app using the `Set iOS Info.plist - Bundle Identifier` workflow step.

This is to create an ID `<app-bundle>.test` so as to make a unique test bundle. This is a registered and valid bundle ID on our Apple developer account.

I can see the Info.plist is updated correctly. However, the auto provisioning step within `Xcode Archive & Export for iOS` still attempts to sign it with the original bundle identifier found inside `project.pbxproj` \> `PRODUCT_BUNDLE_IDENTIFIER`.

I had expected a new provisioning profile to be created for the new bundle from Info.plist. Is there anything I could be doing incorrectly?

Many thanks.

---

<div class="post-metadata">

### Author: ![damien.murphy](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/damien.murphy/32/4535_2.png) [@damien.murphy](https://discuss.bitrise.io/u/damien.murphy)
#### Post date: [September 22, 2022, 10:47pm UTC](https://discuss.bitrise.io/t/auto-provisioning-with-new-bundle-identifiers/21184/2 "2022-09-22T22:47:20Z")

</div>

This will likely require looking at your config and build with support access.

Can you create a ticket [here](https://support.bitrise.io/hc/en-us/requests/new) so we can look into this issue for you please?
