Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uncertain how to flight build #72

Open
mandalorianbob opened this issue Aug 16, 2019 · 3 comments
Open

Uncertain how to flight build #72

mandalorianbob opened this issue Aug 16, 2019 · 3 comments

Comments

@mandalorianbob
Copy link

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?

@SunjayKalsi
Copy link

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.

@mandalorianbob
Copy link
Author

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?

@SunjayKalsi
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants