Download Latest Certificates And Provisioning Profiles #6
Comments
Definitely! I once had this up and running for > 10 apps. Unfortunately many different problems occurred after a time, because of various reasons, like Apple changing something on the UI. Sooner or later I'll implement it from scratch, maybe as a plugin for What do you think? |
I think the cupertino gem works well for this. The only trouble is installing the provisioning profiles because it can't be opened from the command line via ssh. Has to be a local terminal session. |
But cupertino does not create/modify code signing profiles and push notification files, including generating the .pem file, right? Because that's what I was thinking about:
|
Ah that would be create as well. For now I was just thinking about if someone updates their provisioning file to just have deliver auto-download the latest profiles for that app. I.e. Developer 1 joins the team, Developer 1 creates a new dev certificate in the portal, this invalidates all old certificates, and recreates them. Then when deliver builds it just downloads the new provisioning profiles. Not create them or anything. |
This would be a really nice addition to cupertiono IMHO ;) |
As far as I know, |
Played around with this idea yesterday, The question is: Should we extend cupertino, or work on our own solution? |
I'll have to investigate if it's possible to do it without Javascript. |
We could have a call about it later this week if you want... |
@aschuch This would be the fourth open source project of this collection then. I just released [Snapshot])(https://github.com/KrauseFx/snapshot) and will release I think creating/modifying the profiles would be the next one then. |
I'll close this issue for now, since it's not in the scope of this project. |
This issue was migrated to fastlane/fastlane#2478. Please post all further comments there.
|
A good feature enhancement would be to download and install the latest provisioning profiles and certificates for your app as they can change constantly by adding new developers or new devices.
The text was updated successfully, but these errors were encountered: