Fastlane多签名身份校验耗时过长问题求助

Hey there! I’ve dealt with this exact frustrating slowdown using Fastlane’s match (matc) in a proxy environment before—waiting 50 minutes just for certificate checks is brutal. Let’s walk through the fixes that worked for me and other devs facing the same issue:

• Optimize the match git repo clone process
  Your log shows a nearly 50-minute gap between starting the git repo clone and finishing the certificate check. Even if Apple’s sites load fine, the match repo (where your certificates/profiles are stored) might be hitting proxy-related bottlenecks. Try these tweaks:

  • Switch the match repo URL from HTTPS to SSH if possible—proxies often handle SSH traffic more efficiently without throttling.
  • Add the repo’s domain to your proxy’s whitelist to ensure it’s not being slowed down by filtering rules.
  • Double-check that your SSH keys or repo credentials are cached properly. Silent auth prompts (even if you don’t see them) can cause match to hang indefinitely.

• Adjust match’s certificate verification settings
  Match runs thorough checks by default, but some of these aren’t essential if you already trust your certificates. Try disabling non-critical checks:

  • Add skip_certificate_verification: true to your match lane in the Fastfile. This skips verifying the certificate chain with Apple’s servers, cutting down on slow round-trip requests.
  • Confirm you’re using force: false (the default setting) to avoid re-downloading certificates/profiles that are already installed (your log confirms the cert is on your machine, so match might be wasting time re-fetching it).

• Explicitly set proxy variables for Fastlane
  System-wide proxy settings don’t always carry over to Fastlane reliably. Try exporting proxy variables in your terminal before running Fastlane:

  export HTTP_PROXY=http://your-proxy-address:port
  export HTTPS_PROXY=http://your-proxy-address:port
  export NO_PROXY=apple.com,developer.apple.com,github.com # Add your match repo domain here too
  

  You can also add these variables to your shell profile (like .bashrc or .zshrc) so they apply automatically every time you run Fastlane.

• Update Fastlane and match to the latest version
  Older versions of Fastlane had known bugs causing slow certificate checks in proxy environments. Run fastlane update to grab the latest stable release—this resolved the issue for a ton of devs when this problem was widespread.

Hope one of these fixes gets your certificate checks back to a normal speed!

内容的提问来源于stack exchange，提问作者r4phG