9

TestFlight is closing due to Apple acquisition and I'm in the process of transferring my beta test groups to iTunes Connect.

I used to upload my new nightly build using the desktop app, select (all) the users, and hit Next, that was it. Dead simple.

I've followed instructions at http://help.testflightapp.com/customer/portal/articles/1800072 and I've imported my contacts to iTC. Now, I want to submit my build, but I'm being told that I need to wait for App Review, which seems ridiculous for testing. I've searched and seen that I can add up to 25 "internal" testers that wouldn't require App Review to access the beta app. 25 users is enough for me, however, as far as I see, it requires me to grant these people access to my apps as it clearly states in the Prerelease/Internal Testers tab of my app:

Internal testers can be added in Users and Roles.

Internal testers are iTunes Connect users with the Admin or Technical role.

I don't want to grant them Admin or Technical role, I just want them to be able to test my nightly builds. It was the case with TestFlightApp. Bottomline: Is there a way to submit builds in realtime and let people test it without granting them access to my iTC apps and without waiting for any kind of App Review, just as in TestFlightApp which is being closed? If not possible, are there any alternatives?

Community
  • 1
  • 1
Can Poyrazoğlu
  • 33,241
  • 48
  • 191
  • 389

2 Answers2

4

From what I've seen, only your initial release to external testers is submitted for review. Once it's been reviewed any subsequent uploads shouldn't need to be reviewed. I can't be 100% sure about that though, maybe someone can confirm?

Personally though, I've moved over to use Crashlytics (Now Fabric). It make out to be 'Invite Only' but if you sign up with your email they usually get back to you within a few hours. I actually prefer it to TestFlight and it add's some really neat error catching as part of the same SDK, I'd recommend it.

There are a few other alternatives I've been looking at. HockeyApp, TestFairy and others. But Crashlytics looks to be the best FREE alternative out there.

Hope that helps. Dave.

Dave Leverton
  • 614
  • 3
  • 16
  • If only the initial release is reviewed and subsequent releases are immediately sent, that's great, I didn't know that. At the meantime, I've applied for Crashlytics/Fabric and got an invite while reading your answer :) I'll be giving it a try now. – Can Poyrazoğlu Feb 20 '15 at 13:45
  • I've just set up everything and it just looks great! I didn't know Fabric was that good (yeah, sounds like a viral marketing campaign, but I mean it!). Thank you! – Can Poyrazoğlu Feb 20 '15 at 13:54
  • 1
    No problem, had some downtime at my job so spent a while looking into alternatives when TestFlight announced they were closing. Crashlytics looked to be the best from the ones I looked at. Could have missed one though! – Dave Leverton Feb 20 '15 at 13:58
  • Just an extra note: Does it play well with Flurry Crash Reporting and/or Parse crash reporting? iOS technically permits only one crash reporting service per app AFAIK. – Can Poyrazoğlu Feb 20 '15 at 14:06
  • 1
    Ahh I wouldn't know unfortunately, we were actually using Crashlytics for crash/error reporting before we moved over to using their Beta service so that wasn't an issue for us. – Dave Leverton Feb 20 '15 at 14:08
  • It is not only the initial release that is reviewed. All are reviewed, but we found the review time dropped to <4 hrs for the builds after the first one. – combinatorial Feb 20 '15 at 19:18
  • 3
    In my experience, after using Testflight Beta for 3 releases, the *beta* app review is only required for the first upload. When new binaries are uploaded to the same version and submitted for external testing there is a checkbox that asks if there have been significant changes since the last build. I've always checked "NO", if you check "YES" I suspect that will trigger a new beta app review. – Mark Edington Feb 24 '15 at 22:15
1

Not sure, if this workaround will work for your need and honestly its not the cleanest one. But it did for me, Without going to Ridiculous TestFlight review process.

Ideally, in itunes connect, under User/Roles Area, you should create internal users with technical roles assign to them, and share that apple ID for testing with real persons, may be your QA person, working in different country. In this case, there is no waiting time required and you can share build instantaneously, since internal testers do not required TestFlight Review process.

But let's say, if you can't even create new internal testers on itunes connect, which was my situation, then What a person can do is to share one time credentials of the "Apple ID of any internal tester aka users who have technical roles assign to them" and who have access to that latest build. Then the person in different country, he/she can sign in with these credentials of apple Id by going to Settings> Itunes & App Store and by signing off his existing apple id on that phone.

After this, basically his phone, will have access to all the latest build in TestFlight App for that Apple ID of internal tester and then after installing the app built that person want, he/she can sign off from that apple ID going back to original Apple ID under Settings itunes & apps store settings, and keep this newly installed app built on this phone.

If you concerned about sharing apple id credentials (password, email) of internal tester with this person, then you can temporary update them and then after following this process (huge pain in neck process) revert them.

Again, not the cleanest way, but help me to share my latest built with QA person remotely. Hope other stack flow users have better options.

user2577923
  • 206
  • 1
  • 5