Why can't Visual Studio TACO find the application I'm trying to debug?

Question

I use a visual studio running in parallel on a Mac. The Mac functions as my build server for iOS. I am trying to get debugging that works with a visual studio for both the simulator (iPad Air iOS 9.3) and the actual device (actually iPad Air). At this point, it may be useful to focus on the simulator first.

When I try to run on a simulator (iPad Air) from a visual studio or on a real device, my application runs on a device or simulator before the visual studio seems to hang for a few moments, eventually reporting the following error message:

We were unable to find the application you are trying to debug. Make sure the device> is connected, woken up and unlocked. Also, make sure it has Web> Inspector turned on.

The device is connected. In the case of the simulator, there is no device to connect.

The device is awake and unlocked. In the case of a simulator, there is nothing to wake or unlock. The application starts while the visual studio is still debugging just before the error message is returned.

I checked and double checked that the web inspector is enabled on both the device and safari on the Mac. I can run the build from XCODE and debug through Safari.

It seems unusual that the application does open in the simulator before the visual studio returns with the error that it cannot find the application. If the visual studio cannot find the application, then why did it start?

I would be very grateful for any help.

Wednesday [Updated]

I am using a MacBook Pro running Windows 10 in Parallels.

Windows configuration

• Visual Studio 2015 Update 2
• Cordoba 6.1.1
• TACO Updated 8.1
• Node 6.0.0

MacBook Pro Configuration

• Cordoba 6.1.1
• Node 6.0.0
• iPad Mini 2 runs iOS 9.2 (13C75)
• iPad Air 2 works 9.2.1 (13D15)

Update 1: I installed the visual update for Studio 2 and still get the same error message. I appreciate the offer though!

Update 2: Thank you for your suggestion. I edited the configuration, changed the timeout settings, and restarted the build server as suggested. The error associated with the real device was replaced by a warning with the same result. The simulator supports the same error.

Now the warning reads:

Completing the launch of the application. Check your network connection and try again. If you start the device, make sure that the web inspector> is installed on it.

I have a web inspector enabled. It seems that the visual studio does not wait a full minute before returning with an error or warning. Also, the visual studio environment seems to freeze (not responding) when it tries to connect to a device or simulator.

I also tried using multiple networks and getting the same results.

Is there any additional information I can provide that might be helpful?

Update 3:

Any other suggestions or additional information I can provide? I'm really at a standstill. Fortunately, this is not a showstopper, as I can do some debugging in safari when deploying to the device, but it is frustrating.

Is it typical for visual studio to freeze when trying to connect to a device for debugging?

I also do not think that visual studio is waiting for the full duration of the timeout settings that have been configured.

I updated every dependency that I can think of, and made sure that the versions of the cord correspond to ios and windows. I'm at a dead end ...

Answer 1

I increased the amount of memory available for the Windows 10 virtual machine from 4 to 5 GB, and now the debugger is connected, as expected, without errors.

I post this in case it is useful to someone else.

Answer 2

What you see may be the result of a timeout in the remotebuild tools, this can happen for various reasons (including overall network performance). Take a look at the following answer to another post ( Apache Cordova / Visual Studio 2015 tools do not run the application in the IOS simulator ) for some recommendations: how to change timeouts

• first launch of remotebuild saveconfig on macos terminal
• Open the RemoteBuild.config file in the Text Editor along the path of the previous step
• Change appLaunchStepTimout to 60000 (1 min)
• Change the value of emulatorLaunchTimeout to 60,000 (1 min)
• Save file
• run remotebuild on terminal
• Run the project with Visual studio again

Answer 3

I sometimes encounter the same error, but this happens much less with the latest update of VS 2015, Update 2 TACO Update 8.1 - If you can update this level ( VS2015 Update 2 ), it can solve the problem for you.

I still sometimes see this error with Update 2. But usually this happens with non-incremental (full) iOS builds and seems to be related to synchronization. Update 2 fixes a lot of problems, so I recommend you upgrade.

Answer 4

Edit2: The problem appeared again, so it was not the final fix, but now it works fine.

Edit: I have reset iPad settings from Settings → General → reset → reset all settings, and now it works.

I have the same problem when testing on my iPad 1, but it works on my iPhone 6. They both run iOS 9. I have no other iOS devices to test, so I can not draw any exact conclusions from this.

Answer 5

I encountered the same problem as you. and I just tried to switch from debugging to release, and everything was decided. and I can do debugging. this is a strange solution, but it is mistakenly said that it cannot just debug, so I thought about it.