软件测试中怎么判断是不是bug，该不该提交_缺陷管理_领测软件测试网
软件测试中怎么判断是不是bug，该不该提交
发表于：来源：作者：点击数：
如何对进行 缺陷管理 那？ 一般来说，明显的错误（如程序不能继续运行，出现明显的错误提示框，数据存储错误等）大家都知道肯定是 bug ，经常有疑问的是对于期望结果模糊，GUI（界面，操作模式等）不友好，对比其他的软件的问题。 由于工作的原因，参与了项
如何对进行那？
一般来说，明显的错误（如程序不能继续运行，出现明显的错误提示框，数据存储错误等）大家都知道肯定是，经常有疑问的是对于期望结果模糊，GUI（界面，操作模式等）不友好，对比其他的软件的问题。&&&&&&& 由于工作的原因，参与了项目的一些过程，发现其实如果从开发的角度看看问题，就更容易下定提交bug的决心的。根据bug的来源，以下是我的一些总结：1。由于代码引起的bug&&&&&&& 所有的程序都会有bug,而且所有的都会制造bug.这个道理如同bug是不可能被完全消灭一样.对于一般的开发人员，经常出现的问题是由于没有良好的编程习惯和技术能力。每个人从新手到高手都是有个阶段的，成长的过程总是充满错误的。开发人员多少会在修改bug的过程中成长。有些可能他们认为无法实现的操作是有可能实现的。所以这种情况要提交bug，即使不能修复，开发人员也会在bug里填写理由，这样对和开发人员都是有利的。&&&&&&& 那么对于高级的开发人员，低级错误的发生概率相对来说少很多，大多的bug是由于功能定义不清晰,完善或是架构，语言的局限引起的。有些严重的问题大家可以一起商量解决的.
2。项目时间紧迫造成的bug&&&&&&& 基本上每个项目都有加班的时候，开发人员在紧迫的时间里能做的就是尽可能的完成功能需要要求的功能，主要的功能。然后有时间再去通过修复bug来完善代码。所以测试人员也不要诧异为什么会有那么多的bug，要作的就是尽可能的提交你所发现的bug。&&&&&&& 在我参与的开发中，项目经理经常会询问开发人员的进度，如果他发现你已经实现了某一个模块功能的功能后不是马上开始下一个模块的开发，而在花时间在竭力地凭着自己的猜想去完善模块时，项目经理一定会要求你把模块提交给测试人员测试，并马上开始下一个模块的开发
3。项目定义模糊造成的问题&&&&&&& 有些项目在开始编码时可能只是一个大概的项目定义，甚至连具体功能的定义都不是很清楚.有时客户对产品的最终结果都不清晰，需要一个有形的东西让自己不断的开发出自己的需求。那么这时开发人员大多都是根据自己的经验或常识来实现代码。&&&&&&& 还有就是大多数地需求和设计文档不是面面俱到,只是描述了主要的业务定义.对于一些非主流或异常的处理并没有详细的定义.很多情况下程序在负面的操作时就会出现错误.&&&&&&& 测试人员可能就会发现很多不合理或和其他软件不同造成的用户界面的问题，或者有时更会发现负责代码实现的开发人员误解了需求定义人员对功能的解释，甚至从从源头上需求定义人员对功能就存在误解。
&&&&&&& 虽然有很多原因会引发bug,但是不管什么原因测试人员都要提交自己认为是问题的问题,即使后来发现bug是由于某种局限造成的，但对于自己乃至整个项目组都是一个财富。&&&&&&& 只是在bug提交的时候要切记中立客观,对事不对人.即便开发人员拒绝修改bug,都应该不卑不亢的询问原因.如果还有问题就让你们的上级决定,他们会本着对项目考虑的原则从大局上把握好问题的.[Page]
&&&&&&& 以上的我在开发过程中的一些总结。工作这么长时间，角色也不断在转变，发现自己刚进测试这一行业的有些想法是错误的。而且体会最深的就是在从别人的角度多去思考问题，这样有些问题根本就不是问题。&&&&&&&& 开发和测试的关系永远都应该是水乳交融的，互相促进的。建议大家在出现问题的时候多想想为什么会出现从这样的问题，问题最终是如何解决的，这样才不失为经验积累的好方法。
原文转自：
评论列表（网友评论仅供网友表达个人看法，并不表明本站同意其观点或证实其描述）热门搜索：
梦幻西游解除易信安全模式为什么我明明按照他说的做的去做了.可他还说还存在安全隐患.解除失败呢.求大师们的解释.
你现在位置： &
& [杂谈]梦幻西游隐患之我见
[] []发布时间：07-12-17 10:59
12月18日我们又一次欢度梦幻西游的生日，4个年头里，这款游戏带给我们的经典与欢乐不言而喻，随着大型盗号风波的渐渐远去，将军令的极力推广，梦幻的人气开始得以复苏，策划的努力人人见之，四周年之际，除了对梦幻表示祝福时，也提出了对梦幻后期或明或暗的隐患的担忧，这些隐患已经真实存在在玩家里，虽有目共睹，但若不加以修正，泛滥之势必将引起梦幻危机。
BUG重重，&补偿使者&已成常客
&梦幻西游&开放4年却仍在玩家最爱的游戏之中名列前茅，不得不看出他的实力，其开放后的2、3年里，虽经过大幅度的移民、跨服PK，却少有出现BUG现象，这是这款游戏成功的原因之一，能让我们安心游戏！而如今，随着&补偿使者&的频繁做客，BUG出现之频率让人诧异，一款&熟透了&的游戏，却在重导&游戏初期&或许该有的错误，实在不应该！恰好一朋友在玩大话3，两款游戏比较，居然发现当大话3内测之日起，梦幻西游的大小BUG就开始频繁，大话3也是错误不断，是巧合还是两款游戏的互通点我们无法猜测，只是BUG虽没有盗号来得这么损失惨重，但还是会一次次的让玩家无可奈何，对官方失望透顶。
可怜的帮派&建设&一次次的修改却一次次的出BUG、服务区多次出现惨痛的回挡现象、有段时间节日活动不是提前几天不小心放出就是推迟活动时间、帮派迷宫卡得让人掉线&&补偿使者一次次的出现是否真的可以在这位老人家那里得到完全的修复？他是不是真的起到了&挡箭牌&的作用？突然觉得每个周二的新出内容都已经很格式化的要先测试一周、二周，而另人费解的是这一周、二周的测试并没有起到根本的作用，BUG还是会几天出现一次！补偿补的只是经验和金钱，而不会真正补到玩家的心里去，卡机和BUG是游戏最为忌讳的现象，相信策划比我们更清楚这一点，但请策划把这一隐患可以更认真的屏蔽掉，游戏的经典才会重现。
变相盗号，相关措施应出台
&梦幻&如同一个虚拟社会，人心的道德无限放大，盗号因将军令等措施的出现而有了缓解，而变相盗号的出现却再一次给人以启示，人心不可防。所谓变相盗号，就是以卖号为诱饵，等买号玩家把号练得很JP时再用原始证件修改安全码拿回该号。这样的现象已经非常频繁的出现在玩家的身边，从第一个吃螃蟹的人开始，竟相吃螃蟹的人也越来越多，原始证件成为了一个非常好的盗号本钱，无论你是这号的第几任主人，最后总会成为受害者。
买游戏帐号成为了一个非常危险的行为，而官方也一定知道其中的原由，官方已经在测试推出&藏宝阁&的中间交易场所，这是否预示着官方也开始允许线下交易帐号、梦幻币、装备等虚拟物品了呢？既然这样是否可以出台一些新的措施来保障游戏帐号买家的安全性呢？
简单一点的说，官方是否可以提供一个替换原始证件的平台，并需要通过买家和卖家双方的有效身份证件的证明和核对来完成这次替换呢？虽然有一定的局限性，也比较麻烦，但对于保障买家的接手安全却是非常不错的，同时严谨的核对及交换过程也可以抵制不法分子的从中作祟。有这样一个平台的出现，即使有些玩家还是要铤而走险，但还是保障了部分玩家的利益了。
梦幻活动，要精不要泛
短短一年，梦幻推出的新资料包和活动层出不穷，可以看出策划们的用心良苦，希望丰富的活动能够带动玩家的激情，而策划们的用心却并没有达到很好的效果，一些活动策划的非常辛苦，但推出后却消沉了。或许活动的多并不能很好的带动游戏的激情，而求得活动的精才是一个真正值得去做的事。
精致的活动总会吸引N多人的眼球，比如七夕的鹊桥羽毛活动，拥有足够的人气，比如武神坛活动既是高手之间的较量又是平民百姓看经典战役的最佳时机，又比如副本，四门副本和乌鸡副本更是被人津津乐道的活动，因为可以获得丰富的经验和奖励。但梦幻里还有一些活动则是被人忽视的或者说并没有完全被人认识，比如牌艺大赛、比如&幻镜寻宝&，比如&生死劫&还有比如节假日活动推出3，4年以来一层不变的活动&&
可以说，我们的梦幻西游内容已经非常丰富了，尤其是活动，很多。与其说在推出新的活动，还不如在一些被人忽视的活动中加以深化，从而被人熟识呢？我觉得&变身装备&就是一个非常好的先例，变身套装一开始的推出是完全被人所忽视的，但策划通过帮派迷宫这个活动，把迷宫和套装很好的结合在了一起，从此玩家开始了&套装热&。
并不是让人很难触摸到的活动才算精致，&法宝&的贵族气质曾让人很难接近，因此大家都害怕接到法宝任务，真正能放在玩家心里的并不是一些高难度的活动，真正要把任务或特点发扬起来的也没有太大的局限性。有消化才可以进一步的去接受新的事物，如果本身的活动就难以消化及吸收，新的活动的推出更让人少了一份去接近的信心。
以上这些只是个人的意见，也是搜索各位论坛玩家近期的困惑而总结出的一些文字，这些也仅仅只代表个人及部分玩家的心声，但真心希望策划们可以以游戏的基层设施为重，过多的推出新活动新任务，还不如好好的去解决一些卡机和BUG的现象。
查看更多关《梦幻西游》诚挚邀请各路高手或者
标签： 梦幻西游相关推荐梦幻西游解除安全模式为什么老说账号密码不对_百度知道
梦幻西游解除安全模式为什么老说账号密码不对
提问者采纳
梦幻西游早期的时候好像跟玩家要过一次“安全码”、是由玩家自己设定提交的。也有可能是操作问题。如果怀疑账号被盗。就去163的邮箱试试这个账号密码。真不能登录的话就该注意了哦。
提问者评价
虽然你说的不对，但只有这一个答案，也没有办法了。
其他类似问题
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁
说的太好了，我顶！
Copyright & 2014 www.51yue.net Corporation, All Rights Reserved
Processed in 0.0532 second(s), 3 db_queries,
0 rpc_queries梦幻西游提示问题都记得但是安全码忘记了，怎么查安全码_百度知道
梦幻西游提示问题都记得但是安全码忘记了，怎么查安全码
知道的说下 谢谢了。
只是忘了安全码，别的资料都有，是想查出安全码或修改，不是清空！
提问者采纳
　　尊敬的玩家：　　您好：　　梦幻西游提示问题都记得但是安全码忘记了，怎么查安全码　　通过客服专区提供游戏资料解除：请使用需要取消相关密保产品绑定的帐号，登录主页客户服务专区，在“我要提问”选择“解除帐号绑定服务”——“申请解绑密保产品”提交问题，再随时留意工作人员的回复进行操作！成功申请取消后，帐号上所有的密保服务都会随之取消，请留意。　　有广大玩家的支持，我们会以更周到的服务陪伴您遨游更精彩的网易游戏世界。　　冻结帐号load_kind.html?357　　强制离线load_paper.html?1364　　快速解绑（首次绑定后7天内）　　　　可以修改密码　　方法：　　1 绑定的密码卡 不足7天内 可以立即用安全密码解除全部一切所有的绑定　　2 解除了所有绑定 就可以修改密码了　　如果能改密码，但是还是上不去。那么怎么能把密宝卡取消啊。　　解除密码保护卡　　方法：　　去吧　　改安全密码的网站　　　　如何防盗以及被盗处理事宜　　　　网易公司重申，向玩家提供三种帐号取回途径：　　1，通过有效证件号码取回帐号（）　　2，通过点卡卡号和密码取回帐号（）　　3，通过游戏数据取回帐号（）　　为保护玩家帐号信息的安全性，网易公司强烈建议玩家通过自身申请的方式向网易公司提出帐号取回申请，网易公司将尽力为玩家提供满意的服务。　　百度知道专家为你服务　　如果还有什么疑问，请继续提问　　在我们的共同努力下，“知道”一定能成为充满温馨和智慧的知识社区
提问者评价
其他类似问题
安全码的相关知识
按默认排序
其他1条回答
你杂不说你银行卡里有N万 就是卡丢了呢这年头老实点玩吧穷。B
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁Understanding app submission errors - Windows app development
Understanding app submission errors
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
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 IDErrorMore info1002Silverlight app manifest missingVerify that the AppManifest.xaml file exists and is included in the package that you submitted.1003Silverlight app manifest not validThere'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 . To learn more about using the Windows Phone Store Test Kit on Windows Phone 8.0 and earlier, see . To learn more about using the Windows App Certification Kit on Windows Phone 8.1 and later, see . To rebuild your app, see . If these steps don’t resolve the issue, see .1004App manifest not validRebuild your app and then run the automated tests. To view what's inside your package, see . To learn more about using the Windows Phone Store Test Kit on Windows Phone 8.0 and earlier, see . To learn more about using the Windows App Certification Kit on Windows Phone 8.1 and later, see . To rebuild your app, see . If these steps don’t resolve the issue, see .1005The 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.1008There’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 . To learn more about using the Windows Phone Store Test Kit on Windows Phone 8.0 and earlier, see . To learn more about using the Windows App Certification Kit on Windows Phone 8.1 and later, see . To rebuild your app, see . If these steps don’t resolve the issue, see .1010The 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.1011A 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, XNA1012A 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".1013The 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.1014There'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".1015The 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.1016A 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 . To learn more about using the Windows Phone Store Test Kit on Windows Phone 8.0 and earlier, see . To learn more about using the Windows App Certification Kit on Windows Phone 8.1 and later, see . To rebuild your app, see . If these steps don’t resolve the issue, see .1017We 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.1020We 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 . 1021The 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 .1023The 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.1024The 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. 1025The 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.1026The 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.1028The 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.1029The 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.1032The 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. 1033We 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.1034Invalid entry assemblyMake 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.1039Missing embedded resource config from the xbl gameA resource config file is missing from your Xbox Live game package. Check and resubmit the package.1041Too many game config xlast files foundThere were too many config files found. Reduce the number and resubmit the package.1042We 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.1045The 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.1046Package's targeted Application Platform Version not permittedYour 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.1051RpalApiAccess permission is required when RpalManifest.xml file is presentThe appropriate permission is required when the RpalManifest.xml file is present. To request permission, contact .2001Duplicate file detected in Silverlight Appmanifest.xaml or appx manifestIf 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 .Note:If you see error 2001 during package processing, see the
section for more info.2002Localized title is missing or emptyThe named resource or the named resource's language was not found in the .PRI file.2003The [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. 2005There’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. 2006The 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 . To learn more about using the Windows Phone Store Test Kit on Windows Phone 8.0 and earlier, see . To learn more about using the Windows App Certification Kit on Windows Phone 8.1 and later, see . To rebuild your app, see . If these steps don’t resolve the issue, see .2007The 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. To rebuild your app, see .2008Capability [capability id] is not allowedYou 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 .2012Agent [agent name] doesn’t have a valid entry assembly.Verify the assembly name in the EntryPointAssembly field.2013Agent [agent name] doesn’t have a valid entry point type.Verify the value of the EntryPointType field in AppManifest.xaml.2014This image file format isn’t supported: [format].Verify that your app only uses the allowed image format types. For more information, see .2017The 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.2019You 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.2025You 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. 2030DeviceID [device id] is not allowedApps 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.3003ISV does not have permission to submit Xbox Live appsThe particular ISV does not have permission to submit Xbox Live apps. Contact Dev Center support to get the necessary permission.3006Background 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 .3008The 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. 3016Your account doesn't have permissions to submit framework packages.Login with an account that has framework package submission permissions and resubmit.3017The appxbundle manifest is not validThe bundle manifest is not valid. Check to see that it conforms to the bundle manifest schema and then resubmit the package.3018The appx manifest is not validThe appx manifest is not valid. Check to see that it conforms to the appx manifest schema and then resubmit the package.3019The appxbundle package size is too bigThere is a limitation of 4GB on the appxbundle package size. Reduce the size and then resubmit the package.3110Store manifest is not validThe store manifest file is not valid. Check to see that it conforms to the store manifest schema and then resubmit the package.3111Windows Phone reserved app info manifest not validThe Windows Phone reserved app info manifest file is not valid. Check to see that it conforms to the schema and then resubmit the package.3114The PRI file is missingFor localization, the PRI file needs to be present.3115Extracting localized string data did not complete in timeTry resubmitting the package.3116Dumping contents of the PRI localized resource map failedWe 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.3117Invalid package fileWe were unable to unpack the appx package. Try again or submit a different one.3118The appxbundle cannot have framework app packageThe appxbundle cannot have a framework package specified. Remove the framework package and resubmit the package.3119The appx bundle must have one app packageThere can only be one application package containing the binaries in an appxbundle.3200The appxbundle multiple publisher display nameEvery 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.3201The appx manifest publisher displayname mismatchThe publisher display name in the manifest does not match the publisher display name defined in Dev Center.3202In-process background tasks are not permitted for Windows Phone packagesExtension of category Windows.ApplicationModel.Background task must not have an executable.3204You 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
for more help.Error IDError1000We weren't able to write to your file. Try again.1001We weren't able to unpack the XAP package. Try again or submit a different one.1006The author name in the manifest is too long: [author name]. It must be shorter than [number] characters. Use a shorter name and try again.1007The description for the manifest isn’t correct [description]. Use a different description and try again.1009The ProductID in the manifest isn’t correct: [product id]. Use a different ID and then try again.1018Assembly [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.1019We don’t allow embedded packages. Remove the [embedded package count] embedded packages and then try again.1022The photo extras file contains incorrect XML: [file name]. Update it and then try again.1030The package is missing a native assembly. Update it and then try again.1035The Xbox xlast file can only have [achievement limit] achievements, and your file has [achievement count]. Reduce the number in your file and try again.1036The Xbox xlast file can only have [credit limit] credits, and your file has [credit count]. Reduce the number in your file and try again.1038This Xbox game is missing an embedded configuration resource. Update it and then try again.1040The config xlast file for this Xbox LIVE game wasn’t found.1043The updated title ID for your Xbox game doesn’t match the original. Update it with the same title and then try again.1044Your package uses native APIs or has WPInteropManifest, but your account doesn’t have permission to use native APIs. Update it and then try again.1047You can’t remove a language from an app update that the original version of the app supported. 1048The locale identified in this app conflicts with a language that an existing app version supports.
1049The languages in this package don’t exactly match the languages in the previously uploaded version of this app. 1050You can’t downgrade the app platform.2000Can’t open resource file: [resource file name].2004Something’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.2009The embedded file [file name] isn’t allowed.2010The 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.2011The background agent can’t use [resource], which assembly [assembly name] is trying to use. Update your file and then try again.2015This extension isn’t supported: [extension].2018You 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.2020You can't use APIs from a Windows Phone OS version that's higher than the version in AppPlatformVersion.2021You've specified an incorrect AppConnectKey: [key]. It must be no more than [number] characters and can include only ASCII characters.2022You'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.2023You've specified an incorrect FileType: [file type]. The FileType must begin with a period and be between 1 and 64 characters long.2024You can't define more than one AppConnectKey.2026The file {0} has an incorrect name.
File names can only contain ASCII characters. 2027Assembly names can't contain the '~' character (tilde). Update the name for file [file name] and try again.3000Windows Phone OS 7.0 doesn't support Settings apps.3002Your account doesn't have permissions to submit preinstalled apps.3004Your account doesn't have permissions to submit Settings apps.3005The native resource file [file name] can't contain executable code. Try resubmitting the file without it.3007The language element specified in the manifest is invalid. It must be one of the values supported by the Windows Phone Store.3009The 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.3010The [NeutralResourceLanguage] attribute is invalid on the entry assembly. Update the assembly and then try again.3011The package is missing [file name]. Update it and then try again.3203Windows 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.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:CauseSolutionNotesOne 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.One or more assemblies (or the entire package) is already precompiled.Make sure that you upload the package generated by Visual Studio.To rebuild your app, see .A Windows Phone 8.1 XAP or appx/appxbundle assembly is not valid.Make sure your .winmd file has at least one public entry point.You can use any decompiler application to review the code and check for public entry points if needed.If the previous solutions do not resolve your error, contact
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.
Was this page helpful?
Your feedback about this content is important.Let us know what you think.
Additional feedback?
1500 characters remaining
Thank you!
We appreciate your feedback.
Related developer sites
Other Windows sites
Tool and product downloads
Design template downloads
Essentials
Hello from Seattle.}