iOS Signing certificate success install but still not found when building the app

[trungnguyen-rak]

Description

Hi team,
We are a team which are targeting the Github Action to help archiving the ipa file which then send to the QA teams by uploading it to a Firebase App Distribution.

The code now works well in the local environment, of course, where we can set up the code signing with a big screen.
However, its failed when we tried to run it in a github action macos runner.

The log is saying that the installation of the certificate was success but the build process still not able to find any identity to continue with.
We have confirmed and reupdated the signing certificate and the provisioning file but still not success.

I went through this guild to do the setup: https://docs.github.com/en/actions/use-cases-and-examples/deploying/installing-an-apple-certificate-on-macos-runners-for-xcode-development

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 20.04
• Ubuntu 22.04
• Ubuntu 24.04
• macOS 12
• macOS 13
• macOS 13 Arm64
• macOS 14
• macOS 14 Arm64
• macOS 15
• macOS 15 Arm64
• Windows Server 2019
• Windows Server 2022
• Windows Server 2025

Image version and build link

This is the build log.

0_build_with_signing.txt

Is it regression?

No

Expected behavior

We expect that the build process can find the certificate.
Then the archive action can be success and get the ipa file.

Actual behavior

It seems there is not any certification was installed.
2025-01-15T02:25:51.1364380Z [02:25:51]: �[31mThere are no local code signing identities found. 2025-01-15T02:25:51.1365370Z You can runsecurity find-identity -v -p codesigning /Users/runner/Library/Keychains/login.keychain-dbto get this output. 2025-01-15T02:25:51.1366070Z This Stack Overflow thread has more information: https://stackoverflow.com/q/35390072/774. 2025-01-15T02:25:51.1366950Z (Check in Keychain Access for an expired WWDR certificate: https://stackoverflow.com/a/35409835/774 has more info.)�[0m 2025-01-15T02:25:51.1696500Z [02:25:51]: �[31mCertificate XXXXXXXXXX (ABCCCC Group, Inc) can't be found on your local computer�[0m

Repro steps

The action runs on push event.

1. Push a new tag which matchs the condition
2. The action starts running
3. The logs said the installation of the certification was success
4. The signing process starts looking for the certification in the macos instance.
5. Then it shows "There are no local code signing identities found."

[prasanjitsahoo]

HI @trungnguyen-rak , We will look into the issue and keep you posted with updates.