Understanding app submission errors

July 21, 2014

Applies to Windows Phone

App submission has a lot of moving parts. If something goes wrong in the process, we always try to make our messages as informative as possible, so you can correct the error and resubmit your app. The information here gives you some additional context to help you understand what’s happened and what you can do to fix it. The easiest way to find what you’re looking for here is to search on this page using the error id of the error you are seeing. If you’re still stuck, visit Dev Center support for more help options.

This topic contains the following sections.

The following table lists app submission error messages, ordered by the error ID. The Error field contains the error message. The words shown in bold in the table will be replaced at run time by specific values relevant to your app. You’ll find more info about each error in the More info field.

Error ID

Error

More info

1002

Silverlight app manifest missing

Verify that the AppManifest.xaml file exists and is included in the package that you submitted.

1003

Silverlight app manifest not valid

There's a problem with the AppManifest.xaml file in the package you submitted. You will need to resubmit your app. Try rebuilding your app and then run the automated tests. To view what's inside your package, see Browsing the contents of your package. To learn more about using the Windows Phone Store Test Kit on Windows Phone 8.0 and earlier, see Windows Phone Store Test Kit for Windows Phone 8. To learn more about using the Windows App Certification Kit on Windows Phone 8.1 and later, see Using the Windows App Certification Kit. To rebuild your app, see Rebuilding your project in Visual Studio. If these steps don’t resolve the issue, see Dev Center support.

1004

App manifest not valid

Rebuild your app and then run the automated tests. To view what's inside your package, see Browsing the contents of your package. To learn more about using the Windows Phone Store Test Kit on Windows Phone 8.0 and earlier, see Windows Phone Store Test Kit for Windows Phone 8. To learn more about using the Windows App Certification Kit on Windows Phone 8.1 and later, see Using the Windows App Certification Kit. To rebuild your app, see Rebuilding your project in Visual Studio. If these steps don’t resolve the issue, see Dev Center support.

1005

The Windows Phone OS [version number] version you’ve specified isn’t correct. Use a different one and then try again.

Verify that the AppPlatformVersion value in WMAppmanifest.xml matches the version of the Windows Phone OS you are targeting.

1008

There’s an incorrect setting in the manifest. Update it and then try again.

Rebuild your app and then run the automated tests. To view what's inside your package, see Browsing the contents of your package. To learn more about using the Windows Phone Store Test Kit on Windows Phone 8.0 and earlier, see Windows Phone Store Test Kit for Windows Phone 8. To learn more about using the Windows App Certification Kit on Windows Phone 8.1 and later, see Using the Windows App Certification Kit. To rebuild your app, see Rebuilding your project in Visual Studio. If these steps don’t resolve the issue, see Dev Center support.

1010

The publisher name in the manifest is too long: [publisher name]. It must be shorter than [publisher name limit] characters. Use a shorter name and then try again.

Change the Publisher field in your WMAppManifest.xml file so it doesn't exceed [publisher name limit] characters.

1011

A RuntimeType in the manifest isn’t correct: [runtimetype]. Use a different one and then try again.

Make sure the RuntimeType attribute in your WMAppManifest.xml is one of the following values: Silverlight, XNA

1012

A TaskName in the manifest isn’t correct: [taskname]. Use a different one and then try again.

Make sure the Taskname field in your WMAppManifest.xml file has the value "_default".

1013

The title in the manifest is too long: [title]. It must be shorter than [title limit] characters. Use a shorter name and then try again.

Change the Title field in your WMAppManifest.xml file so it doesn't exceed [title limit] characters.

1014

There's an invalid task name being used in the PrimaryToken field in the WMAppManifest.xml file.

Make sure the Taskname field in your WMAppManifest.xml file has the value "_default".

1015

The version specified in the manifest isn’t correct: [version number]. Use a different one and then try again.

Verify that the AppPlatformVersion value in WMAppmanifest.xml matches the version of the Windows Phone OS you are targeting.

1016

A file registered in the Silverlight app manifest is missing: [file name]. Use a different one and then try again.

