Ios-auto-provision 1.3.1 Failed to find ad-hoc Xcode managed provisioning profile for bundle id: com.mindoula.royals.mmr.staging


Bitrise Build Issue Report template

Description of the issue

I went thru all our builds and aligned everything with the correct stack and updated the build steps to the latest versions. Everything is fine other than the upgrade from ios-auto-provision 1.3.0 to ios-auto-provision 1.3.1. which fails with:


Failed to find ad-hoc Xcode managed provisioning profile for bundle id: com.mindoula.royals.mmr.staging.

Please open your project in your local Xcode and generate and ipa file

with the desired distribution type and by using Xcode managed codesigning.

This will create / refresh the desired managed profiles.

Stacktrace (for debugging):

/private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise048926407/step_src/lib/autoprovision/portal/profile_client.rb:76:in `ensure_xcode_managed_profile’

/private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise048926407/step_src/lib/autoprovision/profile_helper.rb:65:in `block in ensure_xcode_managed_profiles’

/private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise048926407/step_src/lib/autoprovision/profile_helper.rb:59:in `each’

/private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise048926407/step_src/lib/autoprovision/profile_helper.rb:59:in `ensure_xcode_managed_profiles’

/private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise048926407/step_src/lib/autoprovision/profile_helper.rb:40:in `block in ensure_profiles’

/private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise048926407/step_src/lib/autoprovision/profile_helper.rb:38:in `each’

/private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise048926407/step_src/lib/autoprovision/profile_helper.rb:38:in `ensure_profiles’

/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise048926407/step_src/step.rb:90:in `’


XCode 10.3

If on which stack? If not on on what operating system? (Plus any other information you can share)

Xcode 10.3.x, on macOS 10.14 (Mojave)


  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • Does the issue happen sporadically, or every time? :EVERYTIME
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? :6/16/2019

Local reproduction

Can it be reproduced on your own Mac/PC by following our local debug guide? Please follow at least the first section (“Testing with a full clean git clone”) to make sure to test the state of the code what will get when it does a git clone in the clean environment! If possible please note which sections you tried. work fine with version 1.3.0

Local reproduction: Linux / Android (docker based) stack builds

Can it be reproduced by running the build locally, after doing a new git clone of the repository into the /tmp directory and running the build from there with the Bitrise CLI ( )? If no, can it be reproduced with Docker (using the same docker images / environment we use on Related guide: .

Build log

Please copy paste the build’s URL here (or if the issue happens somewhere else then the full logs), or if you can’t share the url / log here then send the url or full log through a private channel (e.g. email - ), with a link to the related Discuss issue.



Hi @clay-mindoula!

Sorry to hear about the issue. Can you also include a build URL for the same workflow succeeding on the 1.3.0 version of the step please?




Thanks! We’re looking into this and getting back ASAP.



Hi there @clay-mindoula, our tooling team is currently investigating this issue. Can you please provide support user access in your app’s Settings so that they can review your configuration if necessary? Thanks! :smile:



I believe I have made bitrise support an outside contributor?



@clay-mindoula that won’t work as intended unfortunately, this would be a toggle button in the Settings of your app, you can check out how it works here:



try it now



Perfect, thanks!