fastlane: match - macOS Sierra keychain error

Issue Description

When using macOS Sierra beta I am experiencing an issue with match. I receive an error saying that it cannot locate my keychain. It appears that Sierra is saving keychains with the keychain-db extension instead of keychain. If I change the keychain_name value to login.keychain-db it runs successfully.

Complete output when running fastlane, including the stack trace and command used

$ match adhoc

+-----------------------+---------------------------------------------+
|                       Summary for match 0.6.2                       |
+-----------------------+---------------------------------------------+
| git_url               |  |
| type                  | adhoc                                       |
| git_branch            | master                                      |
| app_identifier        |                         |
| username              |                      |
| keychain_name         | login.keychain                              |
| readonly              | false                                       |
| team_id               |                                  |
| verbose               | false                                       |
| force                 | false                                       |
| shallow_clone         | false                                       |
| force_for_new_devices | false                                       |
| skip_docs   false                                       |
+-----------------------+---------------------------------------------+

[21:11:03]: Cloning remote git repo...
[21:11:10]: 🔓  Successfully decrypted certificates repo
[21:11:10]: Verifying that the certificate and profile are still valid on the Dev Portal...
[21:11:11]: Installing certificate...
[21:11:11]: 🔒  Successfully encrypted certificates repo

Looking for related GitHub issues on fastlane/fastlane...

Found no similar issues. To create a new issue, please visit:
https://github.com/fastlane/fastlane/issues/new

[!] Could not locate the provided keychain. Tried:
    /Users/username/Library/Keychains/login.keychain
    login.keychain```

### Environment

match 0.6.2

About this issue

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

Commits related to this issue

[mach] Fix Keychain handling on macOS Sierra Fixes https://github.com/fastlane/fastlane/issues/5649 — committed to fastlane/fastlane by KrauseFx 8 years ago

Most upvoted comments

Found temporary workaround: ln -s ~/Library/Keychains/login.keychain-db ~/Library/Keychains/login.keychain

+10

podkovyrin on Sep 21, 2016

I just pushed https://github.com/fastlane/fastlane/pull/6389, which will fix this issue. We’ll push a release tomorrow 🚀

KrauseFx on Oct 5, 2016

Where are the rocket and sparkles reaction-emoji when you need them!? 😂

JagCesar on Oct 5, 2016

@JagCesar @larsacus I reached out to the core team about prioritizing a better fix for this. Thanks!

TKBurner on Sep 27, 2016

Hey @KrauseFx - thanks for jumping in. Happy to help any way possible.

It seems like a warning, as Fastlane eventually completes successfully for just the match component, but does show the warning mentioned above.

However, when I attempt to run gym to deploy to Crashlytics with the following:

gym(scheme: scheme,
configuration: "Release",
export_method: "ad-hoc")

That’s where I’m seeing the exit status 65 error without any logging that helps me diagnose the root cause.

trackvia-ios on Oct 4, 2016

@trackvia-ios I investigated my particular Sierra config more carefully, and running security list-keychains only returned the new login.keychain-db:

$> security list-keychains
    "~/Library/Keychains/login.keychain-db"
    "/Library/Keychains/System.keychain"

So, I moved my old login.db -> login.db.bak and did the above symlink and everything seems to be working properly…

larsacus on Oct 4, 2016

I think I’m running into something similar here on Sierra (upgrade from El Cap), but I have both login.keychain and login.keychain-db in my ~/Library/Keychains/ folder and don’t feel comfortable symlinking -db to the non-db. So I can’t validate the above. 😞

larsacus on Sep 27, 2016

Same here with release version of Sierra. If you do clean install then keychain name is login.keychain-db, if update from previous OS X - login.keychain

podkovyrin on Sep 21, 2016