Cannot create flight package

[tnsturm]

I'm experiencing a strange behavior:

I'm trying to set up publishing a flight package through VSTS. Connection, Authentification etc works fine.

In the Field "Flight name" I am entering a flight name like I would do in Dev Center "Package flight name".

When I now trigger a publish, VSTS shows error message: "No flight with name 3.3.0".

I then thought because of this this statement in docu: "This task allows you to publish your app to specified flight on the Store by creating a submission on Dev Center" that i have to create the flight package in Dev Center prior to publishing through VSTS.
Error message now is: "Ingestion API can only update, delete, and commit submissions that are created through the API. Please delete the current in-progress submission and create one using the API"

I'm now somewhat lost, I can't create a flight, but I can also not publish to a previously created flight.

Furthermore, there is this line in Documentation:
"Flight name (Text, required) - Friendly name of the flight group (as seen on the Dev Center) that you want to update the submission for."

OK, Flight Group... I tried to put the name of the group of testers ("Testers") as defined in Dev Center into the field "Flight name", but that leads again to Error: "No flight with name Testers"

Please help!

Best Regards
Torsten

[elendil326]

Thanks for reporting this issue @tnsturm . Based on what you describe, it looks like when you create manually the submission through dev center, you try to create a new one from the extension without letting the first one complete, that is why you hit the error "Ingestion API can only update, delete, and commit submissions that are created through the API.". Please create the submission manually in Dev Center for the flight, submit it and let it finish. Then you should be able to use the extension for future submissions.

Let me know how it goes. Happy to clarify further if needed.

[elendil326]

I'm closing this issue since it is not related to the code.

[jzoooneee]

reopening this.

as per @tnsturm, i believe this was done through azure devops. I too am having the same issue.

I made sure I have no flight packages on pending in partner center. and have test group created.

I tried entering new flight name but threw this error : No flight with name "test app"

as suggested to use flight group name. threw this error : "Ingestion API can only update, delete, and commit submissions that are created through the API. Please delete the current in-progress submission and create one using the API"

any thoughts?

[louis-wuitton]

Hi @jzoooneee , please make sure the flight name you put matches exactly to the flight name it appears on the partner center. You can also give it a try to create submission on the flight directly on partner center, let it run and finish, as suggested before.

[jzoooneee]

there is no specified flight name in partner center. I would have to create a new package flight in order for it to be available.. However, when I do that, I get this error.

2020-09-02T17:08:01.2191797Z ##[error]Status 400: {"code":"InvalidOperation","data":[],"details":[],"message":"Ingestion API can only update, delete, and commit submissions that are created through the API. Please delete the current in-progress submission and create one using the API","source":"Ingestion Api","target":"applicationSubmission"} CorrelationId: e6ff5c4b-4037-48df-a099-1e2565e633a2

[louis-wuitton]

Do you see the error message on partner center? Also do you see any submission on partner center regardless of flights?

[jzoooneee]

No i don't see any error. And yes there's a pending submission to publish to store.

[louis-wuitton]

Emm give it a try to delete that pending submission, then create a new package flight.

[jzoooneee]

delete the pending submission and same error. when there's no flight package created.

I also tried creating a flight package and ticked the Delete pending submissions option but still no dice.

##[error]Error: No flight with name "test app" was found
    at request.performAuthenticatedRequest.then.body (D:\a\_tasks\store-flight_13dee6a7-3698-4b12-bbb4-b393560a3ebc\0.2.28\local\flight.js:124:19)
    at _fulfilled (D:\a\_tasks\store-flight_13dee6a7-3698-4b12-bbb4-b393560a3ebc\0.2.28\node_modules\q\q.js:854:54)
    at self.promiseDispatch.done (D:\a\_tasks\store-flight_13dee6a7-3698-4b12-bbb4-b393560a3ebc\0.2.28\node_modules\q\q.js:883:30)
    at Promise.promise.promiseDispatch (D:\a\_tasks\store-flight_13dee6a7-3698-4b12-bbb4-b393560a3ebc\0.2.28\node_modules\q\q.js:816:13)
    at D:\a\_tasks\store-flight_13dee6a7-3698-4b12-bbb4-b393560a3ebc\0.2.28\node_modules\q\q.js:624:44
    at runSingle (D:\a\_tasks\store-flight_13dee6a7-3698-4b12-bbb4-b393560a3ebc\0.2.28\node_modules\q\q.js:137:13)
    at flush (D:\a\_tasks\store-flight_13dee6a7-3698-4b12-bbb4-b393560a3ebc\0.2.28\node_modules\q\q.js:125:13)
    at _combinedTickCallback (internal/process/next_tick.js:73:7)
    at process._tickCallback (internal/process/next_tick.js:104:9)
##[error]Error: No flight with name "test app" was found

[louis-wuitton]

Did you create a new package flight called "test app"?

[jzoooneee]

I did, that was the last comment i mentioned
#57 (comment)

also... in the Windows Store task documentation. It mentioned that flight name is the Friendly name of the flight group.

I have already have a flight group called test app and that doesn't seem to work as well.

[louis-wuitton]

When I saw your screenshot I didn't see a flight called "test app" created. Was that because you got this error?

2020-09-02T17:08:01.2191797Z ##[error]Status 400: {"code":"InvalidOperation","data":[],"details":[],"message":"Ingestion API can only update, delete, and commit submissions that are created through the API. Please delete the current in-progress submission and create one using the API","source":"Ingestion Api","target":"applicationSubmission"} CorrelationId: e6ff5c4b-4037-48df-a099-1e2565e633a2

[jzoooneee]

Yes correct. I deleted the flight package "test app" because it threw that InvalidOperation error.

[louis-wuitton]

From this comment: #57 (comment)

I think what you can give it a try is to create the flight "test app", make sure it appears on partner center, then create a submission directly on partner center to the test app flight. There is no need to run the extension throughout this process.

Then if you can successfully submit a submission on partner center, then give it a try on the extension again.

[gentledepp]

Why is this issue closed? It is nearly 2022 and I still have this issue.
Or is this library deprecated just like UWP?

Our goal was to run a release in azure devops for our UWP app and let it create a new package flight named after $(Build.BuildNumber) (i.e. 2021121.0) for our flight group "Beta testers"

However, no matter what I try, this does not work.

1. I used "Beta testers" as friendly name
   Result:
   

2. I configured "$(Build.BuildNumber)" as friendly name
   Result:
   

Sure there isn't! I want it to create a new package flight without me having to manually upload the artifacts.

3. I add a new package flight manually and call it "2.2112.1.0"
   
   Result:
   

4... changed the task to "delete pending submissions":

steps:
- task: MS-RDX-MRO.windows-store-publish.flight-task.store-flight@0
  displayName: 'Internal test flight'
  inputs:
    serviceEndpoint: 'Windows Dev Center'
    appId: THIS-IS-A-SECRET
    flightName: '$(Build.BuildNumber)'
    packagePath: '**/*.msixupload'
    force: true

Result:

Please delete the current in-progress submission and create one using the API" - HOW? 😳

How on earth shall we automate our build then?
I cannot find any helpful instructions on that topic.
Do we need to actually use different APIs?
Please point me in the right direction!

[YYWolf1]

so any update information about this issue?
because i have the same issue
but i use only curl request for receive link for blob storage temporary and everything was good
but now

Ingestion API can only update, delete, and commit submissions that are created through the API. Please delete the current in-progress submission and create one using the API