fastlane: [Match] Cannot get working on Bitrise (WWDC cert)

New Issue Checklist

Issue Description

I’m trying to get my build running on Bitrise. It’s using the latest version of Fastlane:

Successfully installed fastlane_core-0.44.1
Successfully installed spaceship-0.27.1
Successfully installed cert-1.4.1
Successfully installed deliver-1.11.3
Successfully installed frameit-2.6.2
Successfully installed gym-1.6.3
Successfully installed sigh-1.8.0
Successfully installed match-0.6.1
Successfully installed pem-1.3.1
Successfully installed pilot-1.6.0
Successfully installed produce-1.1.2
Successfully installed scan-0.7.0
Successfully installed supply-0.7.0
Successfully installed xcode-install-1.4.0
Successfully installed fastlane-1.90.0

I’m using Match to manage my certificates but it doesn’t seem to be able to install things properly. It’s only looking in the login keychain for the WWDC intermediate cert - Bitrise has it installed in the System keychain. Its unable to install it into the login keychain.

[07:20:38]: 🔓  Successfully decrypted certificates repo
[07:20:38]: Installing certificate...
security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  1062  100  1062    0     0   1276      0 --:--:-- --:--:-- --:--:--  1276
[07:20:39]: There are no local code signing identities found. You can run `security find-identity -v -p codesigning` to get this output. This Stack Overflow thread has more information: http://stackoverflow.com/q/35390072/774. (Check in Keychain Access for an expired WWDR certificate: http://stackoverflow.com/a/35409835/774 has more info.)
[07:20:40]: Installing provisioning profile...

The rest of the process seems to report that it worked OK but once it gets to building, everything fails with the error:

Code Sign error: No code signing identities found: No valid signing identities (i.e. certificate and private key pair) were found.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 36 (3 by maintainers)

Most upvoted comments

Thanks @TKBurner , let us know if we can help with anything, and have a nice weekend! 😉

I had the same exact issue and adding the match(type: "development", app_identifier: "*") worked.

Not sure why you need to have a wildcard development profile since the builds (in my case) are ran in release mode and will do code signing with either ad-hoc or appstore profiles.

I’m the guy that @viktorbenei quoted on this. For me, I had some frameworks that were bundled with my project, and I needed a wildcard provisioning profile to build with. I created a development profile through match with app_identifier *, and then added a lane to pull that provisioning profile, followed by my distribution one:

  lane :match_targets do

    match(type: "development", app_identifier: "*")
    match(type: "appstore", app_identifier: "<app_id>")
    match(type: "appstore", app_identifier: "<app_extension_id>")

  end

That seemed to fix my build issues, although it seems your issue differs a bit.

@viktorbenei Thanks for following up with the detailed info. I just bumped this with the core team. We’ll update you on this thread. Thanks! 👍

We just pushed a fix, please update using sudo gem update fastlane or bundle update (if you use bundler). Let me know if that fixes the problem for you 👍