does anyone have a good reference to information about distributing an iOS (JUCE) app via TestFlight so I can give it to testers?
Edit: talking about a standalone app at this point.
It’s been a while, and years ago, things were quite complicated, to the point we switched to using InstallrApp, which is now gone.
I’m assuming things have become much more streamlined now.
Should I just go read through all of Apple’s current docs again, or is there a simple fast-track tutorial/set of steps to follow?
Any tips/advice?
This could actually also be a good topic for a JUCE tutorial / short ADC talk
Thanks for the pointer to fastlane (I now remember hearing about this before).
At the moment I’m content with the manual way of doing things, but this may indeed become very handy at some point.
Since I noticed I had already created an “app” entry for this thing in App Store Connect years ago, I actually just tried doing the TestFlight distribution by simply building the JUCE project in Xcode, archiving and then distributing to TestFlight for internal testing via Xcode (organizer), and that went very smoothly I must say.
Then I had to find out how to also allow external testers to test the app (apparently you then really need to submit the app to Apple first in order to be able to do that), but after a few hours, that went fine too.
So, for now all is fine, and I was positively surprised that things went so smoothly.
TestFlight is very streamlined. The AppStore Connect UX is far of being a good example of UX. but I must admit, over the years, Play Store has worsen (to me) while AppStore is more streamlined.
Also, if there’s no major diffs between builds, the TestFlight updates are being approved immediately which is nice.
Fastlane looks really nice workflow, especially when you’d like to have some automated push from a git repo with CI/CD.
