Re: Apple TestFlight is unusable, isn't it?
Re: Apple TestFlight is unusable, isn't it?
- Subject: Re: Apple TestFlight is unusable, isn't it?
- From: Roland King <email@hidden>
- Date: Fri, 10 Oct 2014 07:08:57 +0800
> On 10 Oct 2014, at 6:52 am, Rick Mann <email@hidden> wrote:
>
> Haha, wow. I just tried setting up Apple's TestFlight for distributing builds to our QA department. Turns out, it's impossible to use (especially if you're like me, with responsibility for more than one iTunesConnect account).
>
> I have a personal AppleID I use for everything, personal app development, consulting I do, and app development I do for my employer. I am a member of at least two teams: my team, and my employer's. For development, this is fine, as the Provisioning Portal and Apple Developer page support this explicitly, and reasonably well.
>
> But to distribute for testing, you have to use iTunesConnect. I have a separate AppleID just for this purpose, because iTC doesn't let one AppleID belong to multiple organizations.
>
> So, any device you wish to test on must be logged into the App Store via a different Apple ID (you cannot log in the TestFlight app separately from the App Store).
>
> Moreover, you MUST use the link in the supplied email to access the test build. It's not enough to log in with the correct AppleID and launch the TestFlight app (I had assumed it would list available builds). So, now you have to make your email account available on each test device. This increases security risk.
>
> <rant>Until Apple removes the restriction on AppleIDs belonging to multiple iTC organizations, and until they let a tester bypass the email requirement, we will not be able to use it for internal testing.
>
> My guess is that the AppleID restriction is one of the reasons they have not yet made it available for external testing, too (external testers are even more likely to need to belong to more than one organization).
>
> I've reported two bugs about this, not like that'll have any effect.</rant>
>
> I don't suppose anyone has any workarounds to all this?
>
Basically right. Integrated TestFlight at this point is fairly useless. External testers not there and internal testers need to be people on your team with full access to the dev account, yes full access. And yes that also then runs into issues with accounts belonging to multiple organizations.
Workarounds are to use your old TestFlight account just like you did before, if you have a working one or find something else to use. The entire direction TestFlight has been taken in is very disappointing, (app reviews for test builds .. seriously) and I have to think one of the other testing sites will see this as a business opportunity, perhaps they already have.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden