Windows tips and workarounds
This document covers tips, tricks, and known workarounds for problems with the Cordova Windows and Windows Phone platform.
Resolve Windows build and deployment errors
Try these steps if you have trouble building and deploying to Windows or Windows Phone emulators or devices.
Before taking any other steps, try running your app against other platforms or emulators to make sure the issue is Windows-specific.
For example, we suggest you test on Android:
Try running against Android and select Ripple - Nexus (Galaxy) (Chrome required)
If you see the same error on other platforms, the issue is likely not Windows-specific, see Resolve build and deployment errors for more general help.
Open the configuration designer (config.xml), Windows tab, and make sure you select the OS that your are currently trying to target (Windows 8.1 or Windows 10).
Running on a device? Make sure that your device is enabled for development. Instructions to do this are different for each platform. * For Windows Phone, see this article. For Windows 10, Visual Studio will prompt you to enable the device.
If you are running on a device and the app is already installed, uninstall the app and try again.
Here are some of the more common issues that you might see on Windows.
appxrecipe file missing?
If you see this error when targeting Windows 10, make sure you set Windows 10.0 as the target in the Windows tab of the configuration designer (config.xml). Then rebuild the project.
Certificate error on Windows?
Make sure your credentials are up to date. Check for any notifications or warning icons in the upper right of Visual Studio.
You may need to re-enter your credentials. If the notifications indicate that you need to update Cordova tooling, please click on the notifications and follow instructions.
Content Security Policy is missing?
Visual Studio will use the Cordova Whitelist plugin by default, so you need to update index.html in the Cordova app with the following
<meta http-equiv="Content-Security-Policy" content="default-src 'self' data: gap: https://ssl.gstatic.com 'unsafe-eval'; style-src 'self' 'unsafe-inline'; media-src *">
Depending on what resources your app needs to access, you may need to add a domain name or URI to the
Unhandled exception running on Windows?
If you see the following unhandled exception when targeting Win/WinPhone 10, make sure you set Windows 10.0 as the target in the Windows tab of the configuration designer.
If you see same exception when targeting Win/WinPhone 8.1, follow the steps here to call platformOverrides.js to fix this issue.
WWAHost runtime error?
When debugging on a Windows 8.1 dev machine, you may get a WWAHost runtime error when navigating between pages. This can happen when loading partial pages in some routing modules such as AngularJS. You can work around this by:
Closing DOM Explorer before navigating pages, or
Upgrading to Windows 10 on your dev machine (the platform issue is fixed in Windows 10).