Open wabahaba opened 1 year ago
@wabahaba , The errors are unrelated. Please double check provisioning profile names in your project. What I see you are trying to build AdHoc version, but somewhere in Build Settings you have a specified match Development...
and not match AdHoc
.
[16:18:051: • /Users/distiller/project/ios/NativeProject.xcodeproj: error: No profile for team 26A7FQK7NS' matching match Development com.blueprintnyc.bluebirdapp' found: Xcode couldn't find
@nekrich great catch! thank you for spotting this, I'll double check!
I'm getting the same error output during create_keychain
when the keychain doesn't exist, yet all lanes complete successfully so it's not really an error but an incorrect warning printed in red. (Someone called this a "red herring warning" https://discuss.circleci.com/t/debugging-common-ios-code-signing-issues/39282)
It seems to be an execution order problem. Our lane is written:
The expectation being that it will run serially, e.g. create will complete before match begins. However, the logs show them happening at the same time:
Is it a faulty assumption that commands within a lane will execute one at a time?
BTW I tried adding a 10s delay after the call to create_keychain,sleep(10)
, but it didn't change the above. So it is running the commands serially, and is definitely something wrong in match
.
(Note that in the image above, it has already successfully run the first half of match but then there seems to be a collision at Installing certificate...
and [⠋] Setting key partition list...
– might be a race condition or concurrency issue in the match code.)
Hi everyone, I am running into the same problem. @wabahaba, did changing it to match AdHoc solve your issues?
@wabahaba, did changing it to match AdHoc solve your issues?
Yes, two things helped:
AppStore
(not AdHoc
) profile to be able to publish the app to TestFlight (fastlane match appstore --git_branch=main
)match AppStore <bundle_id>
and thus saving it.Thanks for such a quick response! I feel I have tried these things but I will persist, cheers.
The error is a "Red herring" as @mosesoak shared. I had recently installed OneSignal into my app and as part of the installation process you have to create a new target. Each target needs their own provisioning profile, it even says in the docs https://docs.fastlane.tools/codesigning/xcode-project/ 🤦♂️. Once I had correctly created my provisioning profiles for each target for both development and appstore my build succeeded. Hopefully this helps someone in future!
it seems the export_xcargs
is missing in the BuildCommandGenerator for Xcode 15.0 and above.
+---------------------------------------------------------------------------------------------------------+
| Summary for gym 2.219.0 |
+------------------------------------------+--------------------------------------------------------------+
| workspace | xxxxxxx.xcworkspace |
| scheme | xxxxxxx |
| configuration | Debug |
| clean | true |
| export_method | ad-hoc |
| export_options.stripSwiftSymbols | true |
| export_options.compileBitcode | false |
| export_options.signingStyle | automatic |
| export_options.method | ad-hoc |
| export_options.manifest.appURL | %APP_IPA_DOWNLOAD_URL% |
| export_options.manifest.displayImageURL | %APP_DISPLAY_IMAGE% |
| export_options.manifest.fullSizeImageURL | %APP_DISPLAY_IMAGE% |
| export_options.thinning | <none> |
| export_xcargs | -allowProvisioningUpdates |
| output_name | xxxxxxxx-v0.0.2-0.0.2 |
| output_directory | ./build/ipa/debug/xxxxxxxx-v0.0.2-0.0.2/ |
| include_symbols | false |
| include_bitcode | false |
| buildlog_path | ./build/log/ |
| silent | false |
| skip_package_ipa | false |
| skip_package_pkg | false |
| build_path | Library/Developer/Xcode/Archives/2024-01-30 |
| result_bundle | false |
| destination | generic/platform=iOS |
| xcodebuild_formatter | xcpretty |
| build_timing_summary | false |
| skip_profile_detection | false |
| xcodebuild_command | xcodebuild |
| skip_package_dependencies_resolution | false |
| disable_package_automatic_updates | false |
| use_system_scm | false |
| xcode_path | /Applications/Xcode-15.2.app |
+------------------------------------------+--------------------------------------------------------------+
+-------------------------------------------------------------------------------------------------------------+
| Generated Build Command |
+--------------------------------------------------------------------------------------+----------------------+
| Option | Value |
+--------------------------------------------------------------------------------------+----------------------+
| set -o pipefail && | |
| xcodebuild | |
| -workspace xxxxxxxx.xcworkspace | |
| -scheme xxxxxxxx | |
| -configuration Debug | |
| -destination | generic/platform=iOS |
| -archivePath | |
| /Developer/Xcode/Archives/2024-01-30/xxxxxxxx-v0.0.2-0.0.2\ | |
| 2024-01-30\ 19.02.23.xcarchive | |
| clean | |
| archive | |
| | tee | |
| /build/log/xxxxxxxx-xxxxxxxx.l | |
| og | |
| | xcpretty | |
+--------------------------------------------------------------------------------------+----------------------+
INFO [2024-01-30 19:02:23.69]: $ set -o pipefail && xcodebuild -workspace xxxxxxxx.xcworkspace -scheme xxxxxxxx -configuration Debug -destination 'generic/platform=iOS' -archivePath /Archives/2024-01-30/xxxxxxxx-v0.0.2-0.0.2\ 2024-01-30\ 19.02.23.xcarchive clean archive |
tee /build/log/xxxxxxxx-xxxxxxxx.log | xcpretty
I used xcargs
the problem is gone.
@farshadmb could you share how you use xargs? i have similar issue with github actions. it was ok in Nov 2023 and build suddenly broke with this error
[00:52:28]: Installing certificate...
[00:52:29]: There are no local code signing identities found.
You can run security find-identity -v -p codesigning fastlane_tmp_keychain
to get this output.
This Stack Overflow thread has more information: https://stackoverflow.com/q/35390072/774.
(Check in Keychain Access for an expired WWDR certificate: https://stackoverflow.com/a/35409835/774 has more info.)
[00:52:29]: Setting key partition list... (this can take a minute if there are a lot of keys installed)
[00:52:29]: security: SecItemCopyMatching: The specified item could not be found in the keychain.
New Issue Checklist
Issue Description
The ReactNative project which builds successfully with automatic signing when run locally on a Mac computer, when run in Circle CI/CD environment, the automatic signing doesn't work resulting in a There are no local code signing identities found error. Following the Circle CI recipe:
with storing profiles in the repo or in the Google Cloud storage bucket (the error is the same for both).
Could this be an issue with the particular Fastlane version (2.213.0) and/or mismatch with Xcode used in Circle CI (version 14.2)? Or is this an issue with configuration of Fastlane or match itself, could you spot a culprit then, please? Or is it possible to keep automatic signing in CI/CD environment? Thanks in advance!
Checked some issues: #21145, #20967, #20626 (related but unfortunately not helping).
Command executed
(Part of Circle CI job.)
Environment
The error:
Log further:
gym
manifest:gym
error:Appfile
Matchfile
Fastfile
Circle CI config:
fastlane env
: