Re: Save for enterprise deployment?
Re: Save for enterprise deployment?
- Subject: Re: Save for enterprise deployment?
- From: Rick Mann <email@hidden>
- Date: Wed, 18 Feb 2015 14:13:46 -0800
> On Feb 18, 2015, at 13:45 , Quincey Morris <email@hidden> wrote:
>
> On Feb 18, 2015, at 13:29 , Rick Mann <email@hidden> wrote:
>>
>> I only need to distribute apps to testers and other non-developers (e.g. UX designers, product managers) in the company.
>
> Can you re-iterate what the problem is with distributing to these users as *external* testers through TestFlight? I only recall comments you’ve made about *internal* testers.
Here are a few:
• Apps distributed to external testers require app store approval. We can't wait that long. These are internal testers, in that they're employees of the company, but they should not have iTunesConnect access.
• We sometimes upload a debug version and a release version of the same app, with the same version number. This worked fine in the original TestFlight, but is not allowed in iTunesConnect.
• Our debug version sometimes uses private APIs (in particular, Reveal uses IOSurface or something). I can't upload that to iTunesConnect, even though it's only for internal testing; it's removed for the release version.
• iTunesConnect uploads take a long time to become available for testing (several minutes? 10? 15?), and require multiple steps spaced out throughout time. With TestFlight's desktop uploader, I could do all the work I needed (upload, set access, write up release notes, release) in a couple of minutes, and hit a button, and be done. With iTunesConnect, I have to upload it, wait many minutes for it to be ready for testing, then visit the website to assign testers. It's very clunky.
--
Rick Mann
email@hidden
_______________________________________________
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