'deliver' - the missing API for Apple's new TestFlight

The old TestFlight will shut down in February, so it’s time to switch to a new Beta Testing service.

While there are some great alternatives to the new TestFlight (like Crashlytics Beta and HockeyApp) you might decide to use the official solution for various reasons, however unfortunately there is no public API to implement into your Continuous Integration system any more. 

Introducing deliver testflight, an unofficial command line tool to upload your builds to the new Apple TestFlight (now part of iTunes Connect).

All you have to do is install deliver and add the following to your build steps:

deliver testflight

deliver will fetch all information it needs (e.g. bundle identifier, build number, App ID, IPA file) and will ask you for missing information. You can pass additional parameters too, checkout the project page of deliver.

If you want a more advanced setup, including a fully working Continuous Deployment solution, which takes screenshots, updates provisioning profiles and creates your push certificate for you, checkout fastlane.

Open on GitHub

Edit on GitHub

'fastlane' - Connect all iOS deployment tools into one streamlined workflow

Recently I’ve been working on some really cool iOS related open source tools. All those run independently from each other. This changes with fastlane.

There is a really cool website about the project: https://fastlane.tools

With fastlane you define how your app needs to get released to the App Store (or beta testing service).

Features:

  • Connect all tools, part of the fastlane toolchain to work seamlessly together
  • Define different deployment lanes for App Store deployment, beta builds or testing
  • Deploy from any computer
  • Jenkins Integration: Show the output directly in the Jenkins test results
  • Write your own actions (extensions) to extend the functionality of fastlane
  • Store data like the Bundle Identifier or your Apple ID once and use it across all tools
  • Never remember any difficult commands, just fastlane
  • Easy setup, which helps you getting up and running very fast
  • Shared context, which is used to let the different deployment steps communicate with each other
  • Store everything in git. Never lookup the used build commands in the Jenkins configs
  • Saves you hours of preparing app submission, uploading screenshots and deploying the app for each update
  • Very flexible configuration using a fully customizable Fastfile
  • Once up and running, you have a fully working Continuous Deployment process. Just trigger fastlane and you’re good to go.

Open fastlane.tools

Edit on GitHub

'sigh' - Because you would rather spend your time building stuff than fighting provisioning

Sigh… you have code signing issues again? Introducing sigh, which creates all necessary certificates for App Store, Ad Hoc and Development for you.

What it does:

  • Download the latest provisioning profile for your app
  • Renew a provisioning profile, when it has expired
  • Repair a provisioning profile, when it is broken
  • Create a new provisioning profile, if it doesn’t exist already
  • Supports App Store, Ad Hoc and Development profiles

Open on GitHub

Tags: automatic, code, signing, certificates, provisioning, profiles, script, ruby, gem, jenkins   |   Edit on GitHub