Important: We no longer maintain this article but if you’re stuck, ask us a question on Stack using the tag ‘visual-studio-cordova'. Also, subscribe to our developer blog. We regularly post issues and workarounds.
This article covers known issues related to Visual Studio Tools for Apache Cordova 2015 when building or deploying to a Windows 8.0, 8.1, Windows Phone 8.1 or any Windows 10 device or emulator.
Due to a bug, you will need to build once for Windows or Windows Phone 8.1 using Cordova 5.1.1 or later for these options to be available. Simply build once and then select Windows 10. We are actively working on a fix.
Due to a Cordova issue, you will need to update the version number in the "Common" section of the config designer to cause the version number to update properly. We are working with the Cordova community on a fix.
This issue has been resolved in the RTM version of Visual Studio 2015 by selecting "Always" for the "Generate app bundle" option. For earlier versions, you can take advantage of the MakeAppx command line utiltiy as follows:
After running the "Create App Packages" wizard, copy your app's ".appx" files from the appropriate AppPackages sub-folders in your project (ignoring the WinJS appx file if present) into a new folder.
Open the Visual Studio Developer Command Prompt and go to the folder where you placed the appx files.
Execute the following command replacing <name> with a name of your choice:
MakeAppx bundle /d . /p <name>.appxbundle
Due to a coding error, the Cordova Windows platform in Cordova previous to 4.1.2 has a temporary key in it that expired on 11/11/2014. To work around this issue, update your Cordova version or download this file and place it in your Tools for Apache Cordova project in following location:
You can read more about the issue on the MS Open Tech blog.
While trying to associate a Cordova app with Windows store using Visual Studio 2013 and CTP3.1, the AppxManifest.xml doesn’t get updated with the appropriate Application Id & publisher name. This has been fixed in Visual Studio 2015 RC. To fix this issue in VS 2013, install the workaround plugin from this site and try building your application again.
Did you find this article helpful?
We're sorry to hear that! Feel free to email our team with your question.