Fastlane match succeeds but "Xcode couldn't find any iOS App Development provisioning profiles matching"

#1

Bitrise Build Issue Report template

Description of the issue

I am using fastlane and using match directly in the Fastfile (and made sure I am not including the Bitrise step) and it keeps failing with the following error:

error: No profiles for 'com.alltogether.Hellosaurus' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'com.alltogether.Hellosaurus'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild. (in target 'Hellosaurus' from project 'Hellosaurus')

But you can see directly above that it properly finds and uses the app store profile

Setting Provisioning Profile type to 'app-store'

My Fastfile is pretty basic:

  desc "Push a new beta build to TestFlight"
  lane :beta do
    xcversion(version: "11.5")

    increment_build_number(build_number: latest_testflight_build_number + 1)

    match(app_identifier: "com.alltogether.Hellosaurus", type: "appstore", readonly: true)

    build_app

    upload_to_testflight(username: "ios-dev@hellosaurus.com")
  end

Also, I’ve tried totally removing all provisioning profiles from my local machine and “bundle exec fastlane beta” works as expected.

Local reproduction

I am able to run this locally on my machine (Mac) and it works as expected.

Build log

Please let me know if there is any other info I can provide!

0 Likes

#2

Hi @dannyhertz! As the error message implies, you will still need to have a development type provisioning profile available, even if the export method is app-store. Can you try pulling a profile like that too from match? :slight_smile:

0 Likes

#3

@dannyhertz : it works on your machine because you probably have the dev certificates already present in your keychain. This is something that drove me nuts trying to get our devs to understand (I am an admin).

What I ended up cobbling up is having the devs use the codesigndoc tool (https://devcenter.bitrise.io/code-signing/ios-code-signing/collecting-files-with-codesigndoc) to collect all the certificates and then I have these installed by the workflow into each new VM. Two weeks of cajoling and we are now in a place that we can run builds without certificate or provisioning file errors. :smiley:

0 Likes