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

#1

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:

Error:

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 `’

Environment:

XCode 10.3

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

Xcode 10.3.x, on macOS 10.14 (Mojave)

Reproducibility

  • 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 bitrise.io 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 ( https://www.bitrise.io/cli )? If no, can it be reproduced with Docker (using the same docker images / environment we use on bitrise.io)? Related guide: http://devcenter.bitrise.io/docker/run-your-build-locally-in-docker/ .

Build log

Please copy paste the build’s bitrise.io 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 - https://www.bitrise.io/contact ), with a link to the related Discuss issue.

0 Likes

#2

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?

0 Likes

#3
0 Likes

#4

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

0 Likes

#5

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:

0 Likes

#6

I believe I have made bitrise support an outside contributor?

0 Likes

#7

@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: https://devcenter.bitrise.io/troubleshooting/enabling-bitrise-support-user/

0 Likes

#8

try it now

0 Likes

#9

Perfect, thanks!

0 Likes

#10

Where are we with this issue? I am having to upgrade all the things to xcode 11 and after sorting out various issues this step failed so I upgraded it to 1.3.1 and get the following problem:
Developer Portal authentication

Session loaded from environment variable is not valid. Continuing with normal login.

Two-step Verification (4 digits code) or Two-factor Authentication (6 digits code) is enabled for account ‘[REDACTED]’

More information about Two-step Verification (4 digits code): https://support.apple.com/en-us/HT204152

More information about Two-factor Authentication (6 digits code): https://support.apple.com/en-us/HT204915

Two-factor Authentication (6 digits code) is enabled for account ‘[REDACTED]’

If you’re running this in a non-interactive session (e.g. server or CI)

check out https://github.com/fastlane/fastlane/tree/master/spaceship#2-step-verification

Please enter the 6 digit code:

Error:

The input stream is exhausted.

Stacktrace (for debugging):

/Users/vagrant/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/highline-1.7.10/lib/highline.rb:868:in `get_line' 
0 Likes

#11

Seems the Ios-auto-provision 1.3.1 step is screwed

1 Like

#12

Sorry for the delay here.

The step has had a few releases since, you shouldn’t experience these problems on the latest 1.4.1 version! :slight_smile:

0 Likes