Open mandalorianbob opened 5 years ago
Hi, quick comment you don’t mention about making a store entry (non Flighted build). You need to make a regular non Flighted build first. Then you can make a Flighted build.
So just to be clear: if we haven't released to production yet, we can't use the Flight API? Or is there a build we can make that isn't flighted but also isn't in the Store?
Ok, here's what you can do. Create an app profile (ie Staging), and make the visibilty private. You'll have an app URL that you can give to QA etc. This can be flighted (or not) your choice but its a private app that public can't search for. Then when your ready to go live, either make a Live app or set the visibility to public.
So the documentation doesn't have an end-to-end example of how to flight a build, so I'm not certain if I'm doing this right.
Step 1: Created a flight in Dev Center. (I saw an issue that seemed to imply we had to do this.) We did not create a submission for that flight. Just created the flight name, and associated it to a flight group.
Step 2: Specified the appxupload, and the flight name from the flight created in Step 1. I'm using the ID identification method, and the Big ID/Store Id for the app.
I get an error that says: 2019-08-16T18:38:14.1629763Z ##[error]Status 409: {"code":"InvalidState","message":"This application uses features that are not supported by the submission API. To perform this operation, use the Dev Center dashboard.","target":"application"} CorrelationId: d79061bd-7dc4-4cb5-b3f5-9c3795229614
It's possible that there's something set up in Dev Center that I'm not aware of, but we're certainly not intentionally using weird features in the app. What features would cause this?