match 0.6.1 → 0.6.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 69d2b22f33191556e2c6caaebe82df73bae38497
-  data.tar.gz: a448b4d6c7473b3eabf4bf7ca80151c213f53d59
+  metadata.gz: 2bf8411a952af7ce0f17769170a217aeef8bf939
+  data.tar.gz: 1c34d864fdde067fea574ee3a2f4ab5db1ab3e52
 SHA512:
-  metadata.gz: 68d99ff49f1251c43ba757ba3e1517b3f888564ad3999c06d559d1397a3043450e39d94e84b16ea6fdebec75f3496214771643493f50680d199e7f8216813a93
-  data.tar.gz: 9a82844f1676f5b6ba818424198b70643d3b2e4685115861b3f16f63fd4e202d375e1877bfbd7f8456595e3b635e0d08cd69d465e681f201a4ed0a75de63221b
+  metadata.gz: 3f823abc052fe4527efdffb73f54fbdb9eced633fc27cfa6274f867ad35d19a9ead31ee1e69d7a1fbf0d894e35c34b4211d828b1e42653a6db5dcc84d54b0f51
+  data.tar.gz: 4dcebb2b25763a1e4f69569ac27ccb609d6621f28ff5255b4b58ce33ef7caec35ef4398039fb3e171bf76a622ed4471a065d98a91b6de4c1dedb9ef28b19277c

data/README.md

@@ -38,6 +38,10 @@ match
 
 A new approach to iOS code signing: Share one code signing identity across your development team to simplify your codesigning setup and prevent code signing issues.
 
+`match` is the implementation of the https://codesigning.guide concept. `match` creates all required certificates & provisioning profiles and stores them in a separate git repository. Every team member with access to the repo can use those credentials for code signing. `match` also automatically repairs broken and expired credentials. It's the easiest way to share signing credentials across teams"
+
+[More information on how to get started with codesigning](/fastlane/docs/Codesigning)
+
 -------
 <p align="center">
     <a href="#why-match">Why?</a> &bull;
@@ -130,7 +134,7 @@ username "user@fastlane.tools"
 
 #### Important: Use one git branch per team
 
-`match` also supports storing certificates of multiple teams in one repo, by using separate git branches. If you work in multiple teams, make sure to set the `git_branch` parameter to a unique value per team. From there, `match` will automatically create and use the specified branch for you. 
+`match` also supports storing certificates of multiple teams in one repo, by using separate git branches. If you work in multiple teams, make sure to set the `git_branch` parameter to a unique value per team. From there, `match` will automatically create and use the specified branch for you.
 
 ```ruby
 match(git_branch: "team1", username: "user@team1.com")
@@ -267,9 +271,7 @@ match(app_identifier: "tools.fastlane.app.today_widget", type: "appstore")
 
 ### Setup Xcode project
 
-To make sure Xcode is using the right provisioning profile for each target, don't use the `Automatic` feature for the profile selection.
-
-Additionally it is recommended to disable the `Fix Issue` button using the [FixCode Xcode Plugin](https://github.com/neonichu/FixCode). The `Fix Issue` button can revoke your existing certificates, which will invalidate your provisioning profiles.
+[Docs on how to set up your Xcode project](/fastlane/docs/Codesigning/XcodeProject.md)
 
 #### To build from the command line using [fastlane](https://fastlane.tools)
 
@@ -291,6 +293,8 @@ This is useful when installing your application on your device using the Develop
 
 You can statically select the right provisioning profile in your Xcode project (the name will be `match Development tools.fastlane.app`).
 
+[Docs on how to set up your Xcode project](/fastlane/docs/Codesigning/XcodeProject.md)
+
 ### Continuous Integration
 
 #### Repo access
@@ -301,7 +305,7 @@ Some repo hosts might allow you to use the same deploy key for different repos,
 There are a few ways around this:
 
 1. Create a new account on your repo host with read-only access to your `match` repo. Bitrise have a good description of this [here](http://devcenter.bitrise.io/docs/adding-projects-with-submodules).
-2. Some CIs allow you to upload your signing credientials manually, but obviously this means that you'll have to re-upload the profiles/keys/certs each time they change.
+2. Some CIs allow you to upload your signing credentials manually, but obviously this means that you'll have to re-upload the profiles/keys/certs each time they change.
 
 Neither solution is pretty. It's one of those _trade-off_ things. Do you care more about **not** having an extra account sitting around, or do you care more about having the :sparkles: of auto-syncing of credentials.
 

data/lib/match/utils.rb

@@ -1,10 +1,22 @@
 module Match
   class Utils
     def self.import(item_path, keychain)
-      command = "security import #{item_path.shellescape} -k ~/Library/Keychains/#{keychain.shellescape}"
+      # Existing code expects that a keychain name will be expanded into a default path to Libary/Keychains
+      # in the user's home directory. However, this will not allow the user to pass an absolute path
+      # for the keychain value
+      #
+      # So, if the passed value can't be resolved as a file in Library/Keychains, just use it as-is
+      # as the keychain path.
+      keychain_paths = [File.join(Dir.home, 'Library', 'Keychains', keychain), keychain]
+
+      keychain_path = keychain_paths.detect { |path| File.exist?(path) }
+
+      UI.user_error!("Could not locate the provided keychain. Tried:\n\t#{keychain_paths.join("\n\t")}") unless keychain_path
+
+      command = "security import #{item_path.shellescape} -k #{keychain_path.shellescape}"
       command << " -T /usr/bin/codesign" # to not be asked for permission when running a tool like `gym`
       command << " -T /usr/bin/security"
-      command << "&> /dev/null" # we couldn't care less about the output
+      command << " &> /dev/null" unless $verbose
 
       Helper.backticks(command, print: $verbose)
     end

data/lib/match/version.rb

@@ -1,4 +1,4 @@
 module Match
-  VERSION = "0.6.1"
+  VERSION = "0.6.2"
   DESCRIPTION = "Easily sync your certificates and profiles across your team using git"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: match
 version: !ruby/object:Gem::Version
-  version: 0.6.1
+  version: 0.6.2
 platform: ruby
 authors:
 - Felix Krause
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-05-24 00:00:00.000000000 Z
+date: 2016-08-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: security
@@ -311,7 +311,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.8
+rubygems_version: 2.4.5.1
 signing_key: 
 specification_version: 4
 summary: Easily sync your certificates and profiles across your team using git