Rebuild your app and then run the automated tests. package, see Browsing the contents of your package. To learn more about using the Windows Phone Store Test Kit on Windows Phone 8.0 and earlier, see Windows Phone Store Test Kit for Windows Phone 8. To learn more about using the Windows App Certification Kit on Windows Phone 8.1 and later, see Using the Windows App Certification Kit. To rebuild your app, see Rebuilding your project in Visual Studio. If these steps don’t resolve the issue, see Dev Center support.

1017

We found too many DLL files in the package. There are [dll count], but only [dll limit] are allowed. Update your package and then try again.

Examine your package and count the number of DLL files in it. If there are more than [dll limit], refactor your app to reduce the number of DLLs.

1020

We found an assembly file that’s not listed in the manifest: [assembly name]. Update your manifest and then try again.

When you build your project, all assemblies, or DLLs, belonging to the project are listed in the AppManifest.xml in your output directory. Somehow, an assembly, or DLL, listed in that file no longer exists in the package. You should rebuild your project. To rebuild your app, see Rebuilding your project in Visual Studio.

1021

The photo extras file isn’t correct: [file name]. Update it and then try again.

Verify that PhotosExtrasApplication is enabled in Extras.xml. If that doesn't fix the problem, see Dev Center support.

1023

The deployment file listed in the manifest is missing: [file name]. Update the manifest and then try again.

When you build your project, all assemblies belonging to the project are listed in the AppManifest.xml in your output directory. Somehow, an assembly, or DLL, listed in that file no longer exists in the package. You should rebuild your project.

1024

The file that the image path points to doesn’t exist: [file name]. Update it and then try again.

Make sure the path specified by [file name] is correct or update it in WMAppManifest.xml.

1025

The file that the Background Image path points to doesn’t exist [path name]. Update it and then try again.

Make sure the path defined by the BackgroundImageUri field in your WMAppManifest.xml exists. It is a relative path to the root of your project.

1026

The package file exceeds the maximum allowed size of [max package size], and the current size is [package size]. Reduce your file size and then try again.

Typically, the size of your package increases significantly if it contains a lot of icons, images, or other media files. You can try to reduce the size of individual files, or remove files that aren't needed until you're below the [package size] limit.

1028

The native API [API name] isn’t allowed in assembly [assembly name]. Update it and then try again.

You need to remove the reference to native API from the assembly.

1029

The package is missing the interop manifest. Update it and then try again.

Verify that the WPInteropManifest.xml file exists and is included in the package you submitted.

1032

The icon file format isn’t correct: [format]. Update it and then try again.

The icon file specified in the IconPath field in your WMAppManifest.xml points to a file that isn't a png file.

1033

We don’t allow embedded EXEs. Remove the [embedded EXE file count] embedded EXEs and then try again.

Make sure there are no .exe files in your package. If there are, you need to remove them.

1034

Invalid entry assembly

Make sure the name of the assembly specified in the EntryPointAssembly field in your AppManifest.xaml is the name of a real assembly that exists in your package. Rebuilding your project should solve this problem.

1039

Missing embedded resource config from the xbl game

A resource config file is missing from your Xbox Live game package. Check and resubmit the package.

1041

Too many game config xlast files found

There were too many config files found. Reduce the number and resubmit the package.

1042

We couldn’t find the WMAppManifest.xml file. Add it and then try again.

Verify that the WMAppManifest.xml file exists and is included in the package that you submitted.

1045

The Windows Phone OS version [version number] doesn’t support the detected capability: [capability id]. You’ll need to remove it or target a different OS version and then try again.

The WMAppManifest.xml file in your project contains a capabilities section, which lists all the capabilities your app wants to use. The file also contains an AppPlatformVersion value. Each version of the platform supports a specific set of capabilities. This error is saying that there's a mismatch and that a capability you defined is not supported for the platform version specified. We recommend running the Store Test Kit to verify what capabilities your app needs. You may also have to adjust or target a different platform version.

1046

Package's targeted Application Platform Version not permitted

Your app has a platform version number that is currently not supported. It is not in the supported list given by [version number]. You will need to rebuild your app targeting one of the supported platform versions and resubmit.

