> distributing privately via TestFlight

Don't let Apple catch you doing that. Good way to get your account banhammered.

You need their permission for External TestFlight distribution anyway, otherwise you need to add everyone to the App Store Connect account to forego their reviews.

Currently suffering through rejections just to get a client’s app into the first rounder of testers’ hands.

▲

21 hours ago | parent | next [-]

[deleted]

▲

sevenseacat a day ago | parent | prev [-]

It took us literally months to do this for a recent client project.

▲

__m 21 hours ago | parent [-]

What made it take so long? Btw. The review for external testing happens only once per version, not per build

▲

ChrisMarshallNY 16 hours ago | parent | next [-]

It usually takes a couple of days, the first time, then it's almost immediate, until the next version bump.

I use TestFlight almost from the start of a project. Great way to involve non-tech folks, and work out UI design issues quickly.

▲

sevenseacat 16 hours ago | parent | prev [-]

it kept sitting waiting for review for a week and then getting rejected for bullshit reasons, over and over again

	▲	ChrisMarshallNY 15 hours ago \| parent [-]
		> bullshit reasons Depends on the reason. "Bullshit" is in the eye of the beholder. I don't think that they reject for branding issues, in the TestFlight review (like they do, for the App Store -I have had my app rejected, because it had the word "finder" in its name). For example, if you change the color of the Sign in with Apple button, it will get rejected (in the App Store review -I don't know if they would reject it in the TestFlight review). They do, however, look for things like private API access, crashes, and dodgy behavior. Even if a code path is TODO, it shouldn't crash. I just fill those with NOP functions.