| ... | ... | @@ -95,7 +95,21 @@ end |
|
|
|
* (Optional) If you have several build configurations, you need to copy-paste lane configuration and make appropriate changes.
|
|
|
|
* Commit those changes to the repository.
|
|
|
|
|
|
|
|
**6. Setup our server configuration**
|
|
|
|
**6. Export signing resources**
|
|
|
|
|
|
|
|
* Open Keychain access application on your mac.
|
|
|
|
* Go to Certificates and find yours.
|
|
|
|
* Right-click on it and Export it.
|
|
|
|
* Expand the certificate and right-click on your name.
|
|
|
|
* Click `Export`, save it somewhere appropriate and enter a password.
|
|
|
|
* Go to https://developer.apple.com/ and download required provisioning profiles.
|
|
|
|
|
|
|
|
**7. Setup our server configuration**
|
|
|
|
|
|
|
|
* Connect to `vnc://macos.faifly.com` (Ask someone from the management for the password).
|
|
|
|
* |
|
|
\ No newline at end of file |
|
|
|
* Find `SlackBuilderConfiguration.plist` on the desktop and open it for editing.
|
|
|
|
* Based on other entries, setup yours one by specifying all the fields.
|
|
|
|
* Copy your signing resources to the server by dragging them on VNC's window.
|
|
|
|
* Install your signing resources and remove their files.
|
|
|
|
* Open Slack and run your slash command.
|
|
|
|
* Keep server window open until it prompts for keychain access. This happens only once per certificate access. |
|
|
\ No newline at end of file |
