We have released a new step named: “Deploy to iTunes Connect - Application Loader” (0.9.1)
Uploads binaries (.ipa / .pkg files) to iTunes Connect
using the Apple’s Application Loader.
Setup guide and notes:
Register an app on iTunes Connect, on the My Apps page. Click on the plus sign and select the New App option. This requires an admin account.
Requires an app signed with App Store distibution Provisioning Profile.
Every build which you want to push to iTunes Connect have to have a unique build and version number pair (increment either or both before a new deploy to iTunes Connect).
Uploading IPA failed: fork/exec /Applications/Xcode-beta.app/Contents/Applications/Application Loader.app/Contents/Frameworks/ITunesSoftwareService.framework/Support/altool: no such file or directory
@bitce just stumbled across this thread myself after running into the same issue. While the beta track certainly isn’t for releasing to production, Test Flight does require that we upload to App Store Connect, usually using the Application Loader.
What’s the recommended way in Bitrise to upload beta builds to Test Flight? Need to be able to test iOS 13 features with my beta testers before Xcode 11 and iOS 13 hit public release.
@Roland-Bak Yep, that’s exactly what I’m using when I see this error, hence my reply here to this thread. It seems to not be supported on the beta Xcode 11 track, but then how are we supposed to get builds out to our TestFlight testers from June - September while Apple allows us to test and ship test versions of their new OS + features?
Are you experiencing the same problem with the fastlane deliver action? This method you’ve pasted will likely not be working anymore since apple removed the Application Loader in the latest beta.