A while ago, Arek wrote an excellent blogpost about integrating fastlane with Travis in which he described how to set up Travis CI to build an app and send it to HockeyApp. One way of pulling that off involved storing the signing certificate in the repository; this way, Travis was able to easily access the certificate and the private key, decrypt them, and sign the application. It wasn’t the perfect solution: it required us to store the certificate and key in every project’s repo, and to update them every time the signing id changes. Luckily for us, there’s another fastlane tool that can help us out with our perpetual need to simplify the process of building stuff. Without further ado, let us introduce fastlane match.
In my last article I covered the basics of the QC coordinates system and explained how to convert the Mouse patch output to match the Origami Phone screen.
I also attached my Snapping Scroll file, as an example of practical usage. Now let me delve into the science behind the Snapping Scroll itself.