20
votes

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 still can't start the application.

Looked everywhere and found no reference to this problems. Others suggest that environment variables are not set or tools not installed. I triple checked and environment variables are fine and tools are indeed installed.

I uninstalled everything (including git) from programs and features and reinstalled vs2015 RTM with no success, same problem.

I also installed extra stuff from android sdk manager, no luck.

No idea what's wrong and the error message visual studio gives no clue.

Enviroment pathserror messageempty dropdownandroid sdk manager

11
What do you have in your build output? I can't build a fresh Cordova project at the moment after upgrading to RTMKlors
I have upgrade to RTM and I can only Debug > Android > Ripple -. Debug > Android and Windows device are not working.DeanB_Develop
Removed VS 2015 RC and installed VS 2015 RTM. Can't build Cordova project.SPDoctor
@SPDoctor check the build setting out that I posted in my answer, it should help you to get a better idea of what's failingKlors
build success. no error. If I do npm install ripple-emulator and run ripple emulate from command prompt, it works. I did clear cache and reinstall vs-tac and also re uninstalled / installed cordova tools, sdk, etc. it's just like vs doesn't pick up the debugger. I also run a full repair. Still no luck.Bart Calixto

11 Answers

34
votes

Looks like a library is corrupted from the upgrade. Please give this a try:

  1. Close all VS instances
  2. cd %appdata%\"..\Local\Microsoft\Phone Tools"
  3. rename CoreCon folder to something else
  4. Launch VS again.

That's it.

2
votes

The answer from Leo works for me.

Here the documentation of my research, if it does not work for any other user.

Watch the output, to get your specific cause. Increase the build-Verbosity in VS-Options.

go to Tools -> Options -> Tools for Apache Cordova, click the 'Run Dependency Checker'.

Check the installed Visual Studio features, this is selected by default:

VS for Cordova-Development

Compared to msdn:Install Tools for Cordova

Add also:

  • Emulator for Windows Phone 8.1
  • Android Native Development Kit (R10E, 32 bits)

And if you still get no emulator after compiling a blank cordova app:

no preinstalled 8.1. Emulator

I think then you have to install google chrome: msdn "The installer does not install Google Chrome, which is required if you want to run the Apache Ripple simulator for iOS and Android, and it does not install Apple iTunes, which is required for deploying an app to an iOS device connected to your Windows PC."

Also check your Hyper-V Settings:

I'm checking out the Tools\Visual Studio Emulator for Android: Activated Emulator Message

Check the SystemRequirements

Check this link: Troubleshooting the Visual Studio Emulator for Android

Or give "reinstalling node.js" a chance. Wait for "Setup Repair" again.

Hope my documentation here helps someone.

2
votes

I had the same issue using Ripple Emulator. I solved the problem by deleting the cache of cordova (VS-Tools-Options-Apache Cordova Tools-Cordova Tools-Delete cache...).

I've also changed the port from 4400 to dynamic (under Ripple emulator).

1
votes

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

1
votes

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..

0
votes

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.

0
votes

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?

0
votes

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.

0
votes

I'm working through a similar issue. It seems in my case that the failure is specific to my Windows user profile. When I created a new local user account, the new user doesn't experience the problem. Removing your Windows user profile is a potential work-around, if you don't mind the hassle.

0
votes

I just close all visual studios that are opening (vs 2012, vs2013) and reopen vs2015. Ripple-Nexus, Device, google emulator... appear instead of "start" icon only.

enter image description here

0
votes

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.