Hi, Which versions of MonoDevelop and MonoTouch are you using?
I just remembered that the port in MonoDevelop's configuration file shouldn't be used in the most recent versions of MT/MD. Rolf On Thu, Apr 5, 2012 at 9:59 PM, Dean Cleaver < [email protected]> wrote: > Rolf, > > > > Any further suggestions? Uninstall and reinstall everything? > > > > Dino > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Dean Cleaver > *Sent:* Wednesday, April 04, 2012 11:47 AM > *To:* Rolf Bjarne Kvinge > > *Cc:* [email protected] > *Subject:* Re: [MonoTouch] WiFi debugging > > > > Hi Rolf, > > > > No – nothing logged in that file since last night. And changing to 12345 > has no effect – connection as per the device console is still “Connection > Refused” on port 12345. > > > > Dino > > > > *From:* Rolf Bjarne Kvinge [mailto:[email protected]] > *Sent:* Wednesday, April 04, 2012 11:14 AM > *To:* Dean Cleaver > *Cc:* Dimitris Tavlikos; [email protected] > *Subject:* Re: [MonoTouch] WiFi debugging > > > > Hi, > > > > Is anything printed to ~/Library/Logs/MonoDevelop-2.8/MonoDevelop.log? > > > > Or maybe you've installed some other software which happens to use port > 10000 (you can easily test this by editing the file > ~/Library/Preferences/MonoDevelop-2.8/MonoDevelopProperties.xml and replace > "10000" with some other number, like "12345" - just remember to close > MonoDevelop before editing the file, otherwise they'll be lost). > > > > Rolf > > > > On Wed, Apr 4, 2012 at 6:08 PM, Dean Cleaver < > [email protected]> wrote: > > Just ran it again on the iPod, and this is what it output: > > > > Apr 4 11:06:01 unknown KleverLogicFlashValetiPhoneValet[1643] <Warning>: > MonoTouch: Added IP to look for MonoDevelop: 192.168.31.77 > > Apr 4 11:06:01 unknown KleverLogicFlashValetiPhoneValet[1643] <Warning>: > MonoTouch: MonoDevelop Port: 10000 Transport: WiFi > > Apr 4 11:06:01 unknown > UIKitApplication:com.kleverlogic.flashvaletpro[0xab0e][1643] <Notice>: > MonoTouch: Socket error while connecting to MonoDevelop on > 192.168.31.77:10000: Connection refused > > Apr 4 11:06:01 unknown KleverLogicFlashValetiPhoneValet[1643] <Warning>: > MonoTouch: Debugger not loaded (disabled). > > Apr 4 11:06:02 unknown kernel[0] <Debug>: launchd[1643] Builtin profile: > container (sandbox) > > Apr 4 11:06:02 unknown kernel[0] <Debug>: launchd[1643] Container: > /private/var/mobile/Applications/57AB2E04-9B62-4811-8B28-6E30DF6A4546 [69] > (sandbox) > > > > > ------------------------------ > > *From:* Rolf Bjarne Kvinge [[email protected]] > *Sent:* Wednesday, April 04, 2012 10:59 AM > > > *To:* Dean Cleaver > *Cc:* Dimitris Tavlikos; [email protected] > *Subject:* Re: [MonoTouch] WiFi debugging > > > > Hi Dean, > > > > Yes, I mean the iOS Device Console (you can see it either in MonoDevelop's > iOS Device Log pad, or in Xcode's Organizer). > > > > You should see a number of lines starting with "MonoTouch: ", please > include all those (and anything else that might look relevant). > > > > Rolf > > > > On Wed, Apr 4, 2012 at 5:31 PM, Dean Cleaver < > [email protected]> wrote: > > You mean in the console? I am getting “Connection Refused”. > > > > The MacBook is 192.168.31.77, and that’s the IP showing. The devices are > 192.168.31.76 and 192.168.31.89 – so both on the same wireless and subnet > etc. > > > > Any ideas why the connection would be “refused”? Has some update to my Mac > included a firewall or something? > > > > *From:* Rolf Bjarne Kvinge [mailto:[email protected]] > *Sent:* Wednesday, April 04, 2012 8:24 AM > *To:* Dean Cleaver > *Cc:* Dimitris Tavlikos; [email protected] > > > *Subject:* Re: [MonoTouch] WiFi debugging > > > > Hi, > > > > Which versions of MonoTouch and MonoDevelop are you using? > > > > And can you add "-v -v -v" to the additional mtouch arguments, and then > check what's written to the device log when the app starts up? > > > > Rolf > > > > On Wed, Apr 4, 2012 at 3:03 PM, Dean Cleaver < > [email protected]> wrote: > > Hmmmm... something's changed then. Used to work, but now all I get is the > vibration to say debugging isn't connected, and that's it. Mega frustrating > when you cannot debug using USB because you specifically need it to be > unplugged. > > > -----Original Message----- > From: Dimitris Tavlikos [mailto:[email protected]] > Sent: Wednesday, April 04, 2012 12:41 AM > To: Dean Cleaver > Cc: [email protected] > Subject: Re: [MonoTouch] WiFi debugging > > That is also the message I get, but debugging over WiFi works. > > On 4 Apr 2012, at 5:56 AM, Dean Cleaver wrote: > > > Should it say "waiting for debugger to connect on :0..."? > > > > > It looks wrong to me, and WiFi debugging no longer works - any ideas how > to fix it? > > > > Dino > > _______________________________________________ > > MonoTouch mailing list > > [email protected] > > http://lists.ximian.com/mailman/listinfo/monotouch > > Dimitris Tavlikos > Software Developer > Author of "iOS Development using MonoTouch Cookbook" > Email: [email protected] > Twitter: http://twitter.com/#!/dtavlikos > Blog: http://software.tavlikos.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
