From 6b3f76f3b8a6a104a8fd9b31c66752f22e1560ea Mon Sep 17 00:00:00 2001 From: Andrew McKnight Date: Mon, 28 Aug 2023 11:13:17 -0400 Subject: [PATCH] ci: always run setup_ci For some reason if these jobs are both run on ci sequentially, the second one fails in the match phase. I think setup_ci lets the previous run's keychain get used for the subsequent run's, and then something fails. In any case, these are the only jobs that don't call this with force: true. --- fastlane/Fastfile | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/fastlane/Fastfile b/fastlane/Fastfile index bfd74a562bb..5879d9df13c 100644 --- a/fastlane/Fastfile +++ b/fastlane/Fastfile @@ -263,8 +263,9 @@ platform :ios do desc "Build Perf-test app without Sentry" lane :build_perf_test_app_plain do - - setup_ci + setup_ci( + force: true + ) sync_code_signing( type: "development", @@ -287,7 +288,9 @@ platform :ios do desc "Build Perf-test app with Sentry" lane :build_perf_test_app_sentry do - setup_ci + setup_ci( + force: true + ) sync_code_signing( type: "development",