1051

RpalApiAccess permission is required when RpalManifest.xml file is present

The appropriate permission is required when the RpalManifest.xml file is present. To request permission, contact Dev Center support.

2001

Duplicate file detected in Silverlight Appmanifest.xaml or appx manifest

If rebuilding your package doesn't solve this problem, you may have to manually remove any duplicate files from the AppManifest.xaml or appx manifest in your package. To rebuild your app, see Rebuilding your project in Visual Studio.

2002

Localized title is missing or empty

The named resource or the named resource's language was not found in the .PRI file.

2003

The [NeutralResourceLanguage] attribute is missing on the entry assembly. Update the assembly and then try again.

Open Project properties for your project in Visual Studio. Click Assembly Information, and in the Assembly Information dialog, choose a value for Neutral Language in the drop-down.

2005

There’s an incorrect template type in the manifest. Update it and then try again.

The template you are using for Live Tile is not valid. You need to update WMAppManifest.xml with one of the supported values.

2006

The WMAppManifest.xml file isn’t correct. Review it for errors and then try again.

Rebuild your app and then run the automated tests. To view what's inside your package, see Browsing the contents of your package. To learn more about using the Windows Phone Store Test Kit on Windows Phone 8.0 and earlier, see Windows Phone Store Test Kit for Windows Phone 8. To learn more about using the Windows App Certification Kit on Windows Phone 8.1 and later, see Using the Windows App Certification Kit. To rebuild your app, see Rebuilding your project in Visual Studio. If these steps don’t resolve the issue, see Dev Center support.

2007

The package must include at least one assembly. Update it and then try again.

You can explore your package to verify that it doesn't contain an assembly (DLL). Then rebuild your project and verify that the updated package now contains at least one assembly. Rebuild To rebuild your app, see Rebuilding your project in Visual Studio.

2008

Capability [capability id] is not allowed

You specify capabilities in the WMAppManifest.xml file or the appx manifest file. It’s possible that you entered an invalid capability ID into the file, or that you changed the AppPlatformVersion to a version that doesn’t support a particular capability.

It is also possible that you have specified a capability that requires special permissions for your developer account. For example, to deploy or submit an app that uses ID_CAP_WALLET_SECUREELEMENT or ID_CAP_WALLET_PAYMENTINSTRUMENTS, you must request special permissions and have that permission applied to your developer account. For more info and assistance, contact Dev Center support.

2012

Agent [agent name] doesn’t have a valid entry assembly.

Verify the assembly name in the EntryPointAssembly field.

2013

Agent [agent name] doesn’t have a valid entry point type.

Verify the value of the EntryPointType field in AppManifest.xaml.

2014

This image file format isn’t supported: [format].

Verify that your app only uses the allowed image format types. For more information, see Upload and describe your package(s).

2017

The maximum number of defined manifest extensions is [extension limit] and you have too many. Reduce the number and try again.

In your WMAppManifest.xml, reduce the number of extensions defined so it’s less than or equal to the [extension limit] value.

2019

You can't define more than [limit] instances of the background agent type [agent type].

Reduce the number of background agents of this type in your project.

2025

You can't use extension [extension name] with this account. Contact our support team if you'd like to request permissions to use this extension.

You've specified an extension that isn't allowed based on the type of developer account you have.

2030

DeviceID [device id] is not allowed

Apps with the ability to communicate with device [device ID] isn't allowed. Verify the specified device ID or confirm with your OEM or Microsoft that the specified hardware is registered correctly with the Windows Phone Store.

3003

ISV does not have permission to submit Xbox Live apps

The particular ISV does not have permission to submit Xbox Live apps. Contact Dev Center support to get the necessary permission.

3006

Background agents aren't allowed in apps with runtime type as "Modern Native".

For more information on background agents and the types of projects that support them, see Background agents for Windows Phone 8.

3008

The DefaultLanguage element specified in the manifest isn't correct. It must be one of the values supported by the Windows Phone Store.

Check the DefaultLanguage setting in the WMAppManifest.xml file and make sure it's one of the supported languages.

3016

