CODEWITHSUNDEEP
visual-studio-cordova
Matt Honeycutt
Matt Honeycutt

Reputation: 1009

Visual Studio Tools for Apache Cordova - iOS Debugging Fails

I'm no longer able to debug my Cordova app on the iOS simulator. I get the dreaded "We're unable to find the app ... you're trying to debug." error. I've tried all the troubleshooting steps, but nothing has worked so far.

I should note that this was working just fine. I was able to debug my app multiple times, with no issues, and then suddenly this error started, and nothing I've tried has fixed it.

Interestingly, the actual build logs in Visual Studio make it look like everything went fine:

Requesting debug on remote iOS device for buildNumber 6805 on server https://<redacted>:3000/cordova... Debugging - Successfully Debugging on the device {webDebugPort=9221}

Anyone have any ideas?

UPDATE 1 Tried this on my local OS X device, too, and got a similar result. Here are the actual build logs:

Unable to attach to debug. Check that http://Matts-Mac-mini:9221 is accessible. We were unable to find the app you’re trying to debug. Check that the device is connected, awake, and unlocked. Also, make sure it has Web Inspector enabled. ------ Cordova tools 6.1.1 already installed. Requesting emulate on iOS Simulator for buildNumber 522 on server http://Matts-Mac-mini:3000/cordova... Emulated - Successfully sent to ios Simulator ------ Cordova tools 6.1.1 already installed. Requesting debug on remote iOS device for buildNumber 522 on server http://Matts-Mac-mini:3000/cordova... Debugging - Successfully Debugging on the device {webDebugPort=9221}

It looks like things fail, but then the later messages (which appear right away) make it look like things worked. And the app is indeed running in the simulator on my Mac.

Upvotes: 1

Views: 732

Answers (1)

Laguana
Laguana

Reputation: 161

After the discussion in the comments, I believe that the issue here is using a shared machine for debugging. If there are multiple iOS simulators running on a machine at the same time (Typically because there are multiple users connected to the machine each running their own simulator) then remotebuild cannot guarantee that you connect to the correct simulator. This is because we use ios-webkit-debug-proxy which assumes that only a single iOS simulator exists, and doesn't expose a way to restrict which one it connects to.

If you are trying to debug an app in the simulator and there is another user with a different simulator, you may connect to the wrong simulator where your app will not be running, and that can cause the error that you see.

Upvotes: 2

Related Questions