Home Dashboard Directory Help

Visual studio express for windows 8 could not able to create app packages. by WAGmob


 as Fixed Help for as Fixed

Sign in
to vote
Type: Bug
ID: 782015
Opened: 3/25/2013 1:48:41 AM
Access Restriction: Public
User(s) can reproduce this bug


every time I tried to create app package to publish app. visual studio throw error "An unexpected network error has occurred. The app list cannot be refreshed. Please retry by pressing the Refresh button."

After discussion on forum I found that people having more than 100 apps are facing this problem. visual studio is not able to fetch list of apps.
Sign in to post a comment.
Posted by Microsoft on 4/29/2014 at 12:29 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from: http://go.microsoft.com/?linkid=9832436
Posted by anant2614 on 12/15/2013 at 12:12 AM
m facing problem in creating an app package for submitting to windows store...It shows the error "Visual Studio encountered an unexpected network error and can't contact the microsoft account".
Please help its urgent.
Posted by Microsoft on 4/19/2013 at 4:12 PM
Thank you for your feedback. The Windows Store team has pushed an update that should resolve the issue. Please reopen this thread if you are still facing the same issue.
Posted by Microsoft on 3/28/2013 at 5:43 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by WAGmob on 3/25/2013 at 6:13 AM
regularly in contact with Microsoft support but it has been 20 days and they are not able to come up with any solution.
Posted by Microsoft on 3/25/2013 at 1:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by MrSpanky12 on 3/26/2013 at 10:13 AM
Here's how I got it to work (tested on an has worked for 3 apps so far):

1. In your package.appmanifest, under to 'Packaging' tab, put for 'package display name' the app name that's associated with the store (includes spaces, if any).

2. Then, click 'choose certificate' and under 'configure certificate' click 'create test certificate'.

3. For 'publisher common name', put your developer id (the part after 'CN=') and leave the password fields blank and click 'ok', and then 'ok' again.

4. Then create an app package, but do not associate it with the store. (It is recommended you run the automated test program as well if you haven't already)

5. Then, try to upload the package to the store. (It will give you an error that the package name is wrong or doesn't match, that's what we want for now.) (If your are doing this for multiple apps, the correct package name should be a few numbers followed by your developer name followed by a period and the app name associated with the store. The part before the period does not change, so you can save that for future use and skip from step 4 to step 7.)

6. Copy the correct package name (given in the error).

7. Go back to your package.appmanifest, under the 'Packaging' tab and paste the correct package name into the 'Package name' field.

8. Now that the manifest is correct, make another app package (again, without associating it with the store), and upload that package to the store.

9. That's it!

(Basically, we must change the app manifest to match the store release manually instead of having it done for us automatically.)
Posted by Ian G Walker on 3/25/2013 at 10:49 PM
As a workaround I feel that MS should be providing additional accounts for developers to use while this issue is in play.

(The only other workaround is for a developer to open a new live account, pay the store fee again and then submit via the new account)