TestFlight should be more flexible in what it allows (beta SDKs, CloudKit dev, etc.)
| Originator: | robotspacer | ||
| Number: | rdar://21787087 | Date Originated: | 12-Jul-2015 07:39 PM |
| Status: | Open | Resolved: | |
| Product: | iOS SDK | Product Version: | |
| Classification: | Enhancement | Reproducible: | N/A |
Summary: Not long ago I moved all of my beta testing from Microsoft's HockeyApp over to Apple's TestFlight. This change has been wonderful overall made things so much easier for my testers and myself. Unfortunately I'm finding more and more things that are all but forcing me to go back to sending out Ad Hoc builds with HockeyApp. There's no way to test iOS 9 builds externally through TestFlight. That made sense when you had to be a developer to use iOS 9, but now it's in public beta. iOS apps are getting more and more complex, with different features on different devices, and now they include watchOS apps too. I can't wait until the last minute to test major changes. There's no way to use the CloudKit development environment with TestFlight. When I submit a build the production environment is selected automatically. That'd be fine if I could send people a Mac app that uses production, but I can't. See rdar://21787043 Steps to Reproduce: N/A Expected Results: N/A Actual Results: N/A Version: N/A Notes: Here's how I see this working: if I submit an app that does something that isn't allowed in the App Store, like using a beta SDK or CloudKit's development environment, it gets marked as beta-only. These builds would be allowed for external TestFlight, but would not be selectable when you submit a build for App Store review. Configuration: N/A Attachments:
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!