fastlane: match doesn't renew the signing certificate automatically after the certificate expires
New Issue Checklist
- Updated fastlane to the latest version
- I read the Contribution Guidelines
- I read docs.fastlane.tools
- I searched for existing GitHub issues
Issue Description
An expired signing certificate is automatically removed from the Apple Developer Center. After the expiring date match breaks with the following error:
[13:08:23]: Certificate 'xyz' (stored in your git repo) is not available on the Developer Portal
[13:08:23]: for the user xyz
[13:08:23]: Make sure to use the same user and team every time you run 'match' for this
[13:08:23]: Git repository. This might be caused by revoking the certificate on the Dev Portal
I used fastlane with version 2.77.1.
Expected Behaviour
match automatically recreates signing certificates if they don’t exist and regenerates corresponding provisioning profiles etc. This includes certificate expiration and deletion/revoke in the development center.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 12
- Comments: 25 (4 by maintainers)
We just experienced this issue as well.
This is not fixed, this is still happening. What activity do you want, @fastlane-bot ??
Will add this to my list of things to look into 🙃
Sent with GitHawk
Instead of just select the last cert in the directory: https://github.com/fastlane/fastlane/blob/master/match/lib/match/runner.rb#L106 maybe it can loop through the certs and select the first one that is not expired? And if it cannot find one then generate a new cert?