同一项目不同分支适配不同Apple开发者账号的Fastlane Match配置咨询

Absolutely, this is totally feasible, and Fastlane is built to handle exactly these kinds of multi-environment, multi-account scenarios—let’s walk through how to make this work for your setup.

100% yes. Fastlane’s core strength is its flexibility to adapt to complex deployment workflows, including per-branch account and configuration isolation. You won’t have to abandon Fastlane at all; we just need to tweak how we configure it across your branches.

You have two solid options here, though one is more aligned with your "independent account per client" requirement:

• Recommended: Separate Match repo per client/branch
  This is the cleanest approach because it fully isolates each client’s signing certificates, provisioning profiles, and account credentials. No risk of cross-contamination between clients, which fits Apple’s requirement perfectly. Each branch will point to its own dedicated Match repo in its Fastlane config.
• Alternative: Single Match repo with per-client branches
  If you prefer to keep all Match assets in one repo, you can create a dedicated branch in the Match repo for each client. Then, configure your project’s branch to target that specific Match branch. This works, but it’s easier to mix up assets accidentally—so the separate repo route is safer for compliance.

Here’s a quick example of how to set this up in a client-specific Fastfile:

lane :deploy_to_client_a do
  # Point to Client A's dedicated Match repo
  match(
    type: "appstore",
    git_url: "git@github.com:your-company/match-client-a.git",
    username: "client-a-dev@example.com", # Client A's Apple ID
    app_identifier: "com.yourcompany.clienta" # Client A's bundle ID
  )
  # Add your usual build/upload steps here
  build_app
  upload_to_app_store
end

• Maintain branch-specific Fastlane config files
  Each release/ branch should have its own Fastfile, Appfile, and Matchfile. This lets you hardcode client-specific Apple IDs, bundle IDs, Match repo URLs, and other settings directly in the branch—no messy environment variable juggling unless you want it.
• Prevent merge conflicts
  Since these config files are branch-specific, add them to your .gitattributes file with a merge=ours rule. This tells Git to keep the current branch’s version when merging, so you don’t accidentally overwrite a client’s config with another’s. Example:

  Fastfile merge=ours
  Appfile merge=ours
  Matchfile merge=ours
  

• Test each branch independently
  Before deploying, always test the Fastlane workflow in the target branch to ensure it’s using the correct account and Match assets. A quick fastlane match list can confirm you’re pulling the right signing materials.

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