tuist generate reports keychain error in GitHub Actions

[mfcollins3]

I'm trying to get Tuist to work for me for a new project I started, but I'm running into a wall in GitHub Actions that I can't figure out. Tuist works ok locally, but the tuist generate command is failing in GitHub Actions. I have my code signing certificates and provisioning profiles stored in the Tuist/Signing subdirectory and they're being encrypted with the master.key file. I am getting this error:

Run tuist generate --path ios --no-open
[8](https://github.com/nakedsoftware/nakedblogging/actions/runs/3507063027/jobs/5874506117#step:11:9)
Resolved cache profile 'Development' from Tuist's defaults
[9](https://github.com/nakedsoftware/nakedblogging/actions/runs/3507063027/jobs/5874506117#step:11:10)
Generating workspace Runner.xcworkspace
[10](https://github.com/nakedsoftware/nakedblogging/actions/runs/3507063027/jobs/5874506117#step:11:11)
Generating project Runner
[11](https://github.com/nakedsoftware/nakedblogging/actions/runs/3507063027/jobs/5874506117#step:11:12)
The '/usr/bin/security' command exited with error code 1 and message:
[12](https://github.com/nakedsoftware/nakedblogging/actions/runs/3507063027/jobs/5874506117#step:11:13)
security: SecKeychainItemImport: The specified item already exists in the keychain.
[13](https://github.com/nakedsoftware/nakedblogging/actions/runs/3507063027/jobs/5874506117#step:11:14)

[14](https://github.com/nakedsoftware/nakedblogging/actions/runs/3507063027/jobs/5874506117#step:11:15)
Consider creating an issue using the following link: https://github.com/tuist/tuist/issues/new/choose
[15](https://github.com/nakedsoftware/nakedblogging/actions/runs/3507063027/jobs/5874506117#step:11:16)
Error: Process completed with exit code 1.

I'm running out of ideas as to how to fix this. Has anyone run into this before?

[roanutil]

I'm having a similar problem. I'll reply again here if I figure anything out.

#5259

[pepicrft]

@mfcollins3 apologies for this issue. It seems there's a bug in some Tuist logic that leads to some keychain scenarios not getting gracefully handled. I've created an issue to tackle it on our end. Until we are able to provide as solution, I'd recommend not using Tuist's built-in functionality for installing certificates automatically.

[pepicrft]

Please, continue the discussion in this other thread