Your account doesn't have permissions to submit framework packages.

Login with an account that has framework package submission permissions and resubmit.

3017

The appxbundle manifest is not valid

The bundle manifest is not valid. Check to see that it conforms to the bundle manifest schema and then resubmit the package.

3018

The appx manifest is not valid

The appx manifest is not valid. Check to see that it conforms to the appx manifest schema and then resubmit the package.

3019

The appxbundle package size is too big

There is a limitation of 4GB on the appxbundle package size. Reduce the size and then resubmit the package.

3110

Store manifest is not valid

The store manifest file is not valid. Check to see that it conforms to the store manifest schema and then resubmit the package.

3111

Windows Phone reserved app info manifest not valid

The Windows Phone reserved app info manifest file is not valid. Check to see that it conforms to the schema and then resubmit the package.

3114

The PRI file is missing

For localization, the PRI file needs to be present.

3115

Extracting localized string data did not complete in time

Try resubmitting the package.

3116

Dumping contents of the PRI localized resource map failed

We were unable to extract localized string data from the application's PRI file. Check that the identity name in the PRI file matches the identity name in the appx manifest. Try again or submit a different appx file.

3117

Invalid package file

We were unable to unpack the appx package. Try again or submit a different one.

3118

The appxbundle cannot have framework app package

The appxbundle cannot have a framework package specified. Remove the framework package and resubmit the package.

3119

The appx bundle must have one app package

There can only be one application package containing the binaries in an appxbundle.

3200

The appxbundle multiple publisher display name

Every localized publisher display name must match. Modify your resources file to ensure that all publisher display names match the display names configured in Dev Center.

3201

The appx manifest publisher displayname mismatch

The publisher display name in the manifest does not match the publisher display name defined in Dev Center.

3202

In-process background tasks are not permitted for Windows Phone packages

Extension of category Windows.ApplicationModel.Background task must not have an executable.

3204

You can't put a background in a custom host.

Remove the Background Tasks declaration from the manifest and try uploading the package again.

The following table lists more app submission error messages, ordered by the error ID. The Error field contains the error message. The words shown in bold in the table will be replaced at run time by specific values relevant to your app. If you are having trouble determining what the problem is with your app, refer to the support options available at Dev Center support for more help.

Error ID

Error

1000

We weren't able to write to your file. Try again.

1001

We weren't able to unpack the XAP package. Try again or submit a different one.

1006

The author name in the manifest is too long: [author name]. It must be shorter than [number] characters. Use a shorter name and try again.

1007

The description for the manifest isn’t correct [description]. Use a different description and try again.

1009

The ProductID in the manifest isn’t correct: [product id]. Use a different ID and then try again.

1018

Assembly [assembly name] is [bytes] too long. A package’s assembly size can only be [byte limit] bytes long. Update your package and then try again.

1019

We don’t allow embedded packages. Remove the [embedded package count] embedded packages and then try again.

1022

The photo extras file contains incorrect XML: [file name]. Update it and then try again.

1030

The package is missing a native assembly. Update it and then try again.

1035

The Xbox xlast file can only have [achievement limit] achievements, and your file has [achievement count]. Reduce the number in your file and try again.

1036

The Xbox xlast file can only have [credit limit] credits, and your file has [credit count]. Reduce the number in your file and try again.

1038

This Xbox game is missing an embedded configuration resource. Update it and then try again.

1040

The config xlast file for this Xbox LIVE game wasn’t found.

1043

The updated title ID for your Xbox game doesn’t match the original. Update it with the same title and then try again.

1044

Your package uses native APIs or has WPInteropManifest, but your account doesn’t have permission to use native APIs. Update it and then try again.

1047

You can’t remove a language from an app update that the original version of the app supported.

1048

The locale identified in this app conflicts with a language that an existing app version supports.   

1049

The languages in this package don’t exactly match the languages in the previously uploaded version of this app.

1050

You can’t downgrade the app platform.

2000

Can’t open resource file: [resource file name].

2004

Something’s happened, and we’re not quite sure what. We haven’t lost any of your app’s info, so try resubmitting again. If you continue to see this message, try submitting your app at a later time.

