Unable to start debugging in Visual Studio RTM for cordova app

Question

I have a project that was working on RC and worked with no problems. Updated to RTM and now I cannot start the application

I also created a new black cordova app and

Answer 1

I have the same issue, cannot start a JS/TS cordova project.

I went to Tools -> Options -> Tools for Apache Cordova, click the 'Run Dependency Checker'. VS 2015 gave me a report as following:

=====================

Please fix the following issues to ensure that your app builds and runs successfully.

Software/Tool

Issue

Android Package: build-tools-19.1.0 One or more required packages are missing. Please update the packages as described. Instructions Android Package: sys-img-armeabi-v7a-android-19 One or more required packages are missing. Please update the packages as described. Instructions Android Package: sys-img-x86-android-19 One or more required packages are missing. Please update the packages as described. Instructions Android Package: addon-google_apis_x86-google-19 One or more required packages are missing. Please update the packages as described. Instructions Android Package: addon-google_apis-google-19 One or more required packages are missing. Please update the packages as described. Instructions

After fixing these issues, please restart Visual Studio to ensure that changes have been applied.

==================

I also found these links may be helpful:

https://msdn.microsoft.com/en-us/library/dn757054(v=vs.140).aspx

https://msdn.microsoft.com/library/dn771551%20(v=vs.140).aspx

https://github.com/Microsoft/cordova-docs#known-issues

Update: I installed Andriod SDK API 19 21 22 using the SDK Manager, no luck.

Answer 2

If, after upgrading Visual Studio, you see the error message, "The debugger cannot continue running the process. Unable to start debugging.", a library may have been corrupted. Try the following workaround. Close all VS instances, then go to %appdata%\username\Local\Microsoft\Phone Tools, and rename the CoreCon folder to another name such as CoreCon2. Then try restarting your app in VS.

Answer 3

I suspect there was a problem upgrading from RC to RTM on the same machine. You might have to fix the issue by doing a fresh install of RTM on a clean box. Can you give that a try?

Answer 4

I know this isn't an answer (yet). I submitted this issue with Microsoft (I'm experiencing the same thing). I figured I would see what they say. I'll keep you posted if there is any progress.

https://connect.microsoft.com/VisualStudio/feedback/details/1573191/visual-studio-2015-typescript-cordova-project-is-giving-the-error-the-debugger-cannot-continue-running-the-process-unable-to-start-debugging-when-trying-to-run-debug

Answer 5

My first port of call would be to check your build output after setting your build output logging to Diagnostic.

VS Menu > Tools > Options > Projects and Solutions > Build and Run > MSBuild project build output verbosity > Select - Diagnostic

This might then give you a clearer indication of why it is not building/debugging.

---

This led me to a couple of issues, though yours may not be the same.

npm GET failing behind proxy due to Tunnel Agent

The main issue for me being that (I presume) the install had changed the version of nodejs on my machine. There was a node error when trying to get dependencies from npm to do with the Tunnel-agent Request path contains unescaped characters.

Googling around led me to an Ionic issue - https://github.com/driftyco/ionic-cli/issues/321 - and following the advice for changing the index.js file in the Tunnel Agent folder fixed the issue for a new Typescript Cordova project that I created to test. So then I just moved all my files to the new project.

Cannot find the right module

Another debugging step I tried along the way was to do with an error about not being able to find the right module (mentioned here - Configure the Visual Studio Tools for Apache Cordova).

If you see unexpected errors when trying to build the Blank App template, see Re-install vs-tac.

This tells you to Clear Solution, then Clear Cordova Cache (steps in the link), which is what lead me to re-GET the dependencies and find the NPM issue.

Answer 6

I had the same issue and I finally fixed it. I think the issue is with the node upgrade. First.. uninstall node.. and I mean get everything.. after you uninstall make sure you delete node from the program files and your user folder.. In the user folder make sure to get both the npm folder and the npm-cache. Then installed node from the latest installer on the web site.. Oh yea.. make sure you get the 32 bit version.. just had issues with the 64 bit.

Then I did a repair on Visual Studio 2015... Rebooted and it all worked again..