Best way to use match for several teams

[nicolasbraun]

Hi,

I our company we have an Apple Developer Program account and a Apple Developer Enterprise Program.

I intended to use one single repository to store the provisioning assets from both account in a same place. (and eventually for the one from my client's teams)

For the first account everything worked perfectly but when I tried to create the codesigning stuff for the second one I got the following error

[19:20:34]: Certificate '5KL59A3333' (stored in your git repo) is not available on the Developer Portal
[19:20:34]: for the user nicolas.braun@applidium.com
[19:20:34]: Make sure to use the same user and team every time you run 'match' for this
[19:20:34]: Git repository. This might be caused by revoking the certificate on the Dev Portal

This well handled error lets me believe that Match is not intended to be used on several teams and I am thinking of the following solutions, not sure which is the best

Solution1
One repo per team : This could really make a lot

Solution2
One user per team : not viable

Solution3 : use folders
Would it work to have separated folder on the same single repo? like git_url "https://github.com/project/certificates/account1" in a Matchfile and git_url "https://github.com/project/certificates/account2"in another one , each Matchfile being in the account1 or account2 folder.

Thanks for your work and help,

Nicolas

PS:
As a side effect - let's assume one day Match will manage the same user on several team - you can have a Development_*.mobileprovision in each team so maybe adding the team_name to the filename might be a good security

[KrauseFx]

One repo per team
One user per team

That's what match was designed for, more information on codesigning.guide.

I was thinking about subfolders, but it added a lot of complexity for both the library and the user.

[fastlanebot]

This issue was migrated to fastlane/fastlane#3438. Please post all further comments there.

fastlane is now a mono repo, you can read more about the change in our blog post. All tools are now available in the fastlane main repo 🚀