Windows 8 store package fails on WACK when login to developer account

Question

I'm trying to put a simple app on windows store. I made a fail attempt once, I submitted an app which failed to pass WACK, eventually it failed on submission too. Even then, when I try to package an app with my developer account logged in, I get a performance launch error.

Even on a blank app. also right after I create package logged in, my app's package name and provider fields on appmanifest are changes too. app's package name changes to the first app I submitted, and the provider changes to I guess my developer account's key.

I deleted my failed submission on dashboard, deleted all the names I reserved, including the failed one. But even when I reserve a new name and package my app with that name, my package name still changes to the very first one and fails on wack.

BUT, when I create package of my app WITHOUT logging in, I mean without associate with windows store, I can package my app with the name I want and pass the WACK. I hope anyone can help me with this.

Edit: C# application.

Answer 1

I had this happen too, it seems like WACK got confused and kept trying to verify the wrong version. The following steps resolved it for me:

1. Uninstall the app from your development PC (as in, go to start page, right click on the app and select uninstall).
2. Reboot the dev PC.
3. Select "Local Machine" and "Release".
4. Start debugging wait for it to have started up completely and then stop debugging.

Pretty sure that only one or two of those steps are actually needed, but not sure which ones.

Answer 2

I'm not completely sure I understand your issue, but let me try...

First, what is the failure that you got when you submitted to the Store and when you ran the WACK? You mentioned a "performance launch error". If you are failing the performance test, check out this article for tips to help. Some examples:

• Package content locally (or cache it) when possible, so you don’t have to pull resources from a network during launch.
• Load and do only what you need on launch. You can load other data and do other work asynchronously in the background or when you actually need it.
• Use a "dirty bit" when saving data on suspend, so you only save data that has changed. (Rather than re-serializing your app’s state if that data hasn’t changed, create a Boolean flag variable (or “dirty bit”) which signals that your data has been modified, and only re-serialize when the data has changed.)
• Use bytecode caching if you are developing in JavaScript, so each JS file has bytecode created once and not every time the app launches. To enable this, make sure all JavaScript files are UTF8 encoded with a byte-order mark (BOM) and are statically referenced in the root of your HTML start page.

If this is not the error that the WACK and your Store certification is failing with, please see this blog post and the related blog posts that it links to, to see if your failure is covered there.

Secondly, your issue with associating your code with your reserved name in the Windows Store:

also right after I create package logged in, my app's package name and provider fields on appmanifest are changes too.

This behavior is expected. When you associate your app package with the Windows Store, it will change the "Package name" and the publisher in your appxmanifest. But that's okay! The "Package name" is just what the Windows Store uses as an internal identifier for your app package, and the "Package display name" (right below it in the appxmanifest) is what your end users will see. Set the "Package display name" to what you want.