2009

The embedded file [file name] isn’t allowed.

2010

The embedded file [file name] is too big. The maximum size is [max size], and this file is [file size]. Reduce the file and then try again.

2011

The background agent can’t use [resource], which assembly [assembly name] is trying to use. Update your file and then try again.

2015

This extension isn’t supported: [extension].

2018

You can't define Photo Extras using Extras.xml for apps that target this version of the Windows Phone OS. Instead, use the Extensions element in the WMAppManifest.xml file.

2020

You can't use APIs from a Windows Phone OS version that's higher than the version in AppPlatformVersion.

2021

You've specified an incorrect AppConnectKey: [key]. It must be no more than [number] characters and can include only ASCII characters.

2022

You've specified an incorrect protocol name: [protocol name]. The name must be between 3 and 39 characters and it can include only lowercase ASCII letters, numbers, and hyphens.

2023

You've specified an incorrect FileType: [file type]. The FileType must begin with a period and be between 1 and 64 characters long.

2024

You can't define more than one AppConnectKey.

2026

The file {0} has an incorrect name.  File names can only contain ASCII characters.

2027

Assembly names can't contain the '~' character (tilde). Update the name for file [file name] and try again.

3000

Windows Phone OS 7.0 doesn't support Settings apps.

3002

Your account doesn't have permissions to submit preinstalled apps.

3004

Your account doesn't have permissions to submit Settings apps.

3005

The native resource file [file name] can't contain executable code. Try resubmitting the file without it.

3007

The language element specified in the manifest is invalid. It must be one of the values supported by the Windows Phone Store.

3009

The entry point for the application specified in the image path attribute on the default task in the manifest is invalid or missing. It should point to an .exe located at the root.

3010

The [NeutralResourceLanguage] attribute is invalid on the entry assembly. Update the assembly and then try again.

3011

The package is missing [file name]. Update it and then try again.

3203

Windows Phone 8.1 apps can’t have background tasks for location tracking.

After app submission is complete, there is a package processing stage. The package processing stage creates pre-JIT (just-in-time) compiled packages for improved start-up and run-time performance. The package must pass this stage to move forward in the app lifecycle. If there are any errors, the app will be rejected.

This stage applies to apps that target Windows Phone OS 7.0/7.1 and managed apps that target Windows Phone 8 and later. Although this stage applies to all managed apps, the pre-JIT compile packages are only used for phones running Windows Phone 8 and later.

The following are some common errors in the package processing stage and suggested solutions:

Cause

Solution

Notes

One or more assemblies in the package are obfuscated incorrectly.

Use a different tool to perform the obfuscation or remove the obfuscation.

The pre-JIT compile process optimizes the obfuscated assemblies. However, occasionally some assemblies are obfuscated using a tool that modifies the MSIL in an unsupported way that will cause an error.

The size of one or more methods in the app exceeds 256 KB of IL.

Refactor the offending method into smaller functions.

The size of MSIL for methods in an assembly can be determined by using the ILDASM tool.

The strong name signature validation failed for one or more assemblies.

Sign with the correct key or remove strong name signing.

This error typically occurs when the strong name signing was performed using a key different than the one expected in the assembly metadata.

The package contains mixed-mode (with managed and native code) assemblies.

Remove the mixed-mode assemblies from the package and resubmit the app.

Mixed-mode assemblies are not supported on Windows Phone.

If the previous solutions do not resolve your error, contact Dev Center support for more assistance.

The package contains all the files and resources needed to run your app on a phone. It’s just a ZIP file. To browse the contents of the file, add a .zip extension to the filename and then open the file in Windows Explorer.

You can also extract the contents of the file, once you’ve renamed it with the .zip extension, by right-clicking the file and selecting Extract All from the menu.

When you rebuild a project or solution, you’re cleaning it and then doing a build. Cleaning is the process of removing all intermediary files and output directories. To rebuild your solution in Visual Studio, select the Rebuild command from the Build menu. Alternatively, you can use the ALT + B + R keyboard shortcut.

Show:
© 2014 Microsoft