| author | Description | title | ms.assetid | ms.author | ms.date | ms.topic | ms.prod | ms.technology | keywords | ms.localizationpriority |
|---|---|---|---|---|---|---|---|---|---|---|
jnHs |
The Packages page is where you upload all of the package files (.appxupload, .appx, .appxbundle, and/or .xap) for the app that you're submitting. |
Upload app packages |
B1BB810D-3EAA-4FB5-B03C-1F01AFB2DE36 |
wdg-dev-content |
10/12/2017 |
article |
windows |
uwp |
windows 10, uwp, packages, upload, package upload |
high |
The Packages page is where you upload all of the package files (.appx, .appxupload, .appxbundle, and/or .xap) for the app that you're submitting. You can upload packages for any operating system that your app targets in this step. When a customer downloads your app, the Store will automatically provide each customer with the package that works best for their device. After you upload your packages, you’ll see a table indicating which packages will be offered to specific Windows 10 device families (and earlier OS versions, if applicable) in ranked order.
For details about what a package includes and how it must be structured, see App package requirements. You'll also want to learn about how version numbers may impact which packages are delivered to specific customers and how packages are distributed to different operating systems.
To upload packages, drag them into the upload field or click to browse your files. The Packages page will let you upload .xap, .appx, .appxupload, and/or .appxbundle files.
Important
For Windows 10, we recommend uploading the .appxupload file here rather than an .appx or .appxbundle. For more info about packaging UWP apps for the Store, see Packaging a UWP app with Visual Studio.
If you have created any package flights for your app, you’ll see a drop-down with the option to copy packages from one of your package flights. Select the package flight that has the packages you want to pull in. You can then select any or all of its packages to include in this submission.
If we detect issues with your packages while validating them, you'll need to remove the package, fix the issue, and then try uploading it again. For more info, see Resolve package upload errors.
You may also see warnings to let you know about issues that may cause problems but won't block you from continuing with your submission.
After your packages have been successfully uploaded, the Device family availability section will display a table that indicates which packages will be offered to specific Windows 10 device families (and earlier OS versions, if applicable), in ranked order. This section also lets you choose whether or not to offer the submission to customers on specific Windows 10 device families.
For more info, see Device family availability.
Your uploaded packages are listed here, grouped by target operating system. The name, version, and architecture of the package will be displayed. For more info such as the supported languages, app capabilities, and file size for each package, click Show details.
If you need to remove a package from your submission, click the Remove link at the bottom of each package's Details section.
If we detect that one or more of your packages is redundant, we'll display a warning suggesting that you remove the redundant packages from this submission. Often this happens when you have previously uploaded packages, and now you are providing higher-versioned packages that support the same set of customers. In this case, no customers would ever get the redundant package, because you now have a better (higher-versioned) package to support these customers.
When we detect that you have redundant packages, we'll provide an option to remove all of the redundant packages from this submission automatically. You can also remove packages from the submission individually if you prefer.
If your submission is an update to a previously published app, you'll see a checkbox that says Roll out update gradually after this submission is published (to Windows 10 customers only). This allows you to choose a percentage of customers who will get the packages from the submission so that you can monitor feedback and analytic data to make sure you’re confident about the update before rolling it out more broadly. You can increase the percentage (or halt the update) any time without having to create a new submission.
For more info, see Gradual package rollout.
If your submission is an update to a previously published app, you'll see a checkbox that says Make this update mandatory. This allows you to set the date and time for a mandatory update, assuming you have used the Windows.Services.Store APIs to allow your app to programmatically check for package updates and download and install the updated packages. Your app must target Windows 10, version 1607 or later in order to use this option.
For more info, see Download and install package updates for your app.