As I mentioned in my previous post, TestFlight has been acquired by Apple and will be discontinued on February 26, 2015, which is, eh, soon. Instead, they offer the “All-New TestFlight Beta Testing service available inside of iTunes Connect“.
So this post was going to be about moving to this new All-New iTunes Connect TestFlight Beta Testing service provided by Apple.
However, while investigating this new service I quickly stumbled upon so many issues with their service that renders it quite useless. Let me name a few:
- Apps made available to External Testers (testers that are not a member of your team in iTunes Connect) require a Beta App Review and must comply with the full App Store Review Guidelines before testing can begin. A review is required for new versions of your app that contain significant changes.
- A submitted build will be available for only 30 days after invitations to the testers have been sent.
- Enterprise (in-house) distribution builds are not supported, only App Store builds.
- Only support for iOS 8 and up. Really?
- There is no upload API which is kind of a deal breaker in a CI scenario. There is a workaround for this using deliver from fastlane which looks like a great toolset for automating iOS builds. I just happened to hear about fastlane last week in a recent episode of the Gone Mobile podcast. Sounds really interesting and I might give that a try some day.
Wow, that’s a lot of drawbacks! This led me to look for a different app distribution platform. A quick search gives you a number of options, such as http://app.io, http://installrapp.com, http://testfairy.com and http://hockeyapp.net.
And the winner is….HockeyApp
I went for HockeyApp. Partly because I was already somewhat familiar with it (at least with the name), but also because it supports all multiple mobile platforms, including Android and Windows Phone, which is quite interesting. I noticed that Microsoft acquired HockeyApp in December 2014. This of course raises the question if Microsoft will not do the same as Apple did, i.e. drop support for other platforms. However, recent moves from Microsoft in the mobile space, e.g. the adoption of Xamarin and releasing major apps on the iOS platform, lead me to believe that they will not do that and will stick to their cross-platform approach.
Another reason for choosing HockeyApp is the availability of a Jenkins plugin for HockeyApp. And after all, I needed to include this TestFlight replacement into my Jenkins build pipeline.
Configuring the HockeyApp plugin is just as easy as the TestFlight plugin. First you configure a Default API Token in Manage Jenkins – Configure System and then you configure the Post-build Action Upload to HockyApp. Everything else was already in place, the ipa and dSYM.zip files were already present and I had a build.properties file containing the changelog.
So there you go, Apple drove me into the arms of Microsoft with their sub-par service. Isn’t it ironic, don’t you think?