Confused about TestFlight submission process

I want to submit my app for TestFlight ... and am getting an error while submitting it.


First, I'm not sure if I'm really submitting it to TestFlight. In Xcode, the button is "Upload to App Store ... " There's no option for specifying TestFlight.


I tried that and got an error and after reading some online comments, it looked like the path to correcting it was using Application Loader through Xcode.


However, again, in Application Loader, there's no way to specify "TestFlight."


So I'm not sure how the submission winds up being reviewed for TestFlight and not the App Store. My App is certainly not ready for public distribution. There is some functionality to finish and some final polish.


But it is functional enough that I can share it with some colleagues for feedback.


When making the submission, I get this error:


[ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle com.xxxxx.mobile [Payload/xxxx.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal."]


As far as I know, I have a code signing certificate. I have no trouble with builds for developer distribution.


When makes me wonder if I need to change certificates to distribution? But that returns me to the question of how I make sure this is a TestFlight submission.


I've searched around and can't find clear answers to my questions ... which are, what certificates and provision profiles do I need for TestFlight? And how do I know I'm submitting to TestFlight and not the app store?

any help here?

Using TestFlight is an optional part of the process afer put build in the store - either way, the app still needs to be reviewed, but you need to upload the app first, then use iTunes Connect from there.


See https://help.apple.com/itunes-connect/developer/#/devdc42b26b8


>So I'm not sure how the submission winds up being reviewed for TestFlight and not the App Store.


In that case, you'd wait to flag it for 'final review'. See this SO thread for discussion:

https://stackoverflow.com/questions/41395077/testflight-while-app-is-waiting-for-review


Your codesigning errors are another issue - Is there a specific scenario involved that requires AL? Suggest you use a current version of Xcode in your example.

Confused about TestFlight submission process
 
 
Q