Resolving package upload errors

Here are some of the errors that you could see when you upload packages to the Windows Store. For each error, you can follow the link to get info that can help you resolve the error.

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 isn't an app package. Only an app 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.

We couldn't find a logo for at least one of the languages. Run the Windows App Certification Kit to help you determine which logo is missing.

The app is missing a required image. Your error message may indicate the specific image that is missing, or you can find out by running the Windows App Certification Kit.

For more information, see Choosing your app images and Using the Windows App Certification Kit.

Declared dependencies must be the same for all packages.

If your app has more than one package, 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.

The declared capabilities are not the same in all packages. All packages must declare the same capabilities.

The Package/Capabilities element must be the identical in all 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.

Apps can declare dependencies only on versions of Windows component libraries that are available from the Windows Store and applicable to the app's targeted OS. Check your app's dependencies and confirm that the MinVersion of each is less than or equal to a version that supports your targeted OS and is available on 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 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: [app-specific string]

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 must be exactly: [Publisher ID]

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.

This package uses an incorrect hash algorithm. Packages must use SHA2-256 as the hash algorithm.

Change the hash algorithm to SHA2-256, rebuild the package, and upload it again.

Note  App packages created by Microsoft Visual Studio use this hash algorithm by default.

For more info, see Package format requirements and App package block map.

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 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.

Be sure to test your package with the Using the Windows App Certification Kit before you submit it.

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.

Versioning errors

There are a number of error messages related to version number conflicts.

The value of the Version attribute of the Package/Identity element in the app manifest for an app update 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.

Additionally, the version number of Windows 8.1 packages must always be greater than the version numbers of any of your Windows 8 packages for the same app. In other words, the version number of any Windows 8 package you submit must be lower than the version number of any Windows 8.1 package that you've submitted for the same app. For more info, see Adding Windows 8.1 packages for an existing app.

Here are some examples of update scenarios.

Version in the StoreVersion that you want to upload in a new releaseResult

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 StoreAnd you upload this versionAfter the new version is in the Windows Store...
This will be installed in a new acquisitionThis 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.

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.

This package doesn't contain an app.

For more info, see Building the app package manually.

We can't complete the upload

This error occurs when you have already uploaded 10 packages to the Windows Store for the same 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 language from the Windows Store's certification language list.

For more info about the languages that the Windows Store supports, see Choosing your languages.

The package file is too large.

The maximum size for an app package targeting Windows 8.1 is 8 GB. For packages targeting Windows 8, the maximum size is 2 GB. Make any changes needed so that your app package is not too large, rebuild the package, and upload it again.

For more info, see Package format requirements.

This package is a resource package, which can only be uploaded within an app bundle.

For more info, see App bundles.

Once you publish your app using an app bundle, you must update it using an app bundle.

You cannot submit an app package as an update for an app which you previously submitted as an app bundle. Rebuild the app using an app bundle and upload it again.

For more info, see App bundles.

We can't read the .appxbundle.

The app bundle could not be read. Rebuild the app bundle and upload it again.

For more info, see App bundles.

The app bundle doesn't comply with constraints applied during app bundle production.

The app bundle could not be read or has invalid values. Check your settings, rebuild the app bundle and upload it again.

For more info, see App bundles.

The app bundle can't contain more than 512 packages.

Remove some of the packages, rebuild the app bundle, and upload it again.

For more info, see App bundles.

Your app bundle must have a version greater than [number].

The value of the Version attribute of the Bundle/Identity element in the app manifest must be greater than the value shown.

For more info, see App bundles.

An app bundle can't contain a package which is larger than 8GB.

The maximum size for an app package within a bundle is 8 GB. Make sure that all packages in your app bundle meet this requirement, rebuild the app bundle, and upload it again.

For more info, see Package format requirements.

You can't upload an app bundle for a product which is a Windows component library.

For more info, see App bundles.

An app package can't have a ResourceId as part of the identity.

For more info, see App bundles.

A single app bundle can't include both architecture-neutral and architecture-specific packages.

For more info, see App bundles.

All of your app packages must contain the same number of apps.

For more info, see App bundles.

 

 

Show:
© 2014 Microsoft