Now that TestFlight Live became private FlightPath beta, can we still leave TestFlight in production builds?

Question

This document explains that it is OK to leave TestFlight SDK in a production build for the App Store.

But the TestFlight Live they're talking about turned into a new service called FlightPath, which happens to be in private beta. I applied for it weeks ago and never got access. With this change, can I still make my app future-proof and FlightPath compatible by leaving the TestFlight SDK in the App Store build or should I remove it and wait until I get access to FlightPath?

score 4 · Accepted Answer · answered Jun 04 '13 at 21:15

4

yes it should be ok .. just don't set the UniqueIdentifier for [TestFlight takeOff:]

answered Jun 04 '13 at 21:15

Daij-Djan

49,552
17
113
135

Any idea what happens if leave it set ? – Krzysztof Feb 09 '15 at 08:16
the devices can't be matched to users -> all the reports: XY started session, will be as marked anonymous instead – Daij-Djan Feb 09 '15 at 08:23

Now that TestFlight Live became private FlightPath beta, can we still leave TestFlight in production builds?

1 Answers1