Hi, I think i've solved this issue. It was my build arguments for a custom binding I made. Strange thing is, it only started in the last few days, whereas those arguments have been there for about a month. Also, the problem was intermittent which is strange, but eitherway its working now. Hopefully this helps someone else.
On Tue, Jan 10, 2012 at 12:34 AM, Dermot O Sullivan <[email protected]> wrote: > Only on the device. It when using usb and wifi debugging. I've noticed the > best way to fix it is: > > 1. Disconnect cord from device > 2. Build/deploy/debug to the simulator > 3. Reconnect cord to device > 4. Debug on device > > This seems to be a work around. > > On Tue, Jan 10, 2012 at 12:21 AM, Rolf Bjarne Kvinge <[email protected]>wrote: > >> Hi, >> >> Which versions of MonoTouch and MonoDevelop are you using? Is it >> happening in the simulator too, or only on device? Do you have usb >> debugging disabled? >> >> Thanks, >> Rolf >> >> On Sun, Jan 8, 2012 at 6:15 AM, dermotos <[email protected]> wrote: >> >>> I've started to get this recently. I have to delete the app from the >>> device >>> and redeploy. Very annoying, hope its fixed soon. >>> >>> -- >>> View this message in context: >>> http://monotouch.2284126.n4.nabble.com/Could-not-open-port-for-debugger-Another-process-may-be-using-the-port-tp4238473p4274969.html >>> Sent from the MonoTouch mailing list archive at Nabble.com. >>> _______________________________________________ >>> MonoTouch mailing list >>> [email protected] >>> http://lists.ximian.com/mailman/listinfo/monotouch >>> >> >> >
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
