Here are the possible errors that you could see when you upload a package to the Windows Store. For each error, we provide one or more links to more info about how to resolve it.
A single app can't include both architecture-neutral and architecture-specific packages.
-
For more info, see Building the app package manually.
All packages for this app must use the package identity name: [package identity name]
-
For more info, see Building the app package manually.
A package is not a main package. Only a main package, which defines an app tile, can be uploaded.
-
The app manifest must contain a valid Application element.
For more info, see Building the app package manually.
At least one language doesn't have a default store logo image.
-
The app is missing a required image.
For the list of images that must be included in your app's package, see App images. The Store logo topic also has additional details about the Store logo image.
At least one language doesn't have a default small logo image.
-
The app is missing a required image.
For the list of images that must be included in your app's package, see App images. The Small logo topic also has additional details about the small logo image.
At least one language doesn't have a default logo image.
-
The app is missing a required image.
For the list of images that must be included in your app's package, see App images. The Logo topic also has additional details about the logo image.
Declared applications must have the same details between packages
-
If your app has more than one package, the Package/Capabilities and Package/Resourceselements must be the same in each package.
For more info, see Building the app package manually.
Declared dependencies must be the same for all packages.
-
If your app has more than one dependency, the Package/Dependencies elements must be the same in each package.
For more info, see Building the app package manually.
The supported languages are not the same for all packages. All packages must support the same languages.
-
For more info, see Building the app package manually.
Declared dependencies must be the same for all packages.
-
If your app has more than one dependency, the Package/Dependencies elements must be the same in each package.
For more info, see Building the app package manually.
The declared capabilities are not the same in all packages. All packages must declare the same capabilities.
-
The Package/Capabilities element must be the same in all main packages.
For more info, see Building the app package manually.
The declared device interfaces are not the same for all packages. All packages must declare the same device interfaces.
-
For more info, see Building the app package manually.
Your app can declare dependencies only on versions of Windows component libraries that are available from the Windows Store. Check your app's dependencies and make sure that the MinVersion of each is less than or equal to a version that is available from the Windows Store.
-
For more info, see Building the app package manually.
This is a Windows component library package, which can't be uploaded.
-
The Package/Properties/Framework element must be False or undefined.
For more info, see Building the app package manually.
A package supports a language that the Windows Store doesn't support. A package can declare only languages that the Windows Store supports.
-
For more info about the languages that the Windows Store supports, see Choosing your languages.
All packages for this app must use the package identity name: [developer namespace]
-
The Name attribute of the Package/Identity element in the app manifest must match the app's package identity name assigned by the Windows Store.
For more info, see Building the app package manually.
The Publisher attribute of the Identity element in the app manifest doesn't match your publisher ID, which is: [developer publisher string]
-
The Publisher attribute of the Package/Identity element in the app manifest must match your Publisher ID in the Windows Store.
For more info, see Building the app package manually.
Packages must use SHA2-256 as the hash algorithm
-
For more info, see Package format requirements.
A package is not named correctly. All packages must have the same app name.
-
For more info, see Building the app package manually.
The PublisherDisplayName element in the app manifest doesn't match your publisher display name.
-
For more info, see Building the app package manually.
The package defines a ResourceID, which isn't allowed.
-
For more info, see Building the app package manually.
The supported languages are not the same for all packages. All packages must support the same languages.
-
For more info, see Building the app package manually and Choosing your languages.
The package declares more apps than the Windows Store allows.
-
For more info, see Building the app package manually.
The following display name does not match any of your reserved names: [displayName]
-
The Package/Properties/DisplayName element must contain a value that matches a name you reserved for this app.
For more info, see Building the app package manually and Naming your app.
Updates to packages must be a newer version
-
The value of the Version attribute of the Package/Identity element in the app manifest must be greater than that of the package last shipped to the Windows Store for the same architecture.
For more info, see Building the app package manually.
-
Here are some examples of update scenarios.
Version in the Store Version that you want to upload in a new release Result x86, v1.0.0.0
x86, v1.0.0.0
Error
The new version number and architecture are the same as what is already in the Store.
x86, v1.0.0.1
x86, v1.0.0.0
Error
The new version number is less than the version number for a package in the Store that supports the same architecture.
x86, v1.0.0.0
x64, v1.0.0.0
x86, v1.0.0.1
x64, v1.0.0.1
Success
This is allowed because the new version number of the x64 and x86 packages are higher than those of the packages in the Store.
-
And here are some examples of valid version number updates.
With this version of your app in the Store And you upload this version After the new version is in the Windows Store... This will be installed in a new acquisition This will be updated if a customer already has the app Nothing
x86, v1.0.0.0
x86, v1.0.0.0 on both x86 and x64 computers
Nothing.
x86, v1.0.0.0
x64, v1.0.0.0
v1.0.0.0 for the customer's architecture
Nothing. The version numbers are the same.
x86, v1.0.0.0
x64, v1.0.0.0
x64, v1.0.0.1
v1.0.0.0 for customers with an x86
v1.0.0.1 for customers with an x64
Nothing for customers running the app on an x86 computer.
v1.0.0.0 will be updated to v1.0.0.1 for customers running the app on an x64 computer.
Note If the x86 version of the app is running on an x64 computer, the app won’t get updated to the x64 version unless the customer uninstalls and reinstalls.
With this version of your app in the Store And you upload this version After the new version is in the Windows Store... This will be installed in a new acquisition This will be updated if a customer already has the app Nothing
neutral, v1.0.0.1
neutral, v1.0.0.1 on all computers
Nothing.
neutral, v1.0.0.1
x86, v1.0.0.0
x64, v1.0.0.0
ARM, v1.0.0.0
v1.0.0.0 for the architecture of the customer's computer.
Nothing. Those who have the neutral, v1.0.0.1 version of the app will continue to use it.
x86, v1.0.0.0
x64, v1.0.0.0
ARM, v1.0.0.0
x86, v1.0.0.1
x64, v1.0.0.1
ARM, v1.0.0.1
v1.0.0.1 for the architecture of the customer's computer.
Nothing for customers running the neutral, v1.0.0.1 version app.
v1.0.0.0 will be updated to v1.0.0.1 for customers running v1.0.0.0 of the app built for their computer's specific architecture.
x86, v1.0.0.1
x64, v1.0.0.1
ARM, v1.0.0.1
x86, v1.0.0.2
x64, v1.0.0.2
ARM, v1.0.0.2
v1.0.0.2 for the architecture of the customer's computer.
v1.0.0.1 will be updated to v1.0.0.2 for customers running either v1.0.0.1 of the app built for their computer's specific architecture.
Unable to read the contents of this package
-
The package could not be read. Rebuild the package and upload it again.
For more info, see Packaging your app using Visual Studio.
We can't complete the upload
-
You have already uploaded 10 packages to the Windows Store for this app. To upload another package, delete the packages you don't need, such as those with errors, and try to upload the package again.
Your app must support at least one required language from the Store's language support list.
-
For more info about the languages that the Windows Store supports, see Choosing your languages.
Build date: 3/19/2013
