Flighted build

[SunjayKalsi]

Flighted build via the api is broken. I have had daily staging (and live) builds being sent to the store for many months.

But it appears via the api at least the Flighted build submission has recently been broken. I will have to resort to manual flighted build. This is a bit inconvenient as my VSTFS builds auto submit on branch merge.

[W0GER]

I'm encountering the same issue attempting to create a Flight Submission.

Steps up to this point:

1. Manually published an app with visibility hidden
2. Used PowerShell StoreBroker to create Flight Resource
3. Using Azure DevOps Task Windows Store - Flight

From the logs:

2019-10-12T21:17:55.4807086Z Authenticating...
2019-10-12T21:17:55.4808771Z Authenticating with server...
2019-10-12T21:17:55.6233622Z Obtaining app information...
2019-10-12T21:17:58.5499366Z Obtaining flight resource for flight Insiders in app <idRemoved>
2019-10-12T21:18:01.4889998Z Deleting existing flight submission...
2019-10-12T21:18:07.2584436Z Creating flight submission...
2019-10-12T21:18:09.1477162Z ##[error]Status 404:  CorrelationId: 0dc9bb0b-f974-4888-bec5-808122358af8

[SunjayKalsi]

Hi, I have seen error you mentioned (but this isn't the error I created this thread for).

just FYI this is what a sucessful log trace looks like:

``Authenticating...
Authenticating with server...
Obtaining app information...
Obtaining flight resource for flight iPresent Live Flighted Build in app XXXXXX
Creating flight submission...
Submission https://developer.microsoft.com/en-us/dashboard/apps/YYYYYYYYYY/submissions/XXXXXX was created successfully
Deleting old packages...
Updating package delivery options...
Updating flight submission...
Creating zip file...
Uploading zip file...
Successfully uploaded file!
Committing flight submission...
Skip polling option is checked. Skipping polling...
Click here https://developer.microsoft.com/en-us/dashboard/apps/YYYYYYYYYY/submissions/XXXXXX to check the status of the submission in Dev Center

[W0GER]

SunjayKalsi, sorry about that, from reading the original post it sounded like the same issue. I'll create a